docs(handoff): skill-usage-telemetry — ranks 2/3/7 closed, both hosts at 875ceb11, and the flake block was wrong about test AND mechanism

[ZacxDev]

Updates the skill-usage-telemetry handoff with tonight's outcomes. Doc-only.

What this records

• Rank 3 closed — nix/pkgs/default.nix merged as feat(pkgs): add inxi + cpu-x — the CPU-Z equivalents for hardware profiling #1135 (875ceb11), verified by content on origin/main, not by ancestry. The base clone's dirty copy was byte-identical (a2a6fe09) to the merged blob, so it was a redundant copy of the PR rather than orphan WIP.
• Rank 2 closed without being worked — both hosts' homelab-talos/containers/clawgate built source is CURRENT (drift-check.sh: stale=0 unmeasured=0, compared=2 same=2 differing=0). The two-host source split the doc recorded is gone.
• Both hosts shipped to 875ceb11 — ship.sh rc 0, cross-host compared; drift-check.sh rc 0 afterwards. This is also what finally deployed test(gate): the RESULT: verdict grammar is RESERVED — a registry entry could forge it #1119, which was merged-not-shipped.
• The doc's flake block is refuted — it named the wrong test and the wrong mechanism. It is fsync contention, not a readiness race; corrected per fix(store-api flake): it is fsync CONTENTION, not seed/ordering — with a dev-host reproducer #1181 (merged 0c333846), with that PR's reproducer and its two "fixes that look right and are not".
• A rank collision is resolved — the ranked list's item 7 is the followups/G5 item, while three State now sections call test(gate): the RESULT: verdict grammar is RESERVED — a registry entry could forge it #1119 "rank 7". Since a claim slug is <doc>-<rank>, the skill-usage-telemetry-7 claim held for test(gate): the RESULT: verdict grammar is RESERVED — a registry entry could forge it #1119 was addressing G5's identity.

Conflicts with #1169

⚠ #1169 edits this same file and conflicts textually with this branch (test-merged and aborted; my branch is unchanged). Opening against main was the operator's explicit call. Whichever merges second must resolve by hand — and note this repo has been bitten by rerere replaying a resolution from a different merge, so re-run the gate on the merged tree rather than trusting a replayed resolution.

Gate

Doc-only change; no code path touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E3jzstFU7ECH1ARJhJZop1