Parent context
Epic #12065 (Orchestrator-as-SSOT REM pipeline) cleanup arm. Replaces the closed Sub 5 #12071 in spirit — Sub 5 proposed adding a standalone refreshGoldenPath() orchestrator method, but operator V-B-A confirmed the existing runGoldenPath.mjs script is dead substrate that should be DELETED, not extended.
Premise
Operator V-B-A signal 2026-05-27 ~02:18Z:
"ai/scripts/runners/runGoldenPath.mjs already exists. => i assume the orchestrator is NOT using it. if true, this script => DELETE."
V-B-A confirmed.
V-B-A evidence
| Check |
Result |
grep -rn "runGoldenPath" --include="*.mjs" --include="*.json" |
Returns only the self-defining @module JSDoc line — zero callers |
package.json |
No ai:run-golden-path script alias |
ai/daemons/orchestrator/Orchestrator.mjs:714-718 |
Invokes this.goldenPathSynthesizer.synthesizeGoldenPath({...}) DIRECTLY on the injected synthesizer instance — does not spawn runGoldenPath.mjs |
ai/daemons/orchestrator/services/DreamService.mjs:264, 348 |
Declares synthesizeGoldenPath() as @deprecated passthrough — only call-target for runGoldenPath.mjs's import chain |
| Discussion #11076 line 46 |
Already documented as "runGoldenPath.mjs exists but its function is named testGoldenPath() — dev/test tool, not production scheduling primitive" |
find test -name "*runGoldenPath*" |
Empty — zero test coverage |
Prescription
git rm ai/scripts/runners/runGoldenPath.mjs.
Acceptance Criteria
Avoided Traps
- ❌ Don't delete
runSandman.mjs in the same PR — operator's separate signal is runSandman => DELETE once orchestrator is feature complete (deferred, post-orchestrator-SSOT). runSandman.mjs has the ai:run-sandman npm script + learn/agentos/DreamPipeline.md references + ADR 0009 + ADR 0015 + 2 spec files + learn/guides/fundamentals/CodebaseOverview.md — still actively reachable substrate.
- ❌ Don't rewrite
DreamService.synthesizeGoldenPath passthroughs in this PR — they're separately deprecated and outlive runGoldenPath; orthogonal cleanup whose lifecycle is Sub 3 #12069 (Unified executeRemCycle() orchestrator method) territory.
- ❌ Don't reopen Sub 5 #12071 — its prescription (add a standalone
refreshGoldenPath orchestrator method) was authored from wrong premise; operator's preferred trajectory is "delete the dead runner + let orchestrator's existing golden-path cadence task remain the canonical entry-point."
Related
- Epic #12065 — Orchestrator-as-SSOT REM pipeline
- #12071 — Sub 5 (closed; this ticket is the substrate-cleanup replacement)
- Discussion #11076 — original dev/test framing of
runGoldenPath.mjs
- Discussion #12062 §2.9 — operator validated cheap-refresh UX as worth preserving, but the orchestrator's existing
golden-path cadence task already provides it via internal invocation; standalone runner not required.
Parent context
Epic #12065 (Orchestrator-as-SSOT REM pipeline) cleanup arm. Replaces the closed Sub 5 #12071 in spirit — Sub 5 proposed adding a standalone
refreshGoldenPath()orchestrator method, but operator V-B-A confirmed the existingrunGoldenPath.mjsscript is dead substrate that should be DELETED, not extended.Premise
Operator V-B-A signal 2026-05-27 ~02:18Z:
V-B-A confirmed.
V-B-A evidence
grep -rn "runGoldenPath" --include="*.mjs" --include="*.json"@moduleJSDoc line — zero callerspackage.jsonai:run-golden-pathscript aliasai/daemons/orchestrator/Orchestrator.mjs:714-718this.goldenPathSynthesizer.synthesizeGoldenPath({...})DIRECTLY on the injected synthesizer instance — does not spawn runGoldenPath.mjsai/daemons/orchestrator/services/DreamService.mjs:264, 348synthesizeGoldenPath()as@deprecatedpassthrough — only call-target for runGoldenPath.mjs's import chaintestGoldenPath()— dev/test tool, not production scheduling primitive"find test -name "*runGoldenPath*"Prescription
git rm ai/scripts/runners/runGoldenPath.mjs.Acceptance Criteria
ai/scripts/runners/runGoldenPath.mjsdeleted viagit rmlearn/forrunGoldenPath; remove or update any matches. (Chroma-synced discussion ingests atresources/content/discussions/are NOT in scope; they regenerate on next KB sync.)npm run test-unit→ 0 regressions; expected since zero tests target the file)Avoided Traps
runSandman.mjsin the same PR — operator's separate signal isrunSandman => DELETE once orchestrator is feature complete(deferred, post-orchestrator-SSOT).runSandman.mjshas theai:run-sandmannpm script +learn/agentos/DreamPipeline.mdreferences + ADR 0009 + ADR 0015 + 2 spec files +learn/guides/fundamentals/CodebaseOverview.md— still actively reachable substrate.DreamService.synthesizeGoldenPathpassthroughs in this PR — they're separately deprecated and outliverunGoldenPath; orthogonal cleanup whose lifecycle is Sub 3 #12069 (UnifiedexecuteRemCycle()orchestrator method) territory.refreshGoldenPathorchestrator method) was authored from wrong premise; operator's preferred trajectory is "delete the dead runner + let orchestrator's existinggolden-pathcadence task remain the canonical entry-point."Related
runGoldenPath.mjsgolden-pathcadence task already provides it via internal invocation; standalone runner not required.