The Conductor UI can create a mission whose production route emits workerId km-agent even when km-agent is absent from the live swarm.yaml roster. On hermes-workspace vps-prod, the prior Review mission conductor-1783658525138 created exactly one assignment to km-agent; the live roster contains orchestrator, researcher, ops-watch, librarian, and builder, and the requested three specialist lanes were never launched. Source tests passed while dist/server still contained the stale hardcoded route, so this also exposed a source-vs-dist deployment gap. I implemented and deployed a roster-derived fix plus regression coverage in fork commit fe05128 (mojoho81/hermes-workspace vps-prod). Targeted tests: 11/11. dist/BUILD_COMMIT matches HEAD and rg finds no km-agent in the production router bundle. Please consider the roster-derived assignment logic and a post-build stale-bundle check for upstream.
The Conductor UI can create a mission whose production route emits workerId km-agent even when km-agent is absent from the live swarm.yaml roster. On hermes-workspace vps-prod, the prior Review mission conductor-1783658525138 created exactly one assignment to km-agent; the live roster contains orchestrator, researcher, ops-watch, librarian, and builder, and the requested three specialist lanes were never launched. Source tests passed while dist/server still contained the stale hardcoded route, so this also exposed a source-vs-dist deployment gap. I implemented and deployed a roster-derived fix plus regression coverage in fork commit fe05128 (mojoho81/hermes-workspace vps-prod). Targeted tests: 11/11. dist/BUILD_COMMIT matches HEAD and rg finds no km-agent in the production router bundle. Please consider the roster-derived assignment logic and a post-build stale-bundle check for upstream.