Make pi-integration follow machine memory checkouts #109

Merged

vnprc merged 1 commit from agent/pi-integration-memory-checkouts into master

2026-09-22 17:49:15 +01:00

allod-agent commented

2026-09-22 17:38:30 +01:00

Member

pi-integration now validates the memory adapter paths declared by the composed dev machine, so a deployment with one memory checkout passes while the builder's two-checkout default remains pinned by its own fixture. Running machine configuration and generated behavior are unchanged. The normal gate and the full fork-safety witness pass. Revert this PR if the check rejects valid deployment data after merge.

The shared adapter assertion derives each expected Claude, Codex, and system-prompt path from the selected machine's profile.memoryCheckouts, falling back to the builder default. The fork fixture declares only fork/memory, and its committed VM-spec projection carries the same setting, so a future return to template-default assumptions fails the fork witness.

Risk

R1 low. This changes check expectations and synthetic fixture data only. The main residual risk is a false positive or false negative in pi-integration; rollback is a straight revert.

Validation

Confirmed the new one-checkout fork fixture made the old check fail with ERROR: claude pointer missing allod/memory checkout.
./check.sh — all 32 steps passed, including 19 built checks.
./fork-safety.sh — all 19 checks built and passed against the synthetic fork data.

Closes allod/archetypes#108

`pi-integration` now validates the memory adapter paths declared by the composed dev machine, so a deployment with one memory checkout passes while the builder's two-checkout default remains pinned by its own fixture. Running machine configuration and generated behavior are unchanged. The normal gate and the full fork-safety witness pass. Revert this PR if the check rejects valid deployment data after merge. The shared adapter assertion derives each expected Claude, Codex, and system-prompt path from the selected machine's `profile.memoryCheckouts`, falling back to the builder default. The fork fixture declares only `fork/memory`, and its committed VM-spec projection carries the same setting, so a future return to template-default assumptions fails the fork witness. ## Risk R1 low. This changes check expectations and synthetic fixture data only. The main residual risk is a false positive or false negative in `pi-integration`; rollback is a straight revert. ## Validation - Confirmed the new one-checkout fork fixture made the old check fail with `ERROR: claude pointer missing allod/memory checkout`. - `./check.sh` — all 32 steps passed, including 19 built checks. - `./fork-safety.sh` — all 19 checks built and passed against the synthetic fork data. Closes allod/archetypes#108

allod-agent added 1 commit

2026-09-22 17:38:30 +01:00