Skip to content

docs: explain checkpoint recovery and runner cordons - #254

Merged
indykish merged 6 commits into
mainfrom
chore/m247-respawn-changelog
Nov 18, 2026
Merged

indykish merged 6 commits into
mainfrom
chore/m247-respawn-changelog

Conversation

@indykish

@indykish indykish commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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.

  • Gstack: candidate c729a657abed68718f2ee3efa41dda43773487fd, core receipt 903d6917-d02c-4552-9ed7-a0a8fbf78031, native receipt cf03c0bd-528b-4ffd-aa67-1ad521b2cb10; completed, converged, no edits in the final pass. Report: /tmp/m247-docs-gstack-final.5DUvDXhM/review.md in the task environment.
  • P2, 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.
  • Independent Orly standards review: no findings against 51 rules on the same candidate. Its earlier P2 DOC-21 finding in runners/recovery.mdx is FIXED: document three ordinary leases, the next-claim failure after exhaustion, and twelve default cumulative task leases with continuation stopping on exhaustion.
  • Static/source review and documentation validation only; no browser or product runtime acceptance. Greptile follow-up starts after publication.

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 pr after 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.
  • Prior gate attempt — exit 1 because the cloud clone fetched only main and did not map the pushed feature branch as an upstream. Added that branch's local fetch refspec, fetched it, verified equal local/upstream SHAs, and reran the gate. No repository gate or hook was changed.
  • Exact-base CI: gitleaks run 44050166829, success on 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 6d3cbf2e764a37c1b09f3b0c1764e000bd6d96e5 above c503304.

  • Fresh gstack review: completed/converged, four specialists and native no findings. Verified/CURRENT core 71f95cf7-8818-4ed0-a111-12e5fdc09a8e, native 6ea2d65a-c675-4a99-bf31-65afdc09431f. Both prior storage/retry-limit findings remain fixed. Report: /tmp/m247-docs-gstack-platform.WfyWAIGg/review.md.
  • Independent Orly standards recheck: no findings against 51 rules across all three files. Seven tooling/input hashes and fifteen source hashes matched. Gate-enforced rules excluded. Static review only; no live recovery, tenant-runner acceptance, paid provider or human smoke result is claimed.

Make

  • Staged and committed-range gitleaks scans — exit 0, no leaks; /tmp/m247-docs-platform-staged-gitleaks.log and /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 pr after push — exit 0; clean/pushed branch and full make lint passed: prose, OpenAPI drift, Mintlify compilation and links; /tmp/m247-docs-platform-pr-gate.log.
  • Exact-head GitHub checks: lint SUCCESS, gitleaks SUCCESS, Greptile Review SUCCESS. Mintlify Deployment SKIPPED. Inline-thread and late-review follow-up continues before handoff.

RetriggerView in GreptileConfidence 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.

  • The recovery guide explains how platform runs continue after a runner fails.
  • Operators can see why a runner is quarantined and when it returns.
  • Tenant runner endpoints appear together in API navigation.

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

@indykish
indykish merged commit 709e1b7 into main Nov 18, 2026
4 checks passed
@indykish
indykish deleted the chore/m247-respawn-changelog branch November 18, 2026 16:52
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