vault-repo-docslisted

# Vault Repository Documentation Turn a repository into a durable, linked, source-backed OKF bundle. Load `okf-authoring` for the format contract. A full scan means every discovered candidate is reconciled in `coverage.md`; it never means a representative sample. ## Required workflow 1. Read [full-scan-method.md](references/full-scan-method.md). Establish repo path, commit, scan mode, bundle path, and prior coverage ledger. 2. For a full or focused scan, run `scripts/inventory_repo.py REPO --format json > manifest.json`. For an incremental scan, use `--changed-since COMMIT` and repeat `--include-file PATH` for affected registration/contract files. An invalid or diverged baseline must produce `mode: full-fallback`, never a guessed incremental scope. Preserve `manifest.json` in the bundle. Review `scanned_files`, `exclusions`, counts, and suspicious zero-candidate output. Treat candidates as leads, not facts; inspect entrypoints, registration, DTOs, migrations, queries, broker wiring, workers, configuration, and tests. 3. Write `coverage.md` before concept docs. Give every candidate exactly one status: `documented`, `irrelevant`, `generated`, or `uncertain`. Include its evidence, destination document, and a concrete reason. Add manually found candidates to both the manifest and ledger; an unknown ledger row is an audit error. 4. Document breadth first, then depth. Use the completion contracts in: - [api-documentation.md](references/api-