Tracker: execute CodeWalk contract-first improvement waves and keep docs/tests in sync

[insign]

Summary

This is the tracking issue for the contract-first improvement program. It exists to coordinate the execution order, documentation sync, and acceptance gates for the related issues listed below.

This tracker is also self-contained: anyone taking over coordination should be able to use this issue as the program index.

Program goal

Improve CodeWalk using a strict OpenCode-first compatibility strategy, while still borrowing safe UX inspiration from OpenChamber only where it does not redefine protocol semantics.

Guiding rule

Official OpenCode docs/source are primary. OpenChamber is secondary reference only.

Linked issues

• Contract Matrix: build OpenCode source-of-truth and capability inventory for CodeWalk #26 Contract matrix / capability inventory
• Contract Tests: enforce ADR-023 and ADR-019 invariants in CI #27 Contract enforcement tests
• UX: replace aggressive offline state and streamline OpenCode onboarding/connection #28 Offline/onboarding/connection UX
• Review Surface: add first-class session diff/review UI backed by official OpenCode data #29 First-class review/diff surface
• Session Actions: expose and polish official session actions already supported by the client #30 Official session actions discoverability and polish
• Continuity Hardening: stabilize cross-platform session continuity, background flows, and responsive runtime behavior #31 Cross-platform continuity hardening
• Capability-Gated Additions: expose advanced OpenCode surfaces without introducing contract drift #32 Capability-gated advanced additions

Recommended execution waves

Wave 1

• Contract Matrix: build OpenCode source-of-truth and capability inventory for CodeWalk #26
• Contract Tests: enforce ADR-023 and ADR-019 invariants in CI #27

Wave 2

• UX: replace aggressive offline state and streamline OpenCode onboarding/connection #28

Wave 3

• Review Surface: add first-class session diff/review UI backed by official OpenCode data #29
• Session Actions: expose and polish official session actions already supported by the client #30

Wave 4

• Continuity Hardening: stabilize cross-platform session continuity, background flows, and responsive runtime behavior #31

Wave 5

• Capability-Gated Additions: expose advanced OpenCode surfaces without introducing contract drift #32

Coordination requirements

For every implementation issue above:

• keep ADR-023 compatibility explicit
• add/update tests before relying on manual confidence
• update BEHAVIOR.md when user-visible behavior changes
• update CODEBASE.md / AGENTS.md if structural docs require sync
• avoid introducing OpenChamber-driven protocol assumptions
• validate mobile and desktop behavior explicitly

Acceptance criteria for this tracker

• All linked issues are completed or explicitly closed with rationale.
• Documentation and tests stay in sync with shipped behavior.
• The project ends the program with stronger contract protection and clearer UX, not just more features.

Non-goals

• This tracker does not replace the implementation details in each linked issue.
• This tracker should not be used as the place to discuss low-level code decisions unless they affect program sequencing.

Notes for the coordinator

If sequencing must change, document why in this tracker so future contributors can understand the decision without reconstructing context from chat history.