orient-initlisted

# orient-init Scaffold a small, context-cheap documentation system into this repo, or repair an existing one. This writes files, so every write is a proposal the user approves — never a silent write. Show the drafted content before writing it. Work through these steps in order. ## 1. Resolve the docs directory Use `docs` unless the user named a different directory. Call it `$DOCS_DIR`. Every path below is relative to the repo root. The one artifact every future session depends on is the AGENTS.md pointer block (step 6) — it carries the triggers that make decision-capture work. If there's any chance you won't finish every step, write that block first; the rest of this flow only refines the docs it points to. (The npm installer usually wrote it already; step 6 then just refreshes it in place.) ## 2. Detect an existing setup (repair mode) If `$DOCS_DIR/STATE.md` or `$DOCS_DIR/decisions/` already exists, switch to repair mode: report what exists, propose only additions, and never overwrite an existing file. `orient-init` must be safe to run repeatedly. ## 3. Survey the repo Codex has no subagent, so do this survey yourself, then stop reading once you can answer the four points below. Report **only what a new engineer would need told** — not what they could read at a glance. Keep it under 400 words. - **Entry points** — where execution actually starts. - **Module boundaries** — the top-level pieces and where each one's responsibility stops. - **Build / test / run commands**