Task log vs. archive disposition — default tightened

Trigger: every completed KB-OS task ended up with both a terse log (logs/) AND a full archived copy (Tasks/archive/YYYY-MM/) — 11/11 checked. /task-complete presents log/delete/archive as three alternatives, but sessions were defaulting to “log it, and also keep the archive just in case.”

Finding: git history already IS the full archive. Verified on KB-OS-resume-rate-limit.md — git log -p on the old path returns the complete content and edit history forever, whether or not a live copy sits in the vault. The archive copy added zero retrievability, only cost: graphify double-counting (same event as two nodes), qmd search noise (two hits for one fact), and SSOT drift risk (log and archive can disagree after a later correction).

Fix:

• ~/ai-config/claude/commands/task-complete.md Step 6 rewritten: default is now A (log) or B (delete); C (archive) is a named exception — only for genuinely irreproducible reasoning (multi-session design exploration, negotiation trails), not a “keep it just in case” reflex. Deployed, verified no drift between SSOT and deployed copy.
• Deleted the 10 existing redundant archive copies in Tasks/archive/2026-07/ after confirming each had a matching log (KB-OS-focus-ongoing-project, KB-OS-kb-config-ssot-fix, KB-OS-next-upgrades, KB-OS-resume-rate-limit, graphify-fullvault-rerun, idea-capture-workflow, mbr-content-consolidation, mega-project-subprojects, memory-phase3-sessionstart-hook, vault-wide-biggest-rocks). Content still fully recoverable via git log -p on each old path.

Commits: KB 88593f0 · ai-config b0d7c51

Disposition: task note deleted (not archived) after this log was written — per the rule this task itself established.