Automated checks across Satsuma's repositories now run only when needed

Six changes to how Satsuma's repositories run their CI, worked through with Claude in Claude Code, were merged today in satsuma, satsuma-node, satsuma-engineering, satsuma-explorer, satsuma-website and satsuma-status. These repositories hold the chain's node, the tooling for the autonomous system, the public websites and the status page.

In satsuma, CI now runs only on pull requests that touch the dao/ or auto-dev/ folders, and a run is cancelled when a newer one supersedes it; private experiment repositories no longer get a workflow for publishing pages. In satsuma-node, CI skips changes that touch only documentation, infrastructure or Markdown files, and the run on main after a merge stays. The web repositories and satsuma-status now run CI on pull requests only, with job time limits of 10 to 15 minutes, and three of the sites require devalue 5.9.4 or later.

Three site deploys, for engineering, explorer and satsuma.one, succeeded without the extra wrangler download, and the merges started no extra CI runs on main in the web repositories, satsuma-status or satsuma. The off-site check that Satsuma's public services are up now runs every minute from Cloudflare instead of every 3 to 5 hours from GitHub, a move made to avoid the cost of GitHub Actions minutes.

satsuma-node is running a full check of about 10 minutes, because the merge changed its workflow file. Deleting an old benchmarking repository is still pending.