#3328 (2026-08-08) re-verified this exact code and found it wired, not inert —
multi-agent-coordinator was kept, "own issue." That issue is this one. Two
independent re-verifications later, the code is still reachable but the behavior
is dead: ork's own doctor recommends setting the env var that starves it on every call.
One shipped component tells users to permanently disable another.
| gate check | at HEAD | verdict |
|---|---|---|
| detectPipeline() trigger loop | reachable code, real logic | code alive |
| isAgentTeamsActive() yield | fires on every call (user settings) | behavior dead |
| 2026-08 telemetry | 699 checks = 699 yields = 699 no-trigger | 0 detections |
| last successful detection | 2026-01-23 17:05 | 202 days silent |
| doctor recommendation | tells users to set the starving var | self-contradiction |
Owner call recorded on the issue: DELETE. Both re-verifications agree on the
edit set below; every file:line was re-checked against this worktree's HEAD before
touching anything, and two lines had drifted from the first analysis
(unified-dispatcher.ts:59/:116, not :61/:119).
multi-agent-coordinator.ts −412 whole module: detectPipeline, PIPELINES,
createPipelineExecution, registerPipelineExecution,
formatPipelinePlan, getPipelineByType
pipeline-detector.ts −139 whole hook, plus its 627-line / 23-test suite
task-integration.ts −40 updatePipeline · completePipelineStep
(zero callers outside their own tests)
entries/prompt.ts −3 re-export + legacy override-compat registration
unified-dispatcher.ts −2 import + HOOKS registry entry
feedback-loop.ts −21 pipeline-aware routing branch in
getDownstreamAgents — static mapping fallback
KEPT (telemetry: it's the only branch that ran)
KEPT PipelineExecution + registry.pipelines —
registerPipeline/getActivePipeline still feed
task-existence-gate; #3353 owns that call
Second-order defect, filed on the issue but not fixed here:
task-existence-gate Case 3 blocks on getActivePipeline() being
truthy, which was already structurally unreachable before this change — CLAUDE.md's
"blocks them in active pipelines" claim was already false.
verification 315 test files, 7,543 tests passed · typecheck clean
root build clean · validate-counts PASSED (hooks.json unaffected —
pipeline-detector was never a hooks.json entry, only dispatcher-wired)
split-bundles golden count: 200 -> 199 (one legacy export removed)