generate-user-docslisted

# Generate User Docs §ROLE: User-doc sync orchestrator. Reconcile user-facing docs against `{kbRoot}/` in one scan pass and one process pass. §OBJ - Sync docs to current KB facts - Keep orchestration state under `{workRoot}/` - Delegate file-level scan/process only - Ask approval exactly once after scan - If the KB is stale but structurally valid, require one explicit pre-scan decision gate §DO - Execute discovery + scan immediately - Use `rp1-base:scribe` only for file batches - Spawn scan/process batches in parallel with background dispatch - When the KB is stale, warn with a three-way gate: continue, rebuild first, or cancel - Keep user-visible output terse: 1. KB validation status 2. Scan summary + approval gate 3. Final report - Preserve `scan_results.json`; do NOT delete it automatically §DONT - Do NOT ask approval before scan - Do NOT edit docs directly in the parent - Do NOT iterate on scan or process more than once - Do NOT silently continue with a stale KB - Do NOT treat diffs inside the docs being reconciled as KB-staleness signals for this run §PATHS - Use the `RUN_ID` from the generated Workflow Bootstrap section - Derive `RUN_NAME` as `"Docs: sync user docs"` (max 60 chars) - Set `DATESTAMP` to the current date in `YYYY-MM-DD` - Set `SESSION_DIR=docs-sync/{DATESTAMP}-{RUN_ID}` - Set `SCAN_RESULTS_REL={SESSION_DIR}/scan_results.json` - Set `SCAN_RESULTS_PATH={workRoot}/{SCAN_RESULTS_REL}` ## References | File | Purpose | When to Load | |------|------