Define Code Bridge and browser control parity boundary

[shiny-code-bot]

Finish Line

Code Bridge and browser/control behavior has a tested Codex-fork overlay boundary before any bridge implementation is restored.

Current Status

State: Created from #397 parity ledger.

Deleted evidence from the pre-#390 tree includes code-rs/browser/, code-rs/browser/tests/local_navigation.rs, code-rs/core/src/bridge_client.rs, TUI browser history cells, and browser-session VT100 snapshots.

Current main has app-server/Desktop remote-control compatibility, but not the Every Code local Code Bridge control channel as a proven overlay.

Acceptance Criteria

• Inventory old Code Bridge/browser tests and behavior probes from fa0c33944f.
• Classify each as port, rewrite, covered, defer, or retire.
• Define the additive overlay boundary for console/error/pageview/screenshot/control events.
• Add parity fixtures for local navigation/control behavior before implementation ports.
• Do not mutate Desktop compatibility responses to carry Every Code bridge behavior without validation.
• End code-bearing slices with ./build-fast.sh passing cleanly.

Relationships

• Child of Stabilize Every Code parity on Codex CLI fork baseline #397.
• Related to Validate Codex-base Every Code in copied Codex Desktop app #387 because app-server/Desktop compatibility shapes the control boundary.

[cbusillo]

Merged the Code Bridge/browser boundary slice in #415.

Validation evidence:

• git diff --check
• ./build-fast.sh
• scoped Claude planning and review on the Define Code Bridge and browser control parity boundary #399 boundary map
• PR check: Blob size policy passed

What landed:

• docs/code-bridge-browser-parity.md classifies the old pre-feat: replace Rust substrate with Codex base #390 bridge/browser evidence as port/rewrite/defer work.
• The ledger and feature inventory now link to the Define Code Bridge and browser control parity boundary #399 boundary map.
• The boundary explicitly keeps Code Bridge as an additive Every Code overlay and separates bridge control events from Codex Desktop remote-control status/probe/request paths.

Keeping #399 open for the fixture slice. Next action: add fake bridge metadata/server/control fixtures that prove discovery, stale heartbeat handling, subscription normalization, control request/result matching, and separation from Desktop remote-control paths before implementation ports.