Rebase allod/tools#136 (fleet-diff) onto current master #161

New issue

Closed

opened 2026-09-03 16:25:24 +01:00 by vnprc-agent · 1 comment

vnprc-agent commented

2026-09-03 16:25:24 +01:00

Contributor

fleet-diff — the tool in allod/tools#136 — needs to land on master (incl. the flake/fleet-diff file) before the two PATH changes that consume it can work. This issue tracks that gate and the needed rebase.

The problem

PR allod/tools#136 lives on branch agent/fleet-diff, branched from d6a0612. master has moved 37 commits past that base (including the Bash-to-Go migrations and everything since). The branch is stale and not mergeable as-is.

The same content exists here as a single clean commit directly on current master (local branch agent/fleet-diff-ready, test suite green): flake/fleet-diff (356 lines, now executable), tests/flake/fleet-diff.sh (423 lines, 83 assertions, all passing), plus both README updates. It is the rebase this PR needs, extracted onto the current base.

Why it gates other work

Two pending changes read flake/fleet-diff out of the pinned allod-tools input at build time:

allod/nexus — put fleet-diff on the host PATH (nix/home.nix).
allod/archetypes — put fleet-diff on dev-box PATH (modules/dev-home-shared.nix).

Neither can work until flake/fleet-diff exists on master in the allod-tools input they pin.

Acceptance

Rebase the fleet-diff content onto current master (or take the ready local rebase directly).
All 83 tests pass; the script passes writeShellApplication (shellcheck).
Merge allod/tools#136.
Then the consumer PATH changes may go in.

`fleet-diff` — the tool in allod/tools#136 — needs to land on `master` (incl. the `flake/fleet-diff` file) before the two PATH changes that consume it can work. This issue tracks that gate and the needed rebase. ## The problem PR allod/tools#136 lives on branch `agent/fleet-diff`, branched from `d6a0612`. `master` has moved **37 commits** past that base (including the Bash-to-Go migrations and everything since). The branch is stale and not mergeable as-is. The same content exists here as a single clean commit directly on current `master` (local branch `agent/fleet-diff-ready`, test suite green): `flake/fleet-diff` (356 lines, now executable), `tests/flake/fleet-diff.sh` (423 lines, 83 assertions, all passing), plus both README updates. It is the rebase this PR needs, extracted onto the current base. ## Why it gates other work Two pending changes read `flake/fleet-diff` out of the pinned `allod-tools` input at build time: - allod/nexus — put `fleet-diff` on the host PATH (`nix/home.nix`). - allod/archetypes — put `fleet-diff` on dev-box PATH (`modules/dev-home-shared.nix`). Neither can work until `flake/fleet-diff` exists on `master` in the `allod-tools` input they pin. ## Acceptance - Rebase the fleet-diff content onto current `master` (or take the ready local rebase directly). - All 83 tests pass; the script passes `writeShellApplication` (shellcheck). - Merge allod/tools#136. - Then the consumer PATH changes may go in.

vnprc-agent referenced this issue

2026-09-03 16:25:56 +01:00

Add fleet-diff: check which machines a change rebuilds against a declared expectation #136

vnprc-agent commented

2026-09-03 22:22:57 +01:00

Author

Contributor

Solved by rebasing allod/tools#136 onto master (branch now 0 commits behind, all 83 fleet-diff tests pass). Closing.

vnprc-agent closed this issue

2026-09-03 22:22:58 +01:00