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
5a7a48f: The fleet upgrades only in one deliberate whole-fleet run, and is watched between runs (A11-205, step 3 of 5; the decision is docs/adr/0001). fleet:patch is now a chain: pnpm run fleet:patch prints the plan (which box has nothing to upgrade and what each other box is missing), and fleet:patch -- --apply runs deploy.yml, then patch.yml one box at a time, then a read of EVERY box against deploy-pins.json, stopping at the first failure and naming the box. patch.yml takes its target only from the manifest (Windows release, build and exactly the manifest's KB through win_updates' accept_list; the newest build any box reports is no longer the target), refuses a box above the manifest by name and never rolls it back, installs the manifest's Node, NVDA and Edge and the display driver pin through the role's own task files, freezes again in always:, and ends by reading every box against the whole manifest. A new fleet:drift (src/fleet-drift.ts) reads every box's Windows build, Edge, NVDA and worker code against the manifest and names every difference (exit 3; a box that does not answer is unread, exit 4 when none does); fleet:freeze-schedule installs a11y-fleet-drift.timer, hourly and read-only, which writes runs/fleet-drift.json, and fleet:watch mirrors it to runs/fleet-drift-mirror.json for the chairman's announcement channel. A box that differs is out of capture: lab:job reads the workers it needs just before it dispatches and leaves a drifting one out of a whole-fleet pool as drift_excluded (a job that names one is refused, and a read that cannot be made refuses). The patch window's unit names are removed from the unit-drift derivation. Adds control's first ADR and the README sections on the deliberate upgrade.