area-statuslisted

# /area-status <area> [--live] ## Host dispatch contract - Codex: invoke skills as `$skill`; use Codex collaboration roles and GPT-5.6 model tiers. - Claude: invoke skills as `/skill`; use Claude Agent/Skill tools and Claude model aliases. - Examples that name both hosts are routing contracts. Never send one host's command syntax to the other. - A bare `/skill` in this shared source denotes the Claude form; Codex dispatches the same named skill as `$skill`. Answers "is this area actually done?" with evidence, not recall. Read-only toward the area under assessment except the report file it writes. ## Stage 1 — Deterministic facts (no model) ```bash bash "$(dirname <this skill>)/scripts/collect-area-facts.sh" "$AREA" ``` Sections: MEASURED_REF · BEHIND_COUNT · SPEC_ESTATE · CODE_SURFACE · CITED_SURFACES · TEST_INVENTORY · NEWEST_EVIDENCE (+age) · POST_EVIDENCE_COMMITS · VERDICT_HINT. CITED_SURFACES exists because a literal-token scan alone can miss the area's real owning surface (PATH-001, 2026-08-21: "photo-picker" had zero literal hits in its own code surface, yet `web/src/components/media/*` and `pipelines/website/contracts/native-photo-fill.yaml` were the actual surface, cited by path in five predecessor specs). When CODE_SURFACE is empty, the collector mines spec/doc prose that content-matches the area token for concrete repo paths those specs cite, and lists the ones that resolve in the working tree — capped, with the cap stated, per No silent caps. When CODE_SURFA