Documentation compaction

Audit and compress documentation while preserving adopted behavior, evidence and discoverability. Follow the installed lifecycle and environment policies; use agents-md-edit for AGENTS.md edits. Delegate only under current user authorization.

Choose the work

• Read-only audit: run python3 scripts/audit.py PROJECT_ROOT and inspect actual coverage, misplaced/repeated content and relevant authority. Use the audit sections of maintenance workflow. Do not install presets, stamp or repair files.
• Bounded cleanup: inspect the affected domain and overlapping references, then use the relevant structure/compression/verification sections of that workflow. Do not expand a small request into a repository census.
• Whole-project cleanup: read maintenance workflow. Discover effective global instructions, audit each actual documentation host, decide structure by readability, compress content and verify the full requested scope.

Preservation and verification

Change generated or inherited rules through their actual source; preserve managed markers and valid coverage. Use concise content summaries with the shared relevance instruction, without arbitrary reading quotas. Compression does not drop scope, exceptions, timing, evidence or machine-parsed literals.

Read compression guide before substantive compression. Distinguish a smaller file from preserved behavior. Check navigation, source/path liveness, ordinary and exceptional scenarios, and required compact-stamp coverage. Report per-domain results and unresolved factual contradictions; a successful script or stamp is limited coverage evidence.

Migration completion and stop rule

An authorized knowledge migration is complete when the shared authority preserves the reusable knowledge's applicability and exceptions, local product contracts and evidence remain intact, generic duplication is replaced where safe, and content rereading plus navigation checks reveal no unresolved material defect. For multi-file work, reuse one concise source → authority → local retention/outcome table when useful; a small edit needs no extra ledger.

After accepted changes pass the scoped checks, close out rather than starting another harvest or wording pass. Reopen for a concrete defect, contradiction, missed authorized item, or new user direction. Additional reviews need a specific unresolved question; optional polish alone does not require another cycle.