test: validate content-allocation extension on ha-victron-mpc

[akaszubski]

Summary

Validate the content-allocation extension end-to-end by /sync'ing the updated autonomous-dev into ha-victron-mpc, running /align --content, and confirming the allocation applies correctly with no regression in the target repo's behaviour.

Implementation Approach

1. cd ~/Dev/ha-victron-mpc
2. /sync (pulls extended autonomous-dev with /align --content, extended hook, new templates)
3. Verify extended hook fires: write a temp 200+ line file as .claude/PROJECT.md, run a commit, confirm warning. Remove the test file.
4. /align --content — interactive audit + propose + (with approval) execute on ha-victron-mpc's CLAUDE.md (currently ~103 lines), check whether memory exists / is in scope.
5. Verify no regression in ha-victron-mpc's deploy flow: run pytest tests/ -v (211 tests) and the smoke deploy steps (NOT to Pi — just dry-run/test).
6. Document gaps found in ha-victron-mpc-specific allocation (HACS integration shape may differ from realign/autonomous-dev) → feed back to skill if needed.
7. If allocation gaps surface a class of issue not handled by skill → file as follow-up issue, do not block this validation.

Acceptance Criteria

• /sync succeeds in ha-victron-mpc with extended autonomous-dev
• Extended hook warns on synthetic PROJECT.md violation; silent when removed
• /align --content runs end-to-end interactively in ha-victron-mpc
• Allocation proposal generated; approved subset applied
• ha-victron-mpc's pytest tests/ -v still green (no test regressions)
• No autonomous-dev hook errors on session start, commit, or normal operations in ha-victron-mpc
• Findings documented; any pattern gaps fed back as follow-up issues

Dependencies

Depends on (must close first): #(Issue 1 Stream A) · #(Issue 2 extended hook) · #(Issue 3 --content + skill + templates).

Notes

ha-victron-mpc chosen over spektiv (currently P0 trading restoration in flight — too risky to introduce content-rewrite tooling mid-fix) and over realign (already retrofit; would only validate idempotency, not first-application).

---

Part of plan .claude/plans/content-allocation-retrofit.md (item 4 — live validation). Depends on items 1, 2, 3 being closed first.