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
Every repo carries every required caller-stub shim, pinned to its agent's moving major-scoped channel @<agent>/v<M>-stable, so a new reusable version reaches the whole fleet by a canary tag move — never a redeploy. Placement and drift-correction are fully automated by the existing systems; no manual deploy-standard-workflows.sh runs and no admin-merge.
Principle
The 2026-07-21 rollout (#844/#847) was hand-driven (manual sweeps, --admin, quarantine). That fought the systems. The version+channel model + canary rollout + compliance audit already exist; the gaps are two missing automation pieces (a deployer and an auto-merge path). Improve the systems; do not supersede them.
Dependency DAG
graph LR
B["#852 · B: standards-sync auto-merge<br/>(bootstrap: 1× admin-merge)"]
I["#849 · templates → v<M>-stable + audit pin-check"]
A["#851 · A: automated deploy driver"]
D["#856 · D: SKIP_REPOS opt-in + repo-template exemption"]
E["#857 · E: fleet convergence (via automation)"]
B --> I
B --> A
B --> D
I --> A
I --> D
A --> E
D --> E
B --> E
Loading
Sequencing (phased — minimizes bootstrap to a single admin-merge)
Audit reports 0 missing + 0 wrong-channel findings fleet-wide; ContentTwin bats passes against the deployed stub; no manual runs
Bootstrap note (approved): only #852 needs an admin-merge (you can't auto-merge the fix that creates auto-merge). Once #852 lands, #849/#851/#856 auto-merge through the system, and #857 runs entirely on the automation.
Epic-level acceptance (rollup)
A reusable version cut reaches the fleet by a canary tag move alone (no shim redeploy) — spot-checked.
Goal
Every repo carries every required caller-stub shim, pinned to its agent's moving major-scoped channel
@<agent>/v<M>-stable, so a new reusable version reaches the whole fleet by a canary tag move — never a redeploy. Placement and drift-correction are fully automated by the existing systems; no manualdeploy-standard-workflows.shruns and no admin-merge.Principle
The 2026-07-21 rollout (#844/#847) was hand-driven (manual sweeps,
--admin, quarantine). That fought the systems. The version+channel model + canary rollout + compliance audit already exist; the gaps are two missing automation pieces (a deployer and an auto-merge path). Improve the systems; do not supersede them.Dependency DAG
Sequencing (phased — minimizes bootstrap to a single admin-merge)
standards-syncPR with green required checks merges through branch protection, no--admin@<agent>/v<M>-stable; audit flags any bare-tag/off-channel pinBootstrap note (approved): only #852 needs an admin-merge (you can't auto-merge the fix that creates auto-merge). Once #852 lands, #849/#851/#856 auto-merge through the system, and #857 runs entirely on the automation.
Epic-level acceptance (rollup)
--admin, no quarantine) after the [#850 B] Auto-merge standards-sync PRs through branch protection (resolve the reviewer deadlock — no --admin) #852 bootstrap.add-to-project-workflow.batsgreen against the deployed stub.Stories
Refs
#657 (major-scoped channels), #849 (templates), #847/#848 (SKIP_REPOS reconcile), #844 (required-everywhere).