sign-branch, branch-sweep: mint their own broker entries, not the board's - #143
Open
bdelanghe wants to merge 1 commit into
Open
sign-branch, branch-sweep: mint their own broker entries, not the board's#143bdelanghe wants to merge 1 commit into
bdelanghe wants to merge 1 commit into
Conversation
…rd's The first cross-repo dispatch (run 31233034996) failed at the mint preflight: the fan-in `front-desk` app carries organization_projects, issues, pull_requests, metadata — no `contents` at all. That is the preflight working (#87/#93), and the fix is the doctrine claim-ticket.yml already states: each window mints its own broker entry, and the board app must not grow a scope because one window needs it. So: `front-desk-sign` (sign-branch) and `front-desk-sweep` (branch-sweep), both requiring `contents`. Until the broker registry (infra) carries the two entries pinned to these workflows at refs/heads/main, cross-repo runs keep failing at mint naming the gap — the designed interim, same as claim-ticket before its entry landed — and same-repo runs are unaffected (the first same-repo dry-run sweep ran green on the workflow's own token). Co-Authored-By: Claude Opus 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
2 participants
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.
Follow-up to #142, from its first two live dispatches.
What the dispatches showed
Cross-repo mint fails on scope, exactly as the preflight is designed to (run 31233034996): the fan-in
front-deskApp grantsorganization_projects, issues, pull_requests, metadata— nocontentsat all. It's the board door; ref writes were never its scope. The claim-ticket doctrine already answers this: each window mints its own broker entry, and the board app must not grow a scope because one window needs it.Same-repo works end to end. The dry-run sweep of
.githubproduced the intended table — 11 candidates (allno open PR, tips June–early July), 4 kept for age or open PRs, nothing protected touched. Andsign-branch's already-verified guard fired correctly on its first dispatch.Change
app: front-desk→app: front-desk-sign/app: front-desk-sweep, bothrequire: contents, with the doctrine and the failing run recorded at the mint step. Until the broker registry (infra) carries the two entries pinned to these workflows atrefs/heads/main, cross-repo dispatches keep failing at mint, naming the gap — the same designed interim claim-ticket ran under before its entry landed. Same-repo dispatches are unaffected.195/195 tests pass.
What this unblocks, and what it still doesn't
branch-sweepon.github-private(prefix: tmp/) finally deletestmp/api-mode-probe, and the 30-day sweep becomes available org-wide./tmp/code-signshim signs locally, a capability discovered working mid-session after several avoidable laptop amends.)Generated by Claude Code