fix(agent): agent info reports the ENFORCED sudo grant beside the stored isolation label (DIVE-2079) - #207
Merged
Merged
Conversation
… (DIVE-2079) Release 0.16.14. Rebuilt on top of DIVE-2076 (0.16.13) by applying 2079's source delta onto main rather than taking whole files from the pre-merge commit — taking the files wholesale would have reverted 2076's TYPE_CHANNELS defaults in cmd_agent_create.sh. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
lodar
force-pushed
the
dive-2079-isolation-truth
branch
from
July 26, 2026 14:03
ae071a8 to
17b3b8f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
isolationin the registry is a stored label with nothing keeping it honest. The DIVE-1002 v1→v2 migration stampedisolation: "admin"on every pre-existing agent without reading what sudo each actually had, so three genuinely different privilege levels — legacy full(ALL) NOPASSWD: ALL, the narrowcli-rootgrant, and no grant — all rendered identically.agent infonow prints the measured grant beside the stored label and warns when they diverge.This one cost me two wrong fleet-wide instructions earlier today: I asserted
sudo -u claude ghworked across the fleet, was disproved, retracted to "nobody", and was disproved again. The label was the reason both readings looked defensible.Author: dev3. Verified at the effect level by olivia, who holds legacy
(ALL)sudo and so could close the root-branch gap dev3 had declared but couldn't reach:sudo ./5dive agent info devprintssudo: root-all - any command, no restriction; runas anyplus the DIVERGES warning, whileagent info dev2printscli-root; runas rootwith no warning. The two populations that used to read identically now read differently — which is the actual property, not the test count. She also confirmed non-vacuity by neutralizing the new function to its pre-fix answer: 5 reds, exit 1, no crash.Her ship blocker, addressed: the branch was unpushed and its base predated DIVE-2075, which also touches the built bundle — so the committed bundle+sha256 were stale against main. I pushed the original commit to origin untouched first (it existed on one disk), then rebased onto
1bb3b10and re-ran./build.sh; bundle and sha256 are regenerated and match (1d5adbe8).Release: 0.16.14, assuming #206 (0.16.13) merges first — I re-assert main's version immediately before merging, because four version collisions happened earlier today.
Known out of scope, flagged by olivia and now its own ticket:
agent liststill prints the label-only isolation column (src/cmd_agent.sh:118) with no measured grant. The filed defect namedagent infospecifically.🤖 Generated with Claude Code