chore: complete spec 040

[bborbe]

Pipeline-only. Records the verification result for spec 040 and moves it to specs/completed/.

Spec 040 re-verified end to end after the AC2 repair in #111 — all 15 acceptance criteria matched to first-hand evidence, including an independently reproduced mutation proof (retune livenessWindow to 30s → the value-lock assertion fails at claude_session_test.go:300; restore → passes).

No code changes.

[ben-s-pull-request-reviewer]

Confirmed — no ## Unreleased section exists. The finding is a false positive for this PR: the diff contains only a spec markdown file move (in-progress → completed). The code change it documents was released in v0.116.4 (PR #111). An ## Unreleased section would be meaningless here since there's no source to ship from this PR.

The spec accurately reflects the verified behavior: the Verification Result section (lines 196–209) documents a full re-verification of all ACs against HEAD 0c076a3, including AC2 mutation proof, AC1 integration test, AC7 writeback invariants, AC14 CHANGELOG confirmation, and a live Vault UI run. The completed timestamp and status are correct.

---

Manual review complete. No code changes — spec artifact only.

Step 7 cleanup (no worktree created in this run — cwd is already at PR head, Step 0b was skipped):

N/A

---

Step 5: Consolidated Report

Must Fix (Critical): None.

Should Fix (Important): None.

Nice to Have (Optional): None.

Notes:

• This PR (chore: complete spec 040) moves a spec from specs/in-progress/ to specs/completed/ and appends a Verification Result block. No Go source, test, or configuration files are changed.
• The code fix for the bug described in the spec was shipped in v0.116.3/v0.116.4 via PR #111. The verification result confirms those releases are correct.
• The CHANGELOG lacks a ## Unreleased section — expected and correct here, as the release it would trigger was already cut in v0.116.4 before this PR. The changelog/unreleased-entry-required rule fires because it cannot distinguish "PR with no source changes" from "PR missing a release trigger."

---

Step 8: Verdict JSON

{
  "verdict": "approve",
  "summary": "This PR completes spec 040 by moving it from in-progress to completed and appending a full verification result (PASS, 2026-08-27). No source code is changed; the bug fix was shipped in v0.116.4. No issues found.",
  "comments": [],
  "concerns_addressed": [
    "correctness: specs/completed/040-bug-session-start-blocks-on-full-headless-turn.md accurately reflects the verified behavior from PR #111 — verification result section confirms all ACs passed against v0.116.4, including AC2 mutation proof, AC1 detachment integration test, AC7 writeback invariants, and a live Vault UI run. Status 'completed' and timestamp are correct. addressed"
  ]
}