Skip to content

docs(runners): correct checkpoint recovery rollout defaults - #256

Merged
indykish merged 5 commits into
mainfrom
chore/m247-runtime-settings-changelog
Nov 19, 2026
Merged

indykish merged 5 commits into
mainfrom
chore/m247-runtime-settings-changelog

Conversation

@indykish

@indykish indykish commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Document the environment-only recovery opt-in, its TOML precedence, and restarting daemon replicas after rollout testing. The upcoming-release documentation also explains runner-local TOML installation, all 13 settings and their bounds, and separate generation, token-count and retry budgets.

Session notes 1

  • Base: 709e1b7fe9c5da20252438360e04eb7de1a88c21; the branch contains this freshly fetched revision.
  • Base CI: https://github.com/agentsfleet/docs/actions/runs/44352167417 (secret scan passed). CI did not run documentation lint; an isolated checkout at that exact base passed make lint (exit 0).
  • Initial documentation correction was reviewed and verified at b5ae6a86c95c407183cddd158322d5de1687d5e1.

Session notes 2

  • Final reviewed and pushed head: 7e91d1716ce1daff8d214ff0e418fd54a2ce50d5.
  • Repaired Greptile comment4622647940: runners/recovery.mdx explicitly states AGENTSFLEET_RESUME_FROM_CHECKPOINT=true on every daemon replica, restart required, and selected TOML precedence. Replied and resolved the thread after confirming the pushed PR head.
  • Added the previously requested runner profile guide to this existing companion PR. Attempt counts include the first send; token counting remains separate; jitter and the final reconnect clamp are distinguished.
  • Core source is being prepared in agentsfleet/agentsfleet (current committed base 9f9798cd057e384fa556bd3b2030125c20e71661 plus the checked implementation working tree). This docs PR does not deploy or enable recovery. No live-installation claim is made.
  • The owner will perform the manual recovery exercise later. No new Orly rule change is proposed.

Review

  • gstack-review on the final head against 709e1b7: complete/current, native adversarial pass complete, 0 open findings, 25 focused documentation tests, 3/3 probes passed, 13/13 profile values matched. Token: 9b0bc81a-94f8-4599-9a9e-2c3ebe805606.
  • Independent read-only standards review on the same revisions: 0 findings across 62 applicable rules. Earlier findings about parameter bounds, setup steps and jitter were repaired and rechecked.
  • Limits: static documentation, actual core source and installed retry-library checks; no renderer, installation, live deployment or complete core-test proof is claimed. Optional outside-model tools were skipped; no Astra review is claimed.

Make

RetriggerView in GreptileConfidence Score: 5/5

The documentation changes appear safe to merge.

Summary

Documents checkpoint recovery as disabled by default and explains how operators enable it after testing.

  • Checkpoint recovery instructions now require an opt-in rollout.
  • The runner installation page explains how to set local profiles and their limits.

No new actionable issues found. The previous environment-only opt-in finding is fixed.

Reviews (2) · Last reviewed commit: "docs(runners): distinguish generation re..." · Reviewed by Greptile

Comment thread runners/recovery.mdx Resolved
@indykish
indykish merged commit 76bf878 into main Nov 19, 2026
4 checks passed
@indykish
indykish deleted the chore/m247-runtime-settings-changelog branch November 19, 2026 01:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant