[indykish]

Explain how the fleet chat model selector saves the model for future chat, webhook and scheduled runs. Update recovery instructions, Run details, and the header Save changes action.

Companion implementation: agentsfleet/agentsfleet#785.

Session notes 1

The running guide now covers confirmed model changes in Chat and Activity, preserved unsent input, and recovery after an unsuccessful save. Authoring, Slack and approvals instructions point to the fleet header. The new changelog entry includes the API-client migration instruction for the removed needs_re_review field; prior entries are unchanged.

Review

No remaining findings. Native review and the final document-release audit checked all five changed pages against the implementation. Corrected two stale setup-footer instructions and changed the Run label to Run details. The new entry has 93 prose words and four bullets; Documentation rule 43 was applied without a budget exception.

Make

Local verification:

• bun run orly gate pr — exit 0; clean and pushed branch, changed prose clean, make lint exit 0. Evidence: /tmp/agentsfleet-chat-docs-pr-clean-final.log.
• make lint, run by the push hook and final gate — Documentation check passed; OpenAPI drift clean; Mintlify build validation passed; no broken links found. The hook also reported 25 documentation tests, all passing. Evidence: /tmp/agentsfleet-chat-docs-final-push.log.
• gitleaks protect --staged --redact --no-banner — exit 0, no leaks. Evidence: /tmp/agentsfleet-chat-docs-gitleaks-final.log.
• git status --short --branch -uall — clean and in sync with the feature branch on origin.
• orly-babysit-prs begins after this PR is created; Continuous Integration (CI) and post-push bot review are pending.

Documentation

Status: current — all five selected documents match the reviewed product behavior; both prior save-location corrections are resolved.

Scope: read-only release audit against c15d991, covering the committed and working-tree bytes in candidate m234-docs-final-20261026-2. Reviewed changelog.mdx and the authoring, running, Slack and approvals how-to pages, plus documentation entry points and navigation. Candidate HEAD 601b8b1 and all five selected hashes match.

Documentation health:

• README.md — Current; documentation entry points remain accurate for this scope.
• CONTRIBUTING.md — Current; no contributor workflow change.
• AGENTS.md — Current; documentation, changelog and concision rules followed.
• docs.json — Current; reviewed pages remain reachable through site navigation.
• changelog.mdx — Current; 93 prose words and four bullets, required API-client upgrade action inline, history unchanged.
• fleets/authoring.mdx — Current; saved-fleet editing and Save changes location match source.
• fleets/running.mdx — Current; future chat/webhook/scheduled model scope, preserved input, confirmed notices, recovery labels and Run details match source.
• fleets/slack.mdx — Current; Save changes correctly points to the fleet header.
• fleets/approvals.mdx — Current; Save changes correctly points to the fleet header.

Documentation coverage:

Changed surface	Reference	How-to	Tutorial	Explanation
Saved model for future runs	Changelog and running	Running	None	Running and authoring describe future work and existing runs
Confirmed model notices and preserved input	Changelog	Running	None	Running
Model-save recovery	Running	Running	None	Running
Run details and header save action	Changelog	Running, authoring, Slack and approvals	None	None
needs_re_review removal	Changelog	Inline Upgrading action to remove client checks	None	Current readiness checks remain; CLI decoder supports separate upgrades

Coverage debt: no zero-coverage or reference-only gaps remain in the audited changed surface. Existing how-to pages and inline upgrade instructions cover these incremental changes; no new tutorial is required. Configured documentation product_version 0.65.0 is preserved separately from the product binary version.

Diagram drift: no architecture documents or Mermaid/ASCII diagrams affected by this change were found. No diagram drift identified.

Confidence Score: 5/5

The documentation changes appear safe to merge.

Summary

Documents saved fleet models and updated chat controls.

• Fleet chat explains how model choices apply to future runs.
• Chat replies keep their text, and Run details show usage.
• Setup instructions put Save changes in the fleet header.
• The changelog tells API clients to drop the removed review field.

No actionable issues were established.

_{Reviews (1) · Last reviewed commit: "docs: correct setup save locations and A..." · Reviewed by Greptile}