Repository navigation
docs: explain checkpoint recovery and runner cordons - #254
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runner failures need clear guidance on what is restored, what can repeat, and how an operator inspects a quarantined host. Add a recovery guide, link it from the runner reference, and add a coming-soon changelog entry for product 0.78.0.
Session notes 1
Document automatic checkpoints, replacement attempts, retry exhaustion, recovery limits, and runner cordon inspection and removal.
The implementation is on agentsfleet/agentsfleet:feat/m247-checkpoint-respawn; its companion PR will be linked when published. This documentation marks the feature coming soon. Generated API reference updates follow the implementation merge.
Base:
751f49a1cc2ad1842453bd4deb530b840af7d607; reviewed and pushed head:c503304424bb8a07b27edd127d77abbc938bba39. Historical changelog entries are unchanged. No live product acceptance, human recovery test, paid provider run, or formal verification is claimed.Review
No remaining findings. The full-candidate gstack review and an independent Orly standards review cover all three changed files.
c729a657abed68718f2ee3efa41dda43773487fd, core receipt903d6917-d02c-4552-9ed7-a0a8fbf78031, native receiptcf03c0bd-528b-4ffd-aa67-1ad521b2cb10; completed, converged, no edits in the final pass. Report:/tmp/m247-docs-gstack-final.5DUvDXhM/review.mdin the task environment.runners/recovery.mdx: storage prerequisite incorrectly covered only file transfers. FIXED: durable tasks and file restoration both require private object storage; ordinary API-only checkpoints use encrypted PostgreSQL state.runners/recovery.mdxis FIXED: document three ordinary leases, the next-claim failure after exhaustion, and twelve default cumulative task leases with continuation stopping on exhaustion.Make
Local results on this candidate:
bun run orly doctor— exit 0; installed rules match and commands are declared.gitleaks git --redact --no-banner --no-color— exit 0; 744 commits scanned, no leaks. Log:/tmp/m247-docs-history-gitleaks.log.gitleaks git --staged --redact --no-banner --no-color— exit 0; 5.57 KB scanned, no leaks. Log:/tmp/m247-docs-staged-final-gitleaks.log.bun run orly gate work— exit 0; 25 tests, OK. Log:/tmp/m247-docs-final-work-gate.log.bun run orly gate prafter the feature push — exit 0; clean tree, pushed head, documentation prose,make lint, Mintlify compilation, and links passed. Log:/tmp/m247-docs-final-pr-gate-retry.log.751f49a1cc2ad1842453bd4deb530b840af7d607. Branch CI and Greptile are pending at publication; follow-up will record their outcomes.Session notes 2
Limit recovery guidance to platform runners.
Owner: "I think complete M247 for platform runners, park tenant runners", followed by "go". Tenant-runner placement, credential boundaries and acceptance are parked until that stream resumes.
Pushed head:
e23ec5710d67a60c3cfe2b3be4bab5815a41153e; local HEAD and upstream match and the docs tree is clean. The implementation PR remains pending while production-boundary tests are completed.Review
No findings remain on full candidate
6d3cbf2e764a37c1b09f3b0c1764e000bd6d96e5abovec503304.71f95cf7-8818-4ed0-a111-12e5fdc09a8e, native6ea2d65a-c675-4a99-bf31-65afdc09431f. Both prior storage/retry-limit findings remain fixed. Report:/tmp/m247-docs-gstack-platform.WfyWAIGg/review.md.Make
/tmp/m247-docs-platform-staged-gitleaks.logand/tmp/m247-docs-platform-commits-gitleaks.log.bun run orly gate work— exit 0, 25 tests, OK;/tmp/m247-docs-platform-work-gate.log.bun run orly gate prafter push — exit 0; clean/pushed branch and fullmake lintpassed: prose, OpenAPI drift, Mintlify compilation and links;/tmp/m247-docs-platform-pr-gate.log.

Confidence Score: 5/5
The documentation changes appear safe to merge.Summary
Adds coming-soon guidance for recovery after a platform runner fails, including saved progress, retry limits, and automatic quarantine.
No actionable new issues were found. Review was limited to documentation and available local sources; product behavior was not tested.
Reviews (6) · Last reviewed commit: "docs(runners): link shipped account APIs..." · Reviewed by Greptile