Document storage mutation and PR validation safeguards

[BenCodez]

Summary

Strengthen existing AGENTS.md guidance with all eight requested safeguards:

• Audit the complete mutation family, overloads, and callers.
• Preserve dependent per-user mutation order and test blocked-worker interleavings.
• Distinguish task admission/cached predictions from confirmed persistence.
• Test rejection, cancellation, shutdown, and storage failure without false success.
• Give each worktree one Maven validation owner; isolate reviewer builds.
• Check inline threads, review bodies/outside-diff findings, and conversation comments.
• Require explicit user authorization before posting GitHub comments.
• Report readiness for the exact validated head, keeping local/CI/integration evidence separate.

Additional safeguards

• Confirm the change is needed on current master and check overlapping fixes/PRs; ask before implementing an unnecessary or questionable change.
• Validate reviewer/MEX claims and actual dependency contracts against current source and tests.
• Prefer the smallest complete root-cause fix without speculative abstractions.
• State predicted/queued/persisted/delivered/completed guarantee boundaries and report only coverage actually exercised.

Validation

• Documentation/instruction-only: AGENTS.md is the only changed file. Focused tests and Maven package are exempt under the repository's existing documentation-only rule; no source, tests, build configuration, workflows, or packaged resources changed.
• Complete diff manually inspected; git diff --check and staged whitespace checks passed.
• Fresh independent read-only review: No findings.

No runtime or configuration behavior changes.

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 11 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: e5a03102-fc5c-4f17-acd9-1dea3b85cc52

📥 Commits

Reviewing files that changed from the base of the PR and between 5271f58 and 164138e.

📒 Files selected for processing (1)

• AGENTS.md

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-10-02T00:11:16.315657Z	e8afe00	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.