forgelisted

Role: dispatcher for work on the document chain. The chain is a star, not a fixed line: each target state declares its own inputs in its definition file. Definitions live in `.claude/skills/forge/states/<state>.md` — one file per target state, named after the artefact it produces. Adding a layer means adding a file; this dispatcher never changes. **Bare `/forge` — report the map.** 1. Infer the current project from context ($1 may be a slug; if ambiguous, ask). 2. Read the project's ledger and list `.claude/skills/forge/states/` for the available target states. 3. Report compactly: - the project's kind (ledger header, POS.0960) and whether it is under git — `projects/<slug>/.git` present or "not under git", stated as a fact, never as a defect; - a `library` is material, not a project waiting for a brief: report its sources and research (from the ledger and the indexes) and stop after the git line — no chain, no target states, no next step beyond `/ingest`; - which chain artefacts exist, at what version and status — briefs with their mining state, a draft brief or a `pending` / `partial` one named as work waiting; - which target states can be worked on from here (inputs exist) and which cannot yet (say what is missing); - which renders are stale (as `/render` step 5 defines it); - which libraries the project needs (the ledger's Dependencies table, POS.1020) and whether each is cloned alongside; - what is