handofflisted

# Handing the work over ## The files a handoff touches "Update the handoff docs" means a specific set, discoverable only from what the handoff PRs touched (#155, #159, #170). They are titled *"Hand the `<X>` work over: …"* — the stem is the convention, and the clause after the colon says what kind of handoff it is: *"the traps, not just the result"* on #159 and #170, *"what is covered, what is not"* on #155. - **`CLAUDE.md`** — the two roles, the release-exe lock, and the routing table naming every rule and skill below. It is loaded into *every* session, so what goes here is what every session needs; anything longer belongs in one of the next two. - **`.claude/rules/*.md`** — what bites while *editing* a subsystem, scoped by a `paths:` glob so it loads only when Claude reads a file it covers. A new subsystem note goes in the rule whose **subject** it belongs to; the scope is not part of that choice, for the reason below. **`paths:` is one shared scope for the nine code rules, and that is a decision rather than laziness.** Each was first scoped to the files named in its own title, which is the natural thing to do and was wrong fifteen times: nine filed as review findings across rounds one to nine of [#285](https://github.com/glslang/windbg-mcp/pull/285), six more found by enumerating rather than waiting for the next round — and the ninth landed *after* the shared scope, against `cargo-and-dependencies`, whose first paragraph bound a Rust-only change fro