run-next-readinesslisted

# run-next-readiness `retail-orchestrate` observes disk state, decides the next phase, and then EXECUTES it (self-healing against the gate). This skill is the extracted, standalone, READ-ONLY decision half: given ONE table's committed `readiness-status.yaml`, it computes the single next allowed action and STOPS. It runs nothing, writes nothing, and grants nothing. It answers the question; the human (or `retail-orchestrate`) acts on the answer. ## Module contract (this skill IS a filled Product Module declaration) Per the F024 Companion Tools Architecture contract (`templates/module-contract.md`). - **Authority category:** Product Module - **Capability level:** `read-only` *(exactly one)* - **Product layer:** `4` *(readiness spine lens; orthogonal to category)* - **Roadmap feature:** `F080` **On-disk spec:** `specs/080-run-next-readiness-state-machine/` - **Owner:** `the readiness / data-quality lead` *(a named role -- never "the agent")* - **Status:** `Authored` ### What it does (one line) > Reads one table's `readiness-status.yaml` (Core Authority), walks the seven > stages in fixed order, and returns the single next allowed action (or a > stop / approval-required / terminal / defect outcome) -- creating no truth, > executing nothing. ### Core Authority it READS It reads these committed truth artifacts; it never writes them. - `mappings/<table>/readiness-status.yaml` -- `table`, `current_stage`, per-stage `status` (the four words), `evidence[]`, `blocking_reas