M5a: register the allod/profiles definitions checkout #8

Merged

vnprc merged 1 commit from agent/inventory-add-profiles-definitions into master

2026-07-18 02:33:45 +01:00

allod-agent commented

2026-07-17 23:03:52 +01:00

Member

Part of the archetypes/profiles repo split — Refs allod/strategy#18. This is M5a, part of the final sweep: registering the new allod/profiles example-definitions repo now that it exists (M1).

Changes:

Add an allod/profiles registry entry (scripts/repositories.json) and add allod/profiles to allod-dev's repos list, alongside allod/archetypes — so a human editing the example machine definitions on the dev VM gets that checkout.
Regenerate scripts/vm-specs.json.

The framework checkout stays allod/archetypes (set at G1b); no provisioning default relies on allod/profiles for framework or deploy-flake behavior. This is purely the definitions checkout for humans who edit examples.

Risk

R2 Medium — mechanical registry/spec change; the vm-specs.json and repository-registry checks force consistency. Rollback is a straight revert that must re-regenerate vm-specs.json.

Validation

nix flake check                                                                # repository-registry + vm-specs-json green
jq -e '."allod-dev".repos | index("allod/profiles")' scripts/vm-specs.json      # PASS
jq -e '."allod-dev".repos | index("allod/archetypes")' scripts/vm-specs.json    # PASS (framework checkout unchanged)
jq -e '.repositories["allod/profiles"].remote == "allod/profiles"' scripts/repositories.json   # PASS

Part of the archetypes/profiles repo split — `Refs allod/strategy#18`. This is **M5a**, part of the final sweep: registering the new `allod/profiles` example-definitions repo now that it exists (M1). Changes: - Add an `allod/profiles` registry entry (`scripts/repositories.json`) and add `allod/profiles` to `allod-dev`'s `repos` list, alongside `allod/archetypes` — so a human editing the example machine definitions on the dev VM gets that checkout. - Regenerate `scripts/vm-specs.json`. The framework checkout stays `allod/archetypes` (set at G1b); no provisioning default relies on `allod/profiles` for framework or deploy-flake behavior. This is purely the definitions checkout for humans who edit examples. ## Risk R2 Medium — mechanical registry/spec change; the `vm-specs.json` and `repository-registry` checks force consistency. Rollback is a straight revert that must re-regenerate `vm-specs.json`. ## Validation ``` nix flake check # repository-registry + vm-specs-json green jq -e '."allod-dev".repos | index("allod/profiles")' scripts/vm-specs.json # PASS jq -e '."allod-dev".repos | index("allod/archetypes")' scripts/vm-specs.json # PASS (framework checkout unchanged) jq -e '.repositories["allod/profiles"].remote == "allod/profiles"' scripts/repositories.json # PASS ```

allod-agent added 1 commit

2026-07-17 23:03:52 +01:00

Add the allod/profiles definitions checkout for example editors 3844ec2c85

Now that the allod/profiles example-definitions repo exists, add it to the
registry and to allod-dev's repos list alongside allod/archetypes, so a human
editing the example machine definitions on the dev VM gets that checkout.
Regenerate vm-specs.json. No provisioning default relies on allod/profiles for
framework behavior; the framework checkout stays allod/archetypes.