Repository navigation
docs: match fleet setup recovery and dashboard controls - #225
Merged
Merged
Conversation
indykish
marked this pull request as ready for review
October 23, 2026 18:08
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.
Fleet setup and dashboard documentation now matches the companion product changes on
fix/approved-fleet-chat.This is a draft companion review; merging it publishes the documentation site.
Session notes 1
Updated authoring, runtime recovery, connector status, secret references, billing labels, and the changelog.
Loading and command-line authorization remain proposal-only. The long product acceptance runs have not passed and are planned for the development deployment.
The authoring page covers manual edit conflicts, save placement, and private unfinished setups. Recovery pages explain partial replies, retry availability, and possible additional charges.
Connector documentation distinguishes offered providers, saved connection data, and Request access. Billing documentation uses Model, Usage, and Occurred.
Review
No findings in the source-backed documentation review. Checked the changed instructions against the product branch's setup editor, lifecycle controls, connector components, secret dialog, and billing cells.
Applied Documentation (DOC) rules DOC-02, DOC-03, DOC-06, DOC-10, DOC-11, and DOC-43. Preserved existing changelog history.
The deleted temporary precheck configuration is absent from this change. Repository checks use
orly.Make
Local documentation checks:
bun run orly gate workmake test: 25 tests, documentation check passed.bun run orly gate verifymake lintpassed.bun run orly gate prgitleaks git --staged --redact --no-bannermake lintchecked the documentation rules, OpenAPI drift, Mintlify build, broken links, and Markdown links.These local results do not establish product acceptance. Post-push checks and review feedback are monitored with the repository's
orly-babysit-prsworkflow.

Confidence Score: 5/5
The reviewed changes appear safe to merge; both previous findings are addressed.Summary
Updates fleet setup, recovery, connector, secret, and billing documentation to match the companion dashboard changes.
Reviews (2) · Last reviewed commit: "docs: correct setup directions and expla..." · Reviewed by Greptile
Session notes 2
Upgraded the repository to Orly 0.17.0 and corrected dashboard paths for new drafts, saved-fleet edits, and connector setup.
Retry guidance now warns that a new run can repeat a completed outside-service action. This PR is ready for review; product acceptance remains pending on api-dev.
Review
P2
fleets/authoring.mdx:38— related pages disagreed about editor and connector controls. FIXED in7e49bce; new drafts use the chat menu, while saved fleets use the inline editor.P2
fleets/running.mdx:127— retry guidance omitted repeated outside-service actions. FIXED in7e49bce; the warning preserves the separate idempotent Resend behavior.The source-backed follow-up review found no remaining issue in these corrections. Greptile's current-revision summary confirms both findings are addressed, with 16 files reviewed and zero new comments. Both original threads have fix replies and are resolved.
Make
Local, Orly 0.17.0:
bun run orly gate work(commit hook)bun run orly gate verifybun run orly gate prgitleaks git --staged --redact --no-bannerbun run orly --versionand registrybun pm view @agentsfleet/orly versionCI on
7e49bce266bdfc021af45f9e4db1cd7fde104981: lint and gitleaks succeeded. Greptile check120585233942completed successfully and reports “16 files reviewed, 0 comments added.” The PR summary names this exact reviewed commit. Branch Mintlify deployment is skipped.orly-babysit-prsis completing its second quiet poll before the user-authorized merge. Product live acceptance is separate and remains unpassed.