code-example-verifierlisted

Make documentation examples copy-pasteable and truthful against the current codebase. Do not silently convert real examples into vague pseudocode to make the audit pass. ## Workflow 1. **Inventory examples.** Find fenced code, inline shell commands, configuration blocks, request examples, imports, package names, paths, environment variables, and claimed output. Group duplicated snippets by canonical source. 2. **Classify execution.** Mark each example `runnable`, `compile-only`, `requires controlled integration`, `destructive/manual`, or `pseudocode`. Flag unlabeled pseudocode presented as executable code. 3. **Check prerequisites.** Verify supported runtime and package versions, setup steps, imports, public APIs, file paths, environment variables, and permissions against the repository—not memory. 4. **Build minimal harnesses.** Extract examples into temporary or existing documentation-test fixtures without altering their semantics. Use sanitized local data and mock only external boundaries that the example is not teaching. 5. **Run safely.** Execute format, compile/typecheck, and runtime commands as appropriate. Never run destructive, production, billing, or credentialed examples; validate their syntax and document the manual test boundary. 6. **Verify outputs.** Assert exit status, response shape, created artifacts, and documented output. Normalize volatile timestamps, ports, IDs, and paths without weakening meaningful assertions. 7. **Fix the source.** Update imports, c