docs(m131): fleet console, memory, and run cost#141
Merged
indykish merged 2 commits intoJul 16, 2026
Merged
Conversation
indykish
merged commit Jul 16, 2026
bc24d71
into
chore/m130-catalog-row-edit-changelog
3 checks passed
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.
Summary
If-Matchprotection for fleet and catalog editsVerification
make testnpx mintlify validatenpx mintlify@4.2.698 broken-linksgitleaks detectSession notes
This Pull Request is stacked on #140 because the Fleet library page needs M130's catalog editing and draft/publish corrections before M131's stale-write guidance applies.
The aggregate
make lintreaches the OpenAPI drift check and reports 13 operations already absent fromdocs.jsonon upstreammain. The four-file M131 diff introduces none of those operations.Greptile Summary
This PR documents M131's fleet detail console, adding source editing, memory forget, run cost, and stale-write protection (
If-Match/ 412) across four pages. The Jul 16 changelog entry, fleet overview, library, and memory pages are all mutually consistent.DELETEAPI route with both the204success andUZ-MEM-004absent-key responses, closing the gap noted in the prior review round.Jul 16, 2026<Update>entry covers all four features with correct HTTP header casing (ETag) and consistent error codes throughout.Confidence Score: 5/5
Documentation-only change; all four pages are internally consistent and no functional code is modified.
The changes are pure documentation. Error codes, API paths, and behavioral descriptions match across changelog, overview, library, and memory pages. Issues flagged in the prior review round (stale-write guidance in overview, UZ-MEM-004 in memory) are addressed. No cross-file contradictions or missing information found.
No files require special attention.
Important Files Changed
Sequence Diagram
%%{init: {'theme': 'neutral'}}%% sequenceDiagram participant Op as Operator (Dashboard) participant API as agentsfleet API participant Fleet as Fleet Note over Op,Fleet: Source edit with stale-write protection Op->>API: "GET /fleets/{fleet_id}" API-->>Op: 200 + ETag: "v1" Op->>API: "PATCH /fleets/{fleet_id} (If-Match: "v1", new SKILL.md)" alt ETag matches API-->>Op: 200 (edit accepted) API->>Fleet: Next wake uses new source else ETag stale (another op saved first) API-->>Op: 412 UZ-AGT-014 + current ETag Op->>Op: Editor reloads current source end Note over Op,API: Memory forget Op->>API: "DELETE /fleets/{fleet_id}/memories/{key}" alt Key exists API-->>Op: 204 else Key absent API-->>Op: UZ-MEM-004 end%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% sequenceDiagram participant Op as Operator (Dashboard) participant API as agentsfleet API participant Fleet as Fleet Note over Op,Fleet: Source edit with stale-write protection Op->>API: "GET /fleets/{fleet_id}" API-->>Op: 200 + ETag: "v1" Op->>API: "PATCH /fleets/{fleet_id} (If-Match: "v1", new SKILL.md)" alt ETag matches API-->>Op: 200 (edit accepted) API->>Fleet: Next wake uses new source else ETag stale (another op saved first) API-->>Op: 412 UZ-AGT-014 + current ETag Op->>Op: Editor reloads current source end Note over Op,API: Memory forget Op->>API: "DELETE /fleets/{fleet_id}/memories/{key}" alt Key exists API-->>Op: 204 else Key absent API-->>Op: UZ-MEM-004 endReviews (2): Last reviewed commit: "docs(m131): clarify fleet concurrency an..." | Re-trigger Greptile