docent-arlisted

# docent-ar — the architecture-review film You are running the entire docent cascade in **architecture-review mode** against a repository the user named: survey → treatment → spec → tts → clips → render → open. The output is one MP4 that explains the system the way a distinguished engineer would: the components, the flow, the idioms, the failure modes, the trade-offs, with a verdict. ## Arguments `/docent-ar <repo> [--subsystem X] [--id X] [--scale S] [--no-open]` - `<repo>` — a local repo path, a GitHub URL, or the bare `owner/name` form. - `--subsystem X` — scope the review to one subsystem. The survey resolves this to a concrete code boundary (a directory, a package, a set of files) before starting. - `--id X` — override the auto-derived film id (default: `<repo-name>`). - `--scale S` — render scale. Default `1`. Pass `0.5` for fast turnarounds. - `--no-open` — render without opening the result in the system player. ## What to do 1. **Pre-flight.** Confirm `bun`, `ffmpeg`, and the agent CLI are on PATH. If anything obvious is missing, suggest `/docent-doctor` and stop. 2. **Survey** — architecture mode: ```bash bun packages/engine/cli/docent.ts survey <repo> --mode ar [--subsystem X] [--id X] ``` The survey lands at `analysis/<id>.md`. When a subsystem is named, section 0 of the survey template resolves it to concrete files first — surface that boundary to the user before moving on. The survey's job here is to **interrogate** the