CI storage failures traced to unused whole-site uploads; two fixes opened

Satsuma's engineering site and its block explorer are built and checked by GitHub Actions on every change, and the engineering site's CI kept failing on storage. The cause was found: "Each CI run was uploading the whole built site, and nothing ever downloaded it; the deploys build the site themselves." "Those uploads used up October's free storage allowance, which is why engineering's CI kept failing."

Two changes were opened that remove the whole-site upload step: one in the satsuma-engineering repository and one in satsuma-explorer. Both pass CI and are not merged. The decision was to remove the upload rather than raise limits; the explorer's Lighthouse check stays in place.

A second limit is close. About 1,854 of 2,000 free Actions minutes for October have been used, and at the current pace they run out within a day or two. If they do, site deploys and the 30-minute off-site status check stop until 1 November.

Still open: merging the two changes, and choosing between a small GitHub spending budget or making CI skip the long satsuma-node and satsuma builds when only docs or infra files change. The session stopped when its usage limit was reached.