[Task][RFC]: Complete the research exploration control-plane contract

[huangruiteng]

Outcome / 目标

完成研究探索控制面的证据、组合与闭环契约。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: S3/S8/S11, 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.

#3173 shipped explicit composition projection and successor binding. The RFC keeps canonical research observation/closure, shared write-time enforcement and model-selection qualification separate; deferred inference is not current behavior.

Work remaining

• Reconcile M1/M2 against current Explore owners, then complete explicit-only evidence, closure and composition-gap projection with actual consumers.
• Implement M3’s exact Todo/experiment lineage and write-time gate as a separately reviewable behavior change. M4 model selection follows qualification; M5–M7 retain their research gates.

Ownership and ongoing work

Reuse #4391/#3243 for research and benchmark policy. Core replan/authority repair is already active: keep research semantics in Explore, do not rewrite generic settlement or duplicate maintainer experiments.

Contribution route: available for a bounded proposal/PR within this RFC. Name the intended milestone and exact files in a claim comment so simultaneous contributors do not duplicate work.

Acceptance

• Characterize existing behavior first; direct reads/ACKs cannot masquerade as experiment execution or accepted closure.
• Replay, invalidated input, rejected/deferred selection and stale lineage cannot clear a live obligation incorrectly.
• CLI/status and the affected Explore UI use the same bounded facts; feature-off parity and real tool-path evidence accompany any promoted behavior.
• 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/explore
• loopx/control_plane/goals/goal_frontier
• docs/reference/protocols/goal-vision-replan-contract-v0.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.