You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Populate canary-rings.json with the 6 #482 reusables (registry is dev-lead-only → evaluate-all covers nothing else) #1036
#1026 fixed evaluate-all (P1) + client-id auth ✅ — verified live: the 02:38Z scheduled run minted the token via client-id and ran evaluate-all. But it only evaluated dev-lead, because standards/canary-rings.json contains only dev-lead. The 6 #482 reusables (rolled out manually via the now-retired bridge, never onboarded into the registry) are absent — so the automation cannot see or complete their rollout. This is the last thing blocking real fleet automation.
Add these 6 to canary-rings.json (host petry-projects/.github, cross-repo)
All share the same ring topology; use dev-lead's existing entry as the schema template (members/reusable/run_workflow/gate with #548 per-transition knobs). Rings:
at ring1; stable baseline is acec8959 (not 376a4fcb)
dependabot-automerge
…/dependabot-automerge-reusable.yml
dependabot-automerge.yml
at ring1
dependabot-rebase
…/dependabot-rebase-reusable.yml
dependabot-rebase.yml
at ring1; no .github-private caller → set soak_start_ring: ring0 (or equivalent)
pr-review-mention
…/pr-review-mention-reusable.yml
pr-review-mention.yml
at ring1; candidate is v2.1.1 (93bfca45); the pre-fix v2.1.0 loop failure predates its cut
Once added, the next evaluate-all will report all 7, and the 4 at ring1 can be carried to stable by command=promote.
Related (P2 follow-up, dev-lead-specific)
dev-lead's evaluate shows cum_fail=68 benign=0 → the benign_match allowlist is running but dev-lead's known-benign classes (#864 Dependabot-context dispatch; fix-review git-push-permission) aren't configured, so it stays BLOCKED. Add those classes to dev-lead's gate.benign (or equivalent) so it can advance. See #1005.
Issue:#1036 — Populate canary-rings.json with the 6 #482 reusables
Scope
Register the 6 #482 cross-repo reusables (host petry-projects/.github) in standards/canary-rings.json using dev-lead's entry as the schema template, so evaluate-all sees all 7 agents.
Per-agent notes about candidate SHAs / stable baselines (e.g. auto-rebase acec8959, pr-review-mention v2.1.1) are channel-tag (git) state, not registry fields — out of scope for this JSON change.
The P2 dev-lead benign classes are already present in the file — not re-touched here.
TDD: wrote 6 failing bats tests first (red), then implemented to green
Test Results
bats tests/canary_rollout.bats → 57/57 ok (was 51; +6 new)
ok 52 canary-rings.json: all 6 #482 reusables are registered (7 agents incl. dev-lead)
ok 53 canary-rings.json: each #482 reusable has host .github + right reusable path + run_workflow
ok 54 canary-rings.json: #482 reusables share the ring topology (next=.github-private, ring0=.github, ring1 pair, stable=*)
ok 55 orchestrator: resolve_members for a #482 cross-repo reusable (next=.github-private, ring0=.github, stable=*)
ok 56 canary-rings.json: #482 reusables carry the #548 per-transition gate knobs
ok 57 orchestrator: evaluate-all reports all 7 registered agents (dev-lead + the 6 #482)
bats tests/test_bootstrap_new_repo.bats → 18/18 ok (consumes the ring SoT; unaffected)
bash .dev-lead/scripts/dev-lead-lint.sh → all checks passed (shellcheck 85 files + agent frontmatter)
Files Changed
standards/canary-rings.json: registered the 6 feat: implement issue #398 — Compliance: secret_scanning_ai_detection #482 cross-repo reusables (agent-shield, dependency-audit, auto-rebase, dependabot-automerge, dependabot-rebase, pr-review-mention). Purely additive — the dev-lead entry is untouched.
Deliberate topology inversion (documented in a _topology_note): for these cross-repo reusables the reusable is hosted in petry-projects/.github, but the rollout is canaried in petry-projects/.github-privatefirst (next, order 0 — the caller-stub/automation repo), then the host (ring0). Members are written as literal repos (not the $host/$org_infra tokens) so the inversion is explicit and unambiguous.
dependabot-rebase has no .github-private caller → its next tier has zero callers, so the existing waive_sample_if_no_caller: true on next->ring0 waives the fresh sample (dwell-only) — i.e. the soak effectively starts at ring0, the "soak_start_ring: ring0 (or equivalent)" ask. No new field needed.
Out of scope (git/tag state, not registry): per-agent candidate SHAs / stable baselines (auto-rebase acec8959, pr-review-mention v2.1.1 93bfca45) live as channel tags — channel_commit derives them; the registry only defines topology + gate knobs.
Activity
don-petry commentedon Jul 3, 2026
Dev-Lead Implementation Plan
Issue: #1036 — Populate canary-rings.json with the 6 #482 reusables
Scope
Register the 6 #482 cross-repo reusables (host
petry-projects/.github) instandards/canary-rings.jsonusingdev-lead's entry as the schema template, soevaluate-allsees all 7 agents.Implementation Checklist
standards/canary-rings.json:agent-shield,dependency-audit,auto-rebase,dependabot-automerge,dependabot-rebase,pr-review-mentionhost=petry-projects/.github,reusable=.github/workflows/<name>-reusable.yml,run_workflow=<name>.ymlnext→.github-private(order 0),ring0→.github(order 1),ring1→TalkTerm+bmad-bgreat-suite(order 2),stable→*(order 3)gatewith feat: implement issue #545 — Compliance: non-stub-dependency-audit.yml #548 per-transition knobs (incl.waive_sample_if_no_caller: trueonnext->ring0, which coversdependabot-rebase's missing.github-privatecaller — the "soak starts at ring0" note)Tests to Write (tests/canary_rollout.bats)
resolve_membersresolves next→.github-private, ring0→.github, stable→*control.allow_pre_existingNotes on scope boundaries
acec8959, pr-review-mentionv2.1.1) are channel-tag (git) state, not registry fields — out of scope for this JSON change.benignclasses are already present in the file — not re-touched here.Test Command
bats tests/canary_rollout.bats(+bash .dev-lead/scripts/dev-lead-lint.sh)don-petry commentedon Jul 3, 2026
Dev-Lead: Implementation Complete
Plan Execution
standards/canary-rings.json(registry now holds 7 agents incl.dev-lead)host=petry-projects/.github,reusable=.github/workflows/<name>-reusable.yml,run_workflow=<name>.ymlnext→.github-private(0),ring0→.github(1),ring1→TalkTerm+bmad-bgreat-suite(2),stable→*(3)gatewith feat: implement issue #545 — Compliance: non-stub-dependency-audit.yml #548 per-transition knobs;next->ring0keepswaive_sample_if_no_caller: trueTest Results
Files Changed
standards/canary-rings.json: registered the 6 feat: implement issue #398 — Compliance: secret_scanning_ai_detection #482 cross-repo reusables (agent-shield,dependency-audit,auto-rebase,dependabot-automerge,dependabot-rebase,pr-review-mention). Purely additive — thedev-leadentry is untouched.tests/canary_rollout.bats: +6 tests covering registration, host/reusable/run_workflow, ring topology,resolve_members, feat: implement issue #545 — Compliance: non-stub-dependency-audit.yml #548 gate knobs, andevaluate-allreporting all 7 agents.Notes
_topology_note): for these cross-repo reusables the reusable is hosted inpetry-projects/.github, but the rollout is canaried inpetry-projects/.github-privatefirst (next, order 0 — the caller-stub/automation repo), then the host (ring0). Members are written as literal repos (not the$host/$org_infratokens) so the inversion is explicit and unambiguous..github-privatecaller → itsnexttier has zero callers, so the existingwaive_sample_if_no_caller: trueonnext->ring0waives the fresh sample (dwell-only) — i.e. the soak effectively starts atring0, the "soak_start_ring: ring0 (or equivalent)" ask. No new field needed.acec8959, pr-review-mention v2.1.193bfca45) live as channel tags —channel_commitderives them; the registry only defines topology + gate knobs.benignclasses): already present in the file (dependabot-context-dispatch,fix-review-git-push-permission) — left untouched, as it's a separate dev-lead-specific concern (Onboard dev-lead into Release_Manager automation (+ resolve ring1 no-signal blocker) #1005).benign_failure_classes(none known); the gate code handles absence via// [].evaluate-allwill now report all 7 agents; the 4 sitting atring1can be carried tostableviacommand=promote.feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…
feat(canary-rings): onboard the 6 #482 reusables into the registry (#…