Pi-Orchestrator: GOTCHA Fabrication Removal (MC #10549)

Context

Problem: Pi-orchestrator was auto-generating GOTCHA docs at two sites, bypassing ZAKON #25 quality gate (H/BLOCKER → /prompt-forge → /mehanik). Pi-orch is NOT the authority for /prompt-forge work.

The Two Sites Removed

Site 1: Pre-Spawn Auto-Gen (Step 4.55)

Fabricated GOTCHA before spawn so spawn-gate would permit task dispatch
Violated /prompt-forge exclusivity for H/BLOCKER tasks
REMOVED

Site 2: Post-Spawn Synthesis

Fabricated GOTCHA after agent ran, based on proof-of-work artifacts
Papered over agent omissions (agent's failure → pi-orch's rescue)
Rationale for removal: Agent omission IS agent failure; pi-orch should not mask it
REMOVED

Replacement Behavior

GOTCHA Missing Pre-Spawn

mc.js blocks task with reason: "awaiting_forge: GOTCHA doc missing — run /prompt-forge {id} first, then unblock"
Task stays blocked until human review unblocks

GOTCHA Missing Post-Spawn

mc.js blocks task with reason: "agent omitted GOTCHA file — needs /prompt-forge and human review"
Task stays blocked until human review unblocks

Status Note

mc.js does NOT have awaiting_forge as first-class status — used blocked with reason-prefixed text. Future enhancement: add awaiting_forge status (track in separate MC if scope warrants).

Current State

Daemon STOPPED
Code lands cold
No production behavior change yet

Test Plan

7 tests at ~/system/tests/pi-orch-await-forge.test.js
23 regression tests at ~/system/tests/spawn-gate.test.js
Run: node --test ~/system/tests/pi-orch-await-forge.test.js

Change Genesis

Pi-orch hardening Talas 3 (parent thread #10043 reform)
Depends on α #10548 (Spawn Gate Node-Side Parity)

Cross-Reference

Last updated: 2026-05-04 | Part of pi-orch hardening Talas 3