spec-handoverlisted

# Spec Handover — the atomic write **Prerequisites:** the DO-IT pipeline — `DO-IT.md` (operating protocol), the `think` and `orc` skills, and your repo (`REPO_ROOT` in CONFIG). Read DO-IT.md **§2 (bus + naming)** and **§4 (handover)** — this skill *is* §4; the rules below don't restate them, they execute them. You're in a `think` session, the spec is written (under `docs/do-it/specs/`). This skill gets it to the orchestrator. It is **one self-verifying action**: the spec lands discoverably **and** its ledger record is born, or it fails loudly. No partial state, no manual relay, no git (orc commits on its own branch). ## What "ready" means (refuse otherwise) The spec header must have a non-empty `intent:` and ≥1 acceptance criterion. If either is missing, do **not** hand over — say why and send the user back to finish. ## The action 1. **Allocate the number AND birth the record in one atomic command — never hand-roll a grep, never compute `max+1` yourself.** `next-num` is the single source of truth: under one machine-global lock it scans every bus dir with the correct pattern (3 digits *followed by a hyphen* — so the year in a grandfathered `2026-...` date-stem file can't read as 202), computes the next number, **and births the `registered` ledger record before returning** — so a concurrent `think`/handover session blocks until the reservation is on disk and sees the next number, never the same one (this is what killed the 110 double-book). It ref