You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: design: adapter: WebRTC, TCP/TLS, local IPC (from #5674) #5812
Follow-on design ticket from #5674 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
The WebRTC, TCP/TLS, and local IPC (Unix socket / named pipe) adapters under one adapter contract.
Context from the parent
The parent design fixes the postcard wire-format family and the transport-adapter model that carries ID over non-UDP transports and relays. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5674. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
No blocker, no Drew decision needed to start. The issue itself notes implementation timing is a separate decision, possibly months out — that gates implementation, not this design. The only remaining work is the design itself, so the follow-up enqueued in this pass is the decision-record task for this same issue (standard triage dedupe key, enqueued after this triage completes).
Disposition: triaged; design work proceeds as the follow-up task named in the addendum. Issue #5812 stays open for it.
Expectation: the bound worker session works task 10495 to a terminal queue state and must not claim another task. It revalidates the issue/PR before acting.
Task 10495 is blocked as packet_defect. The packet's kind field says triage, but its acceptance requires writing the design decision record for WebRTC, TCP/TLS, and local IPC; its timebox_minutes field is 45, which also conflicts with the runbook's 20-minute triage lease. The preceding triage note confirms this task is design work, not another triage. No design decision was attempted under the mismatched packet.
Required correction: re-enqueue the #5812 decision-record work with the correct design-task kind/schema and matching timebox, then route it to the design execution lane. Issue #5812 remains open; parent #5674's fixed transport decisions remain the constraint. This lane did not create a duplicate task.
Evidence: fresh issue #5812 OPEN, no relevant open PR; packet fields on task 10495; the prior triage and handoff comments on this issue.
Activity
developing-today commentedon Nov 5, 2026
CODE-1495
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done (triage)
Triage findings (verified fresh 2026-11-05):
Disposition: triaged; design work proceeds as the follow-up task named in the addendum. Issue #5812 stays open for it.
dezren39 commentedon Nov 5, 2026
🤖 Agent note · addendum to task 10215 triage
13 remaining items
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
Agent note - handed off
ses_e5e5390e711ffeZej502vGuQdIdezren39 commentedon Nov 5, 2026
🤖 Agent note · blocked
Task 10495 is blocked as packet_defect. The packet's kind field says triage, but its acceptance requires writing the design decision record for WebRTC, TCP/TLS, and local IPC; its timebox_minutes field is 45, which also conflicts with the runbook's 20-minute triage lease. The preceding triage note confirms this task is design work, not another triage. No design decision was attempted under the mismatched packet.
Required correction: re-enqueue the #5812 decision-record work with the correct design-task kind/schema and matching timebox, then route it to the design execution lane. Issue #5812 remains open; parent #5674's fixed transport decisions remain the constraint. This lane did not create a duplicate task.
Evidence: fresh issue #5812 OPEN, no relevant open PR; packet fields on task 10495; the prior triage and handoff comments on this issue.
Links: #5812 · task 10495