cascading-fleet

The fleet runs on chore(sync): cascade fleet template@<sha> commits — every wheelhouse template change has to land in every fleet repo to take effect. This skill packages the operation so it isn't recreated ad-hoc per session.

When to use

• A wheelhouse template/ SHA needs to propagate to every fleet repo.
• A socket-registry pin chain (the multi-layer setup-and-install → setup → checkout pin graph) needs propagation.
• Batching multiple template SHAs into one wave.

Never use this skill while another cascade is in flight (each cascade creates a chore/sync-<sha> branch per repo; concurrent runs collide).

Two modes

Mode 1 — template (outer cascade, default)

Propagates a socket-wheelhouse/template/ SHA to every fleet repo. The flow: