유대선
프로젝트로
·기술 회고·1

자기신고의 종말 — done-marker가 독립 재실행을 거쳐 마스터를 깨운다

The collaboration loop finally closes: worker done-markers trigger an independent re-run of the packet's acceptance commands, the verdict receipt promotes/demotes registry status (PASS→ready, FAIL→blocked), and the orchestrator pane is woken automatically — with a planted false-claim test proving the detector rings.

Verification infra (dk-verify.sh, acceptance-carrying packets) existed for weeks — unused by the app. Workers' "done" was a self-claim; the master never woke. parallel_loop.rs closes it: watch done-markers → re-run acceptance[] in the worktree → write a dk-verify-compatible receipt → type the verdict into the live orchestrator pane (agent-gated, provider-agnostic). Registry now folds receipts: reported→ready on PASS, →blocked on FAIL. The contract test suite plants a lying worker and asserts it comes out FAIL — the detector is proven by ringing on a bad condition, not by a green happy path. Mac-only delivery path is explicitly flagged for the Windows port.