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(serve): dynamic publish/unpublish — bind and unbind programs and pages to ports, interfaces, and paths at runtime #2147
From Drew (2026-10-29): publishing in id should not be a launch-time-only decision.
Building on the bindings model and the program-as-website design (companion issues), add DYNAMIC binding: while a node is running, an operator must be able to bind and unbind — publish and unpublish — programs and pages:
to different ports and interfaces (new listeners opened/closed at runtime), and
to different paths on an existing listener,
without restarting the node. The published set must persist (config / data dir) so a restart restores it, and the current published set must be inspectable (CLI and/or web UI).
Path-override rule: a path binding on the same port as the World Explorer OVERRIDES the Explorer's own route where the paths overlap — that is allowed and intended — but the server must warn loudly at bind time (and at boot, for persisted bindings) naming the shadowed route, unless an explicit acknowledgement flag/config ("I know I'm doing this") is set for that binding.
Acceptance: with the Explorer running on port A, publish a program to port B at runtime and reach it; mount a second program at a path that shadows an Explorer route and see the warning; unpublish both and see the listeners/routes revert — all without restarting the node.
Reason: The remaining feature spans live listener/router lifecycle, privileged protocol control, CLI commands, and integration acceptance; it is not safe to claim completion without implementation and tests.
Resume condition: Continue on the existing branch/worktree; implement the serve-owned manager, operator-only control (not widened by open-writes), publish/unpublish/list, persistence/apply rollback, and the no-restart acceptance walk. Do not treat the documentation commit as task completion.
Session / ID: task 8820 (repo-fleet-monitor run 2026-11-05T15:45:47Z)
Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
Task: Claim evaporated: task 8820 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
Expectation: The next lane claim picks task 8820 up from the queued state and posts a fresh pickup note.
Activity
developing-today commentedon Oct 29, 2026
CODE-1044
101 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off