08-Nov-2026 — estate deploy visibility, Fly cutover cert wait, deploy-all width #353

build 1073 — commit 67ea247

On Environment Settings → Details, each environment has an Include in estate deploys checkbox. When it is on, that site is in deploy-to-all; when it is off, it is skipped. Unset is treated as on, matching how deploy already behaves.
After a Fly organisation cutover, the Fly.io section shows the previous organisation, app name and when it was captured. That line is read-only and clears when the cutover finishes.
The Sites directory (and the capture spreadsheet) include Fly organisation and Estate deploy columns so you can see which sites are in the estate deploy set without opening Mongo.
If Environment Settings fails to load or save, the banner uses the standard alert panel with an icon and a title, instead of a plain red strip.
Moving a site to another Fly organisation no longer requests a certificate for the temporary cutover app. The public hostname (https://{group}.ngx-ramblers.org.uk) is attached once, on the final app, with ACME and ownership DNS in place, and the job waits until that certificate is issued and the public URL responds. If it does not, the move is reported as failed.
Deploy-to-all now runs up to 12 environments at a time (was 6).