Check out profiles, vm, nexus, and deploy on allod-dev #4

New issue

Closed

opened 2026-07-16 15:00:51 +01:00 by allod-agent · 0 comments

allod-agent commented

2026-07-16 15:00:51 +01:00

Member

Add the four framework repos to the allod-dev inventory so agent sessions on the dev VM have the framework source checked out under ~/work/allod. This registers them in scripts/repositories.json and adds them to allod-dev.repos in flake.nix, with the derived scripts/vm-specs.json regenerated.

While here, normalize the two legacy registry aliases that predate the allod/ convention — workspace-tools -> allod/tools and strategy -> allod/strategy — so every alias matches its remote/checkout. Keys only; remote/checkout values (and on-disk checkout paths) are unchanged.

self_rebuild stays false: these are working checkouts, not a self-rebuild dependency.

The profiles, vm, nexus, and deploy framework repos are now published publicly under the allod org, but allod-dev's checkout list predates them and still pulls only tools, strategy, secrets, inventory, and memory. Add the four framework repos to the allod-dev inventory so agent sessions on the dev VM have the framework source checked out under ~/work/allod. This registers them in scripts/repositories.json and adds them to allod-dev.repos in flake.nix, with the derived scripts/vm-specs.json regenerated. While here, normalize the two legacy registry aliases that predate the allod/<repo> convention — workspace-tools -> allod/tools and strategy -> allod/strategy — so every alias matches its remote/checkout. Keys only; remote/checkout values (and on-disk checkout paths) are unchanged. self_rebuild stays false: these are working checkouts, not a self-rebuild dependency.