cascading-fleet

You can propagate a wheelhouse template SHA to all fleet repositories by running a canonical cascade that updates every repo with worktree management, applying direct pushes or PR fallbacks to ensure consistent template landings across the fleet.

Registry-pin chain propagation ensures consistent dependency versions across your fleet. You need it when a registry pin chain requires updates across multiple repositories to maintain deployment consistency and configuration alignment.

Lockfile reconciliation after a cascade is handled automatically through postcascade steps that validate and fix lockfiles, ensuring dependency consistency across all fleet repositories once the template or pin propagation completes.

Yes, per-repo cascade execution supports git worktrees, allowing isolated repository updates during template or registry-pin cascades while maintaining safety guards and sentinel checks for each repository in the fleet.

When a direct push is blocked during a fleet cascade, the system automatically falls back to creating pull requests, ensuring the template or registry-pin changes still propagate to the target repository safely.

FLEET_SYNC gating uses sentinel guards to control and protect cascade execution per repository, preventing mid-loop crashes and ensuring safe propagation of template or registry-pin changes across the entire fleet.