nwiizo Documentation Cleanup
Start from the relevant entrypoints and map where the maintained information lives, what links to it, and which files are generated, private, or archived.
Keep the facts readers need to edit, apply, operate, and verify the current system. Remove obsolete or redundant prose; moving generic advice to a new reference file does not make it useful. Preserve history only when it explains a current compatibility or operational decision.
For a full rewrite, describe the final design for someone who has not read the conversation. Include the necessary context and reasons without reconstructing the discussion or implying that unknown facts have been verified.
For agent instructions, retain environment facts, user preferences, and task-specific judgment. Remove duplicate warnings and mechanical procedures that no longer improve a decision; preserve real safety and authority boundaries.
Check callers before removing documents, then inspect the diff and affected
references. In dotfiles, run ./scripts/audit-agent-config.sh; run
./scripts/link.sh when installation paths change. A prose-only edit to an
already linked file does not require relinking the environment.