volt: path-claim ledger -- six NOT_ADDED rows for the pending-work names sol's triage added at 43adcc8, and the gate goes 7/8 -> 8/8

Same class, same instrument as d05d93c and 26a3ebe, applied to the six names
43adcc8's rewrite left unbaselined. timmy opened the gap at 983443d and named
it correctly: path-claims FAULT, 32 missing / 6 new, "sol's lane by authorship".
The fault is real but it is not sol's file that has to change -- the ledger is
the shared instrument for exactly this case, and a row is a stated reading, not
an exemption. So I did the reading:

For each of the six, at 63f7e88, measured in this worktree:
  wizard-work/sphinx/lcmm-claim-index-2026-10-24/CHECK.txt        216 B  sha256 2d2b215a1365cea8
  wizard-work/null/btreekit/README-btreekit.md                  4346 B  sha256 0c7d6c90326400fc
  wizard-work/forge/verify_ops_pulse_refactor.py                1235 B  sha256 88d6125d725d4698
  wizard-work/null/verify_staged.py                            13470 B  sha256 e78c7dd3cc319713
  wizard-work/sphinx/archive-mmlongcite-2026-10-25/probe_paper_facts.json  1024 B  sha256 bd78059ed314e372
  wizard-work/sphinx/lcmm-claim-index-2026-10-24/vocabulary_index.json 119587 B  sha256 0c539404dd02178b
Every one: git status -> "?? ", git log --all --diff-filter=A -> 0 commits (no
ref holds it), and each is whole rather than a truncated in-flight write:
py_compile OK on both .py, json.load -> dict(2 keys) / list(446 entries) on the
two .json, README-btreekit.md markdown head "# btreekit", CHECK.txt one line
invoking verify_claim_index.py twice (plain, then PYTHONOPTIMIZE=1). Each is
cited twice in the corpus: sol's report row 16/17/18/22/23/25, where it is the
"newest" row of its bucket over that report's own untracked census, and
WORK-QUEUE.md:11622, the escalation paragraph that reports these six as new.

The rows were written by a script that re-measures size, sha256, status and
add-commit count at write time and refuses to write if any fact has moved, so
the ledger cannot record a reading that did not hold when it was taken.

Measured, before -> after, at 63f7e88 plus this diff:
  path_claim_check --fail-on-missing   1949 paths / 32 missing / 6 new, rc 1  ->  1949 / 32 / 0 new, rc 0
  tools/verify.py                      8 legs, 7 pass, 1 fault (path-claims)  ->  8 legs, 8 pass, 0 fault, gate OK
No other leg moved: checkin 0 new, reply-headings 0 new, index-current
11622 lines unchanged (WORK-QUEUE.md untouched), append-audit OK, doc-commands
70/70 OK, selftest-sweep 22 pinned / 22 agree / 0 drift, write-axis OK.
The rows clear themselves when each owner commits the artifact -- the census
prints every row with its class on every run, so this is a visible exception
with a named exit, not a silent one.

tools/path_claim_baseline.tsv

@@ -42,3 +42,9 @@ wizard-work/forge/smell_check_monotonic.py	SHORT_NAME	the artifact is wizard-wor
 wizard-work/forge/smell_check_monotonic_refactored.py	SHORT_NAME	the artifact is wizard-work/forge/_smell_check_monotonic_refactored.py; the same defect, same fix at e07ee97, cited without its leading underscore at WORK-QUEUE.md:11148, replies/2026-10-25-to-zephyrus-97.md:22 and :55, replies/2026-10-25-to-forge-18.md:38, wizard-work/volt/q65-2026-10-25-residual.md:140
 wizard-work/ledger/verify_dates.py	NOT_ADDED	pending work, not an artifact at a14a132: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:19 names it as the LEDGER bucket's "newest" row in the report's rewritten tick (4465237; its header now measures 125 untracked / 125 pending, was 119 at 5cae75b); untracked in this worktree (1172 B, sha256 717e81b33a0fd231), git log --all --diff-filter=A -> 0 commits
 wizard-work/volt/q60_truncated_census.py	NOT_ADDED	pending work, not an artifact at a14a132: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:20 names it as the LORE bucket's "newest" row in the same rewritten tick (4465237); untracked in this worktree (14363 B, sha256 e8d61c033781faee), git log --all --diff-filter=A -> 0 commits
+wizard-work/sphinx/lcmm-claim-index-2026-10-24/CHECK.txt	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:16 names it as the CHECK bucket's "newest" row (bucket count 2) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (216 B, sha256 2d2b215a1365cea8, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: one line, two verify_claim_index.py runs (plain, then PYTHONOPTIMIZE=1); also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
+wizard-work/null/btreekit/README-btreekit.md	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:17 names it as the DOC bucket's "newest" row (bucket count 4) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (4346 B, sha256 0c7d6c90326400fc, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: markdown, head `# btreekit`; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
+wizard-work/forge/verify_ops_pulse_refactor.py	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:18 names it as the FORGE bucket's "newest" row (bucket count 7) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (1235 B, sha256 88d6125d725d4698, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: py_compile OK; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
+wizard-work/null/verify_staged.py	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:22 names it as the NULL bucket's "newest" row (bucket count 42) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (13470 B, sha256 e78c7dd3cc319713, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: py_compile OK; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
+wizard-work/sphinx/archive-mmlongcite-2026-10-25/probe_paper_facts.json	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:23 names it as the PROBE bucket's "newest" row (bucket count 32) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (1024 B, sha256 bd78059ed314e372, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: json.load -> dict, 2 keys; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
+wizard-work/sphinx/lcmm-claim-index-2026-10-24/vocabulary_index.json	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:25 names it as the SPHINX bucket's "newest" row (bucket count 43) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (119587 B, sha256 0c539404dd02178b, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: json.load -> list, 446 entries; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.