reconcile prompts 186/187 to shipped reality

[bborbe]

What

Prompts 186 and 187 have been sitting in prompts/in-progress/ since 2026-08-21, leaving a 186..187 gap in prompts/completed/. findMissingCompleted gates on presence in completed/, so every prompt without a spec: field has been blocked on this repo for three weeks.

Why this is a bookkeeping fix, not a re-run

Both prompts' work already shipped:

prompt	change	shipped in
186	goal-necessity forward check — agents/task-manager-agent.md, commands/verify-task.md	c70d170
187	goal-necessity inverse check — agents/goal-manager-agent.md, commands/verify-goal.md	79a6949

79a6949 is the same commit that left both files in in-progress/. 186's lastFailReason is validate completion report: completion report status: failed — the completion report failed validation about 8 minutes in, after the edits had landed.

Verified by content on master, not by commit subject: all four target files carry the necessity steps (5. **Check goal-necessity (forward):**, 8. **Check goal-necessity (inverse):**), including the advisory-only and unparseable-SC rules.

Requeuing either prompt would re-apply edits that already exist — a no-op that fails validation again at best, a conflicting duplicate edit at worst.

Change

• status: failed → completed (186), status: approved → completed (187)
• reconciled + reconciledReason recording the shipping commit and how it was verified
• both files moved to prompts/completed/

Contiguity restored: …185, 186, 187, 188…, head 215. prompts/in-progress/ is now empty.

Markdown only — no code, no CLI surface change. make precommit passes.

Context

Found by a fleet sweep of all 89 .dark-factory.yaml main checkouts. This is the class docs/running.md calls out as doctor's blind spot: "a spec whose code already shipped but whose bookkeeping was never reconciled looks structurally fine" — dark-factory doctor reports this repo clean of the gap and flags neither prompt.

Spec 035-verify-goal-necessity-checks (still prompted) should follow the same reconciliation.

[ben-s-pull-request-reviewer]

{
  "verdict": "approve",
  "summary": "Both prompt files are excluded from review by .reviewignore (prompts/), and the reconciliation is factually correct: the shipping commits c70d170 and 79a6949 exist and contain the expected goal-necessity forward and inverse checks respectively.",
  "comments": [],
  "concerns_addressed": [
    {
      "concern": "correctness: status transition from failed to completed for 186; reconciled/reconciledReason fields reflect c70d170",
      "disposition": "addressed",
      "detail": "Commit c70d170 confirmed: agents/task-manager-agent.md carries step 5 'Check goal-necessity (forward):' and commands/verify-task.md documents it. The completion report failed validation but the work shipped; reconciledReason accurately describes the gap."
    },
    {
      "concern": "correctness: status transition from approved to completed for 187; reconciled/reconciledReason fields reflect 79a6949",
      "disposition": "addressed",
      "detail": "Commit 79a6949 confirmed: agents/goal-manager-agent.md carries step 8 'Check goal-necessity (inverse):' and commands/verify-goal.md documents it. The prompt was never re-run but work shipped in the same commit; reconciledReason accurately describes the gap."
    }
  ]
}

[ben-s-pull-request-reviewer]

This is a pure bookkeeping reconciliation — two completed prompt files are moved from prompts/in-progress/ to prompts/completed/ with accurate reconciled metadata and reconciledReason fields citing the correct shipping commits. No code, no security implications, no functional change.

{
  "verdict": "approve",
  "summary": "Pure bookkeeping PR: two prompt files (186, 187) are renamed from in-progress/ to completed/ with reconciled metadata correctly citing their shipped commits (c70d170 and 79a6949). The diff is accurate, consistent with the commit message, and requires no code review.",
  "comments": [],
  "concerns_addressed": []
}