docs: machine B is agent-driven too — with a triple guard against team forgery - #574
Open
fujibee wants to merge 3 commits into
Open
docs: machine B is agent-driven too — with a triple guard against team forgery#574fujibee wants to merge 3 commits into
fujibee wants to merge 3 commits into
Conversation
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.
The CLI-first doctrine for machine B came from a real fear: an agent asked to "join team X" might create a fresh local team named X instead of pulling the remote one. Tonight's live cross-account test showed the other side of the trade: the CLI-only path was painful enough that the operator gave up on it, while the B-side agent — once taught — executed pull → digest check → unlock → join flawlessly, refused to let the identity into chat, and flagged a leftover world-readable secret unprompted.
So machine B's main path becomes agent-driven, matching machine A, and the fear is answered with an explicit triple guard in SKILL.md and all nine templates: joining a server-side team must NEVER go through join/create; it always goes through
remote pull; and if an unconnected local team with the same name already exists, stop and ask the user. The raw CLI walkthrough stays as Reference.Template slices hash-identical across nine types; registry/template suites 19/19 green.
PR opened on the author's behalf — their sandbox blocks GitHub access.