Integrate Help, Diagnostics, and Resource Planning into the official Assistant

[gbaudrit]

Area

Cross-cutting

Feature type

Integration

Problem or need

The official Assistant requires several independently useful capabilities, but simply installing them side by side does not define how they are composed, versioned, replaced, or invoked from one stable Assistant Entry.

Expected outcome

The core Assistant router composes Help/Documentation, Diagnostics, and Resource Planning through explicit child-capability bindings while preserving each capability's independent lifecycle and contracts.

Proposed solution

Define an Assistant capability integration contract and wire the official child Flows into #346. Reuse #320 for Help/Documentation, #347 for Diagnostics, and #322/#333 for Resource Planning. Keep capability-specific prompts, Tools, and contracts inside their own capability boundaries.

Scope

• Explicit capability identities/bindings used by the core router.
• Help/Documentation integration from Provide official Console Help and Documentation assistant capability #320.
• Diagnostics integration from Add an official diagnostics capability to the Agentstration Assistant #347.
• Resource Planning integration from Add Agentic Resource Planning with decoupled Resource materialization #322/Package the official Agentstration Resource Planning capability #333.
• Shared request context propagation limited to stable user/session/navigation context, not raw Resource contracts.
• Consistent child success/failure/fallback semantics.
• Capability replacement/versioning rules.
• Causal diagnostics across router and child Flows.
• Tests and documentation.

Out of scope

• Reimplementing child capability logic.
• Copying Resource Planning agents or contracts into the Assistant core.
• Making all future Assistant capabilities mandatory.

Dependencies

Parent: #344.
Depends on #346, #320, #347, and the Resource Planning delivery from #322/#333.

Deployment impact

Configuration change

Acceptance criteria

• The Assistant router can invoke Help/Documentation, Diagnostics, and Resource Planning as separate child capabilities.
• Each child capability remains independently invokable and replaceable.
• Resource Planning integration reuses its official package/contracts without duplication.
• Shared context passed to capabilities is stable and does not expose unrelated Management implementation contracts.
• Child failures/fallbacks are surfaced consistently without collapsing the whole Assistant into one monolithic Flow.
• Parent/child causality identifies the selected capability and resulting execution.
• Tests cover routing to all three capabilities, replacement/missing capability behavior, and failure propagation.

Preliminary checks

• I searched for an existing issue covering this request.