[SaulBuilds]

Tests only.

What

• execution: executor_reuses_the_persisted_nonce_after_a_restart. After a restart before the commitment lands, the executor must commit to the nonce already persisted for the job.
• supervision/auth: read_existing_token_refuses_a_file_owned_by_another_uid. It uses a root-owned system file and only stats and reads it, never writes. It's skipped when the test runs as that file's owner.
• executor: tests/weight_body_cap.rs, using loopback servers:
  • a declared Content-Length over the cap is refused before the body is read;
  • a chunked body with no length is refused once it passes the cap;
  • a body within the cap is returned.

Standard: met

• Revert check: each of these was green under the existing suite and now turns its named test red: ignoring the persisted nonce, dropping the uid comparison, removing either weight-body cap.
• Other guards: I revert-checked 17 more (outbound timeouts and no-redirect, job input cap and its FIFO/symlink/regular-file gates, seal replica binding, model-hash binding, token symlink refusal, bid supersede and queue cap, minted-nonce use, the committed-without-nonce abort, the bearer gate, /health redaction). Each is already red under an existing test.
• Checks: cargo test -p node-agent -p supervision -p executor green.
• Pre-existing on main, not touched here: cargo fmt --check reports diffs across most files with rustc 1.93, and clippy -D warnings fails in the config crate.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KGMeatV8UjtCB4CTbWuAv4

[BerryManifold]

Automated Codex static review of b94fdc2c211535ecec98508d2bb5631f10799211 is complete. Result: incomplete; details retained privately. Details and coverage limits are recorded in the project's private review log. No tests were executed by this reviewer. Both account submissions represent the same Codex review, not independent reviews.

[Matr0xshka]

Automated Codex static review of b94fdc2c211535ecec98508d2bb5631f10799211 is complete. Result: incomplete; details retained privately. Details and coverage limits are recorded in the project's private review log. No tests were executed by this reviewer. Both account submissions represent the same Codex review, not independent reviews.