dispatch build — warn + document --team-name on claude (auto-team is default; legacy shape is silent)#446
Merged
Conversation
…ild --help dispatch build is Claude-team-mode-aware: omitting --team-name on host=claude yields the auto-team shape, while passing it selects the legacy TeamCreate- registry shape. That opt-in was invisible (undocumented in --help) and silent (no warning), so a stray --team-name could emit the legacy envelope unnoticed. Add claudeteam.LegacyTeamNameAdvisory, fired from runBuildFields on !bareMode && host=="claude" && teamName!="" just before the envelope emit — after every error guard, so it warns only when the legacy envelope is actually emitted; an error build (no envelope) stays advisory-free. Stderr-only; the dispatch envelope is untouched. Document --host/--team-name/--bare-mode in printBuildUsage with wording aligned to the advisory. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
clkao
force-pushed
the
spacedock-ensign/dispatch-build-team-name-advisory
branch
from
June 30, 2026 19:44
d833cd5 to
1c0807d
Compare
clkao
added a commit
that referenced
this pull request
Jul 2, 2026
…ation (#462) The sonnet lane's speculative repo-root sniff cd's outside the fixture as a harmless version probe before settling on its (correct) launch cwd; the detector flagged ANY escaping cd as a wander, false-reding both PR #446 runs even though each finished the scenario correctly. A bare cd now reds only when the same command also carries a workflow-operative token (--workflow-dir, --boot, --discover, status --read, state commit, new, README/entity path); standalone --workflow-dir/README-read signatures are unaffected. Also rewords the failure text off the disproved CI-env-leak cause. Checks in the two archived PR #446 sonnet streams as replay testdata (both return nil post-fix; reproduced the exact CI failures pre-fix) alongside the four corroborated-wander fixtures (still 4/4 red). Co-authored-by: Spike Test <spike@example.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
Warn when
--team-namesilently selects the legacy dispatch shape on host=claude, and surface the shape-selecting flags in dispatch build --help.What changed
--team-nameis passed on host=claude (success path; the dispatch envelope is untouched).--host,--team-name, and--bare-modeindispatch build --help.--helpgolden; the legacy-envelope shape stays frozen.Evidence
--helplists the flags, envelope byte-unchanged); no existing assertion weakened.go test ./internal/dispatch/ ./internal/claudeteam/— all passed.0qt