List fleet-diff in the session tool inventory #48

Merged
vnprc merged 1 commit from agent/fleet-diff-inventory into master 2026-09-04 01:16:43 +01:00
Member

Adds one line to the tool inventory agents read at session start.

No machine changes; this repo is Markdown that agents read, not code that runs. What changes is that an agent looking for a way to check which machines a change rebuilds now finds one. What stays identical: every other entry, and every convention. What proves it: a one-line diff. If it is wrong, the line is inaccurate rather than harmful — revert it.

fleet-diff shipped in allod/tools#136 and is on the dev-box PATH (allod/archetypes#68) and the host PATH (allod/nexus#38). allod.md lists the tools a session actually uses, and agent-behavior.md opens by telling agents to check for a project tool before falling back to raw shell — a tool absent from the inventory fails that instruction silently.

The entry states the contract compactly, because the part worth knowing is not the flags but that a run without an expectation asserts nothing and exits 0. An agent that treats a report-only run as a passing gate has proved nothing, which is the one way this tool can mislead.

Deliberately not added: any rule requiring a fleet diff before particular merges. That is proposed in the strategy development-process brainstorm and has not been adopted, and memory records adopted conventions rather than proposals.

Risk

R0. One line in a documentation repo.

Validation

git diff --stat shows one file, one inserted line, nothing deleted. No other memory file mentioned fleet-diff before this — checked with a repo-wide grep, which is how the gap was found. The command shape in the entry matches the shipped --help output.

Adds one line to the tool inventory agents read at session start. No machine changes; this repo is Markdown that agents read, not code that runs. What changes is that an agent looking for a way to check which machines a change rebuilds now finds one. What stays identical: every other entry, and every convention. What proves it: a one-line diff. If it is wrong, the line is inaccurate rather than harmful — revert it. `fleet-diff` shipped in allod/tools#136 and is on the dev-box PATH (allod/archetypes#68) and the host PATH (allod/nexus#38). `allod.md` lists the tools a session actually uses, and `agent-behavior.md` opens by telling agents to check for a project tool before falling back to raw shell — a tool absent from the inventory fails that instruction silently. The entry states the contract compactly, because the part worth knowing is not the flags but that a run without an expectation asserts nothing and exits 0. An agent that treats a report-only run as a passing gate has proved nothing, which is the one way this tool can mislead. Deliberately not added: any rule requiring a fleet diff before particular merges. That is proposed in the `strategy` development-process brainstorm and has not been adopted, and `memory` records adopted conventions rather than proposals. ## Risk R0. One line in a documentation repo. ## Validation `git diff --stat` shows one file, one inserted line, nothing deleted. No other memory file mentioned `fleet-diff` before this — checked with a repo-wide grep, which is how the gap was found. The command shape in the entry matches the shipped `--help` output.
The tool shipped and is on both the dev-box and host PATH, but nothing an
agent reads names it, so it would not be reached for.
vnprc approved these changes 2026-09-04 01:16:30 +01:00
vnprc merged commit 4d1108649d into master 2026-09-04 01:16:43 +01:00
vnprc deleted branch agent/fleet-diff-inventory 2026-09-04 01:16:43 +01:00
Sign in to join this conversation.
No description provided.