Skip to content

docs: update fleet setup chat guides - #224

Merged
indykish merged 2 commits into
mainfrom
chore/m230-setup-chat-recovery-changelog
Oct 23, 2026
Merged

indykish merged 2 commits into
mainfrom
chore/m230-setup-chat-recovery-changelog

Conversation

@indykish

@indykish indykish commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Session notes 1

Combined both setup-chat documentation worktrees into one seven-file change.
The guides match the merged recovery and editor behavior; changelog labels use the product PR merge dates.

Fleet conversation
  ├─ Edit setup → private setup chat beside conversation
  │                  └─ Save changes → new runs use saved setup
  └─ Recent → fleets + unsaved setup chats

No product UI source changed, so this docs-only PR has no UI screenshot.

Review

P2 fleets/authoring.mdx:73 Recent implied saved chats appear in the sidebar. FIXED — the page now says unsaved setup chats.
P2 fleets/authoring.mdx:79 Rename omitted unresolved provider usage. FIXED — the page names pending usage checks.
Final adversarial pass: No findings. The Oct 21 and Oct 23 changelog labels match merged PRs #779 and #783.

Make

  • bun run orly gate verify — exit 0; docs language clean, 25 documentation tests passed, OpenAPI drift clean, Mintlify build validated, no broken links.
  • git diff --check — exit 0.
  • gitleaks protect --staged — exit 0; no leaks found.
  • gstack-gate-diff main — exit 0; listed=0, eligible=0, inspected=0, unread=0.
  • gstack-banned-terms check --base main — exit 0; no banned-terms file configured.
  • gh pr view 779 --repo agentsfleet/agentsfleet — exit 0; merged 2026-10-21T03:55:06Z.
  • gh pr view 783 --repo agentsfleet/agentsfleet — exit 0; merged 2026-10-23T02:53:07Z.
  • bun run slop:diff origin/main — unavailable; the docs repo has no slop:diff script.
  • bun run orly gate pr — pre-push exit 1; its only red item was git.pushed, which required the reviewed commit on the remote. The remote branch now points to the reviewed commit. No post-push gate was run per the user's instruction.
  • orly-babysit-prs — not run; no post-push polling per the user's instruction.

Session notes 2

Aligned the authoring error reference with the recovery guide. UZ-AUTHOR-008 now covers rejected credentials; UZ-AUTHOR-015 directs users to stop the uncertain reply before sending again and notes the accounting hold; UZ-AUTHOR-016 explains that accounting is resolved and a new message can retry.

Review

Greptile P2 fleets/authoring.mdx:61-65: FIXED in 7a19f33. The error-code advice now matches the authoring guide and runtime recovery behavior.
Adversarial review of the PR diff: no findings.

Make

  • orly gate verify — pre-push exit 0; docs language, make lint, 25 documentation tests, OpenAPI drift, Mintlify build, and broken-link checks passed.
  • Commit hooks — 25 tests passed and documentation check passed.
  • git diff --check — exit 0.
  • gitleaks protect --staged --redact — no leaks found.
  • Adversarial review — no production-facing documentation defects found.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; the previous recovery-guidance mismatch is fixed.

Summary

Updates the fleet guides for setup chats beside the conversation.

  • Fleet guides now show setup editing beside the conversation.
  • Setup guides explain how to recover from uncertain replies and rejected keys.
  • The fleet overview names the schedule fields the API returns.

No new actionable issues were found in the changes since the previous review.

Reviews (2) · Last reviewed commit: "docs: align authoring error recovery gui..." · Reviewed by Greptile

Comment thread fleets/authoring.mdx
@indykish
indykish merged commit d926f66 into main Oct 23, 2026
4 checks passed
@indykish
indykish deleted the chore/m230-setup-chat-recovery-changelog branch October 23, 2026 07:06
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