handover-check

/handover-check

Explain the current session's status line to the user in plain, practical terms — the read a smart person who doesn't live in Opus session-management would want.

The heavy lifting is deterministic: a Layer-1 script (handover-facts.mjs) resolves every classification/verdict and pre-formats every number, so the isolated subagent only has to compose — weave the facts into insightful prose. This keeps the check off the very context it measures, kills the band-misread and backtick-mangle classes (the model can't fumble what it's handed), and front-loads every tool call so the report is one uninterrupted reply (Claude Code collapses/fragments tool output — nothing must land mid-prose).

How to run

Two phases — all data-gathering first, then one report.

Phase 1 — gather (emit NO prose yet). Order matters: the fact sheet runs FIRST and freezes the exact snapshot, then the two charts read that frozen copy (--frozen) so all three see the SAME session — even if a concurrent same-project session clobbers the live sidecar between reads (the within-report session-split bug).

1. Run the fact sheet alone first — it writes the freeze. All three scripts live in the config home, which is $env:CLAUDE_CONFIG_DIR when it is set, else $env:USERPROFILE\.claude ($HOME/.claude off Windows) — so a second-subscription session runs its own deployed build rather than the primary home's. Substitute that directory for <config home> in the commands below. (Node accepts the forward slashes on Windows too. On Windows, run these through the PowerShell tool.)

   node "<config home>/handover-facts.mjs"
   

   If it prints MISSING, tell the user to let the status line render once (press Enter on an empty prompt) and re-run — stop here. If its first line is FOREIGN, this session has no status-line snapshot of its own and the resolver fell back to another session's sidecar (the following lines give this session vs the snapshot's owner — each named in words with its id fragment in brackets when that session has a name, id fragment alone otherwise; relay them as given). This is the signature of a session that never renders a status line — the Claude Code desktop app is the common case. Do NOT report the numbers: they belong to a different session and would be meaningless here. Tell the user plainly that handover-check can't read this session (no live status line — e.g. the desktop app) and that it works from a terminal session where the status line renders — then stop here. If its first line is SCHEMA_MISMATCH, the snapshot was written by a status line of a different build than this reader, so its shape is one this reader does not know. The following lines give the schema version this reader expects, the version the snapshot carries, and the one instruction that clears it — relay all of them as given. Do NOT report any numbers, and do NOT run the charts or the subagent: there is no reading here, only the fix. Then stop here.

2. Then, in one message, run the two charts with --frozen AND spawn the subagent (they're independent):