M5b: drop the vestigial profiles alias from the forge-ssh-key fixture #16

Merged

vnprc merged 1 commit from agent/nexus-drop-vestigial-profiles-fixture into master

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

allod-agent commented

2026-07-17 23:08:21 +01:00

Member

Part of the archetypes/profiles repo split — Refs allod/strategy#18. This is M5b, the non-cliff nexus cleanup in the final sweep.

forge-ssh-key resolves the deploy checkout for its lock-bump steps (not profiles) since G1c, so its test fixture registry's profiles → allod/profiles alias was vestigial — dead fixture data that no longer matched what the script resolves. Rename it to the deploy alias it actually resolves.

This removes the last non-definitions allod/profiles reference from nexus. The remaining nexus hits all legitimately mean the new definitions repo or test still-valid paths:

scripts/bootstrap-vm-from-host.sh — the sanctioned optional profile-hook lookup (resolve_checkout profiles … allod/profiles), which points at the definitions checkout.
tests/bootstrap-orchestration.sh — exercises that bootstrap hook.
tests/registry-resolver.sh — unit-tests resolve_checkout profiles, which bootstrap still uses.
tests/provisioning-contract.sh — health-check sample repo; allod/profiles is a real repo the dev VM now clones (post-M5a).

Risk

R1 Low — a test-fixture rename with no runtime surface. The fixture entry is overridden by DEPLOY_CHECKOUT in the test, so it is inert; straight revert.

Validation

git grep allod/profiles tests/forge-ssh-key.sh   # empty
nix flake check                                  # full provisioning suite green (forge-ssh-key + all others)

Part of the archetypes/profiles repo split — `Refs allod/strategy#18`. This is **M5b**, the non-cliff nexus cleanup in the final sweep. `forge-ssh-key` resolves the **deploy** checkout for its lock-bump steps (not `profiles`) since G1c, so its test fixture registry's `profiles` → `allod/profiles` alias was vestigial — dead fixture data that no longer matched what the script resolves. Rename it to the `deploy` alias it actually resolves. This removes the last non-definitions `allod/profiles` reference from nexus. The remaining nexus hits all legitimately mean the new definitions repo or test still-valid paths: - `scripts/bootstrap-vm-from-host.sh` — the sanctioned optional profile-hook lookup (`resolve_checkout profiles … allod/profiles`), which points at the definitions checkout. - `tests/bootstrap-orchestration.sh` — exercises that bootstrap hook. - `tests/registry-resolver.sh` — unit-tests `resolve_checkout profiles`, which bootstrap still uses. - `tests/provisioning-contract.sh` — health-check sample repo; `allod/profiles` is a real repo the dev VM now clones (post-M5a). ## Risk R1 Low — a test-fixture rename with no runtime surface. The fixture entry is overridden by `DEPLOY_CHECKOUT` in the test, so it is inert; straight revert. ## Validation ``` git grep allod/profiles tests/forge-ssh-key.sh # empty nix flake check # full provisioning suite green (forge-ssh-key + all others) ```

allod-agent added 1 commit

2026-07-17 23:08:21 +01:00

Drop the vestigial profiles alias from the forge-ssh-key test fixture 1b1b8abc11

forge-ssh-key resolves the deploy checkout (not profiles) since G1c, so its test
fixture registry's profiles->allod/profiles alias was dead. Rename it to the
deploy alias it actually resolves, removing the last non-definitions allod/profiles
reference from nexus. The entry is overridden by DEPLOY_CHECKOUT in the test, so
this is inert; the forge-ssh-key suite stays green.