Refresh architecture debt register current-count drift on main #2965

Problem

2026-06-29 guard-frontloading audit found architecture debt register current-count drift on main.

Command:

python tools/aippocampus/docs/debt_report.py --headroom-only --json

Compact result stays small, but reports ok=true/status=pass, warning_count=2, and first warning architecture_debt_register_count_drift: 12 register rows drift from script_line_count(). The refresh command is python tools\aippocampus\docs\debt_report.py --refresh-register-counts --write.

Full detail summary: harmless_small_drift=6, positive_drift=5, negative_drift=1. Representative rows: hooks/claude_code.py +32, recall/feedback/events.py +11, tests/aippocampus/test_update_sync.py +15, instruction_surface_owner_registry.py +9, update/plugin_installer.py -64.

Open issue searches for architecture debt count drift, refresh-register-counts, and debt_report.py headroom found no owner.

Recurrence mechanism

Merged PRs can leave current_count stale across many rows. Because this is only advisory, agents may trust stale guard-budget evidence or rediscover the refresh chore late during closeout.

Likely files / tests

• docs/architecture/architecture-debt-register.md
• tools/aippocampus/docs/debt_report.py
• tests/aippocampus/test_architecture_boundaries.py
• tests/aippocampus/test_docs_health.py

Non-goals

• Do not raise budgets just to erase drift.
• Do not hard-fail all historical drift without a separate product decision.
• Do not make compact debt output verbose; full detail can stay behind --detail full.

Acceptance

• python tools/aippocampus/docs/debt_report.py --headroom-only --json no longer reports architecture_debt_register_count_drift on main.
• Positive/negative drift rows are reviewed before refreshing; real budget pressure gets split/trim ownership rather than quiet budget increases.
• Focused debt/doc tests pass.
• Closeout states whether drift remains an advisory refresh chore or gained a lightweight owner/preflight reminder.