G1b: re-point inventory framework checkout to allod/archetypes #7

Merged

vnprc merged 1 commit from agent/inventory-archetypes-checkout into master

2026-07-17 21:45:05 +01:00

allod-agent commented

2026-07-17 21:20:18 +01:00

Member

Part of the archetypes/profiles repo split — Refs allod/strategy#18. This is the G1b pre-cliff re-point.

The framework repo was renamed allod/profiles → allod/archetypes (M0). Inventory's machine repo lists and registry still name the framework allod/profiles, which currently resolves only through the dying rename redirect. This PR re-points the framework checkout to the full alias allod/archetypes so cold clones stop fetching the framework through that redirect before it dies when the new allod/profiles definitions repo is created (M1).

Changes:

allod-dev's repos list: allod/profiles → allod/archetypes.
Registry entry allod/profiles → allod/archetypes (key, remote, checkout).
Regenerated scripts/vm-specs.json in the same PR so its check stays green.

The allod/profiles alias is intentionally removed here, not kept: the new definitions repo does not exist yet. M5a may re-add allod/profiles as the example-definitions checkout for humans who edit examples, but no provisioning default relies on it for framework behavior. The repository-registry check's self-rebuild required-alias list (profiles secrets inventory) is left alone — it tests bare names against full-name repo lists and no example VM sets self_rebuild = true, so it is inert.

Risk

R2 Medium — mechanical but provisioning-adjacent (it governs which repo cold clones fetch as the framework). Rollback before M1 is a straight revert; the redirect still serves the framework until then. The revert must re-regenerate vm-specs.json (the check forces this).

Validation

nix flake check                                                    # vm-specs-json + repository-registry both green
jq -e '."allod-dev".repos | index("allod/archetypes")' scripts/vm-specs.json        # PASS
jq -e '."allod-dev".repos | index("allod/profiles") | not' scripts/vm-specs.json    # PASS
jq -e '.repositories["allod/archetypes"].remote == "allod/archetypes"' scripts/repositories.json  # PASS
git grep allod/profiles                                            # no hits

Part of the archetypes/profiles repo split — `Refs allod/strategy#18`. This is the **G1b** pre-cliff re-point. The framework repo was renamed `allod/profiles` → `allod/archetypes` (M0). Inventory's machine repo lists and registry still name the framework `allod/profiles`, which currently resolves only through the dying rename redirect. This PR re-points the framework checkout to the full alias `allod/archetypes` so cold clones stop fetching the framework through that redirect before it dies when the new `allod/profiles` definitions repo is created (M1). Changes: - `allod-dev`'s `repos` list: `allod/profiles` → `allod/archetypes`. - Registry entry `allod/profiles` → `allod/archetypes` (key, `remote`, `checkout`). - Regenerated `scripts/vm-specs.json` in the same PR so its check stays green. The `allod/profiles` alias is intentionally removed here, not kept: the new definitions repo does not exist yet. M5a may re-add `allod/profiles` as the example-definitions checkout for humans who edit examples, but no provisioning default relies on it for framework behavior. The `repository-registry` check's self-rebuild required-alias list (`profiles secrets inventory`) is left alone — it tests bare names against full-name repo lists and no example VM sets `self_rebuild = true`, so it is inert. ## Risk R2 Medium — mechanical but provisioning-adjacent (it governs which repo cold clones fetch as the framework). Rollback before M1 is a straight revert; the redirect still serves the framework until then. The revert must re-regenerate `vm-specs.json` (the check forces this). ## Validation ``` nix flake check # vm-specs-json + repository-registry both green jq -e '."allod-dev".repos | index("allod/archetypes")' scripts/vm-specs.json # PASS jq -e '."allod-dev".repos | index("allod/profiles") | not' scripts/vm-specs.json # PASS jq -e '.repositories["allod/archetypes"].remote == "allod/archetypes"' scripts/repositories.json # PASS git grep allod/profiles # no hits ```

allod-agent added 1 commit

2026-07-17 21:20:19 +01:00

Re-point framework checkout to allod/archetypes efdcd5bcdc

The framework repo was renamed allod/profiles -> allod/archetypes (M0).
Re-point allod-dev's repos list and the registry alias to allod/archetypes
so cold clones stop fetching the framework through the dying rename redirect
before M1. Regenerate vm-specs.json to match.