bld-util-documentationlisted

# bld-util-documentation — the app, explained in Simplified Technical English Two halves, and both matter: 1. **Survey** the app that is actually in front of you — its stack, screens, flows, data, and limits. Document reality, never intent. 2. **Write** it in **ASD-STE100 Simplified Technical English** and ship it as a real subpage of the app (`/docs`), not a Markdown file nobody opens. The rules live in `references/ste-rules.md`. **Read that file before writing a single sentence of the page.** STE is a controlled language with hard limits — sentence length, verb forms, one-word-one-meaning — and it is not something to approximate from memory. ## Step 0 — Two questions, then go Ask only what changes the work: 1. **Who reads it?** End users (default), or developers who will run the code? One audience per page. If both are needed, write the user page first. 2. **Where does it live?** `/docs` inside the app is the default. Accept any route the user names instead. Everything else is a judgment call — make it and say what you assumed. ## Step 1 — Survey the app Cheapest useful order. Stop as soon as you can describe every screen and every user action without guessing. 1. `<app>/CLAUDE.md`, `<app>/planning.md`, `README.md` — purpose, status, backlog. 2. `package.json` — stack, scripts, real dependencies. 3. `design-system/MASTER.md` — the tokens and components the docs page must use. 4. Routes and screens — `app/**/page.tsx` (Next.js) or `src/App.tsx` plus