Align discord-blue Every Code bridge with shared protocol #48

Current Status

• Codex Lab Code Bridge reliability slices are merged through PR Add Code Bridge replay witness #101: broadcast replay and the exec-harness witness are covered without claiming deployment/browser E2E.
• Launchplane compatibility work is merged separately, with legacy path retirement tracked in Launchplane.
• discord-blue PR Smoke test agent session env in TUI startup #94 is merged: Discord-facing remote-session wording now uses generic agent-session language, /code pause is wired to the existing pause command path, /agent-session/connect remains canonical, /every-code/connect remains during migration, and legacy host: Every Code reconnects are covered by regression test.
• discord-blue PR Keep custom session sources product-restricted #95 is merged: new Discord session start markers now include session: <session_id>, legacy markers still exact-match, and future reconnects can ignore pid changes only when the persisted marker has the same session id and exactly one candidate matches. This directly hardens the odd empty-thread behavior reported after deploy without risking broad wrong-thread attachment.
• The remaining Align discord-blue Every Code bridge with shared protocol #48 work is to keep the boundary sharp: Codex Lab Code Bridge telemetry/control stays separate from discord-blue remote agent session threads, and Every Code compatibility is retired only after Codex Lab is good enough to be the regular harness.

Acceptance Criteria

• Inventory current discord-blue remote session bridge message types, endpoint path /every-code/connect, token/auth assumptions, session recovery behavior, and user-visible slash-command surface.
• Rename the target concept generically as the Remote Agent Session Bridge (or equivalent generic capability name), avoiding new Every Code / Codex Lab product-brand protocol names.
• Decide which fields/types are reusable as product-neutral provenance/request metadata and which remain remote-session-specific.
• Preserve deployed /every-code/connect compatibility during transition by adding a generic endpoint alias rather than breaking existing clients.
• Create and link a discord-blue retirement issue to remove the retired /every-code/connect compatibility path, clean up old Python module/package names, and delete dead Every Code-specific bridge code once migration is complete.
• Preserve existing Launchplane EVERY_CODE_* env compatibility during transition by adding generic aliases for new clients.
• Create and link a Launchplane retirement issue to remove retired EVERY_CODE_* aliases and clean up old Every Code-specific worker/module names and dead code once migration is complete.
• If a shared protocol package/schema is introduced, discord-blue validates against it without losing existing tests. No shared package was introduced; the cross-repo contract remains in repo tests/scripts.
• Launchplane request-origin metadata remains compatible for work-request correlation.
• No app telemetry/control behavior is forced into discord-blue unless there is a concrete product use case.

Target Surface

/Users/cbusillo/Developer/discord-blue, especially discord_blue/doodads/every_code/protocol.py, bridge.py, tests, and README/service docs. May depend on artifacts from #45.

Validation Gate

discord-blue lint/type/test gates; targeted bridge tests for existing session connection, approvals, user input, commands, and recovery.

Risks

Treating discord-blue as “the Code Bridge” would conflate two bridge families. Keep remote session transport and app telemetry/control related but separable.

Finish Line

discord-blue keeps its existing Every Code service behavior while its bridge/session protocol is aligned with the shared Code Bridge contract or explicitly separated as remote-session transport.

Relationships

• Completed prerequisite: Define Code Bridge protocol, trust, and payload contract #45.
• Codex Lab Code Bridge support: Improve Code Bridge reconnect replay #100 and Add Code Bridge replay witness #101.
• discord-blue bridge alignment: Add agent session bridge endpoint alias discord-blue#92, Genericize agent session bridge wording discord-blue#94, and Harden Discord session thread reconnect discord-blue#95.
• Deferred discord-blue retirement cleanup: Retire Every Code remote-session bridge compatibility names discord-blue#91.
• Launchplane generic env compatibility: Add agent session env aliases launchplane#1315.
• Deferred Launchplane retirement cleanup: Retire Every Code agent-work-request compatibility names launchplane#1313.