check / check (push) Waiting to run
The warning for a config file that others can read always said the file contained S3 credentials, so a file:// config with none got a false claim. It now names them only when s3.access_key_id or s3.secret_access_key is set, and otherwise says the file is readable by others. snapshot purge wrapped the listing error, which already starts with "listing remote snapshots:", in that prefix a second time. syncWithRemote now returns it unwrapped, as CleanupLocalSnapshots does. Judgement call: a credential pulled into the config through smartconfig substitution counts as set by the file. Model: opus-5-5