Review generated lifecycle artifacts #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/review-generated-lifecycle-artifacts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes Allod/memory#1
Summary
Update shared Allod review and provisioning memory so future plan reviews do not stop at source-level Nix evaluation when a change affects NixOS, Home Manager, provisioning, systemd, or wrapper-script lifecycle behavior.
This is a direct process fix for the allod-dev first-build failure. The failure was not a Nix evaluation problem: the allod-dev toplevel built successfully. The bug was in a generated runtime artifact.
profiles/modules/netrc.nixusedexit 0when/root/.git-credentialswas absent. In a NixOS module,system.activationScripts.*.textsnippets are concatenated into one generatedactivatescript, so thatexit 0returned from the whole activation script. Activation stopped before the final/run/current-systemsymlink was created, andnixos-anywherelater tried to run/run/current-system/bin/switch-to-configuration, which did not exist. The VM disk was left partially installed and UEFI had no bootable system.Several reviews missed this because the review and acceptance-test guidance pushed reviewers toward structural consistency, closure scans, credential inventory checks, and
nix buildsuccess. Those checks were useful, but they did not require inspection of generated activation scripts or absent-resource paths such as a tokenless VM with no/root/.git-credentials. The rubric already classified the outcome as a blocker because it caused provisioning to fail and left the system nonfunctional; the missing piece was explicit coverage guidance.Changes
templates/plan-review-prompt.md: add a review guideline requiring generated lifecycle artifact inspection for NixOS, Home Manager, provisioning, systemd, and wrapper-script changes. The guideline explicitly calls out generated activation scripts, units, wrappers, install/boot phases, and negative paths for missing optional secrets, credentials, files, or host state.templates/plan-review-prompt.md: extend the blocker rubric so first boot, activation, provisioning, rebuild, and rollback lifecycle breakage is classified as[BLOCKER]instead of being softened into a generic test gap.dev-plans.md: strengthen Acceptance Tests guidance so plans must include generated-artifact and absent-resource checks when lifecycle-generating systems are involved, not only source evaluation or happy-path builds.dev-plans.md: addGenerated lifecycle behavioras a standing review focus area alongside consistency, sequencing, acceptance coverage, and rollback fidelity.vm-provisioning.md: replace the ambiguous activation-script "early exit" guidance with a NixOS-specific rule: use a conditional no-op for missing optional resources and do notexit 0from activation snippets, because snippets are concatenated and exiting aborts the whole activation before/run/current-systemis linked.Validation
Read-only review pass: no findings.
Checked the final diff against the allod-dev provisioning failure mode. The template now forces reviewers to inspect generated lifecycle artifacts and negative paths, the dev-plan guidance makes those checks part of acceptance testing, and the provisioning memory no longer recommends an ambiguous early-exit pattern for NixOS activation snippets.
Validation run locally: