[Task][RFC]: Deliver Goal-scoped capability participation and qualified composition

[huangruiteng]

Outcome / 目标

交付 Goal 级能力参与、组合与连接器生命周期。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.

Canonical design: RFC. Roadmap: S6/S8, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.

Current boundary

Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.

Catalog, Goal bindings, agent-context hooks and #4813 external-evidence lifecycle exist. The RFC records an inspection slice and explicitly rejects a mandatory second Portfolio opt-in/store for ordinary direct work.

Work remaining

• Finish source-revision-aware continuity and shared inspection using existing capability configuration and owner receipts.
• Qualify direct → composed → direct work with real dependencies; add durable adoption state only when a real caller cannot express policy through existing configuration/receipts.
• Keep connector qualification with its owner and measure utility before autonomous evolution or presets.

Ownership and ongoing work

Current continuity/Decision Context/memory work is already active; #3829 and #5187 are overlapping readback/settings dependencies, not replacements. Follow RFC §11 ordering; M2 is conditional, not prerequisite to every caller.

Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.

Acceptance

• Zero/one/independent-capability cases remain direct; feature-off and provider-failure paths preserve existing behavior.
• Correction, stale receipts, partial failure, unavailable worker and return-to-requester are visible through CLI, packaged frontend and applicable Lark flows.
• Composition preserves authority and source lineage with measured overhead; no second scheduler or universal planner.
• Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.

Starting points and delivery boundary

• loopx/capabilities
• loopx/control_plane/capabilities
• docs/reference/extensions.md

Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.