Say a decision was lost only when one was (#710)

[MongLong0214]

Closes #710.

doctor told this repository four decisions were never written to the history. The four captures it meant hold zero records and never reached staging — nothing was drafted, so nothing was dropped.

NONCE     PHASE     RECORDS  FLAGS
ba54a69c  prepared  0        stale
bd065cf2  prepared  0        stale
464b4c13  prepared  0        stale
e8eb71c6  prepared  0        stale

The count was never wrong. lost has separated staged losses from earlier drafts since #458; the explanation appended after it was written for the staged branch and emitted for both.

The guard that should have caught it

warns without claiming a record was lost when nothing reached staged — the test is named for exactly this property and asserted the absence of the other branch's wording:

expect(result.detail).not.toMatch(/expired before reaching a commit/);   // the count's wording
// never asserted:            /never written to the history/             // the loss claim

The consumed case two tests below already uses never written to the history as the loss claim, so the string was established as the thing to check. This case just did not check it. That assertion is now what the name promises, and it fails against the unfixed source:

AssertionError: nothing staged means nothing was dropped:
  expected '1 capture(s) can no longer apply — th…' not to match /never written to the history/

What the non-staged branch says now

None reached staging, so no record was dropped — the commit each was prepared for either never happened or happened without it

That is the file's own existing explanation of staleness, from the comment above stranded.

Not changed

The severity. An abandoned draft still warns — #584 showed that going quiet on a path that looks healthy is how this check loses its meaning, and that judgement is separate from the wording.

Verified

• the new assertion fails before the fix, passes after
• npx tsc --noEmit clean
• 29 cases pass across doctor-pending-backlog, pending-command, capture-pipeline-e2e
• npm run build:canonical then npm run artifact:verify → de9222c7187eb818ab20cfea63fa3e918e56f7eca1dc9fff654cae4bf39c0daf

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/main..b452535f7c19bc87c7e5d6a7a37bbbcd6796698c
Active constraints: not read — commitlore: git log --follow accepts exactly one pathspec, so renames are not followed for 6 paths; query one path at a time to follow its rename chain (6 changed paths)

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}