docs(m130): catalog identity editing, honest status, clipboard + dashboard truth#140
Open
indykish wants to merge 2 commits into
Open
docs(m130): catalog identity editing, honest status, clipboard + dashboard truth#140indykish wants to merge 2 commits into
indykish wants to merge 2 commits into
Conversation
…truth The fleet-library page now documents that an onboarded entry lands as a draft (the page previously claimed it appeared in every workspace's library immediately — untrue since publishing became the only door), and gains an 'Edit a platform entry' section: name/repository/ref editing, source-repoint bundle invalidation, rename durability, credential-copy pruning, and the Broken state. Changelog: Jul 14 entry covering the identity edit, the honest status column, the Create-fleet-library verb, clipboard failure reporting, dashboard tile totality, and tool calls + cost in the live thread.
The Fetch update path now fetches at the ref the entry names instead of resetting it to the repository's default branch, so the ref belongs on the same line as the rename in both the library page and the changelog. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| Platform entries are added from the dashboard at **Fleet library**, under Configuration, with **Create fleet library**. The page is visible only to an operator whose session carries the `platform-library:write` scope. Everyone else is redirected, and the API refuses the request independently. | ||
|
|
||
| Enter the repository as `owner/repo`. `agentsfleet` fetches the repository, validates the bundle, stores it, and adds the catalog row. The entry then appears in every workspace's library, and any workspace can install it. | ||
| Enter the repository as `owner/repo`. `agentsfleet` fetches the repository, validates the bundle, stores it, and adds the catalog row **as a draft**. No workspace can see or install a draft; publishing is the only door to a workspace's library. |
Contributor
There was a problem hiding this comment.
This correctly says a platform entry starts as a draft, but the Jul 12 changelog still tells operators that onboarding adds it where every workspace can install it. An operator following that release note will expect immediate visibility and may treat the required publish step as a failed onboarding.
Prompt To Fix With AI
This is a comment left during a code review.
Path: fleets/library.mdx
Line: 45
Comment:
**Onboarding Guidance Still Conflicts**
This correctly says a platform entry starts as a draft, but the Jul 12 changelog still tells operators that onboarding adds it where every workspace can install it. An operator following that release note will expect immediate visibility and may treat the required publish step as a failed onboarding.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
|
|
||
| ## API reference | ||
|
|
||
| `PATCH /v1/admin/fleet-libraries/{id}` additionally accepts `name`, `source_repo`, and `source_ref`. A request whose `source_repo` or `source_ref` differs from the stored value sets `content_hash` to null and `visibility` to `draft` atomically; re-sending the stored value is a no-op. A request that changes the source and sets `published: true` in the same call is refused with `UZ-CATALOG-002` (there is no bundle to publish by the time the publish would apply). Malformed sources are refused with `UZ-BUNDLE-001` using the same validation as onboarding. The entry identifier is never patchable. |
Contributor
There was a problem hiding this comment.
This introduces PATCH /v1/admin/fleet-libraries/{id}, but the Fleet library API navigation does not include that operation. Operators browsing the API reference cannot discover the documented edit path and are left with only the collection GET and POST operations.
Prompt To Fix With AI
This is a comment left during a code review.
Path: changelog.mdx
Line: 41
Comment:
**PATCH Operation Is Not Discoverable**
This introduces `PATCH /v1/admin/fleet-libraries/{id}`, but the Fleet library API navigation does not include that operation. Operators browsing the API reference cannot discover the documented edit path and are left with only the collection GET and POST operations.
How can I resolve this? If you propose a fix, please make it concise.|
|
||
| ## API reference | ||
|
|
||
| `PATCH /v1/admin/fleet-libraries/{id}` additionally accepts `name`, `source_repo`, and `source_ref`. A request whose `source_repo` or `source_ref` differs from the stored value sets `content_hash` to null and `visibility` to `draft` atomically; re-sending the stored value is a no-op. A request that changes the source and sets `published: true` in the same call is refused with `UZ-CATALOG-002` (there is no bundle to publish by the time the publish would apply). Malformed sources are refused with `UZ-BUNDLE-001` using the same validation as onboarding. The entry identifier is never patchable. |
Contributor
There was a problem hiding this comment.
The new combined source-and-publish failure returns UZ-CATALOG-002, but that code is absent from the error-code reference. Clients following the reference cannot map this reachable PATCH failure to its documented cause or present the intended recovery guidance.
Prompt To Fix With AI
This is a comment left during a code review.
Path: changelog.mdx
Line: 41
Comment:
**New Error Code Lacks Reference**
The new combined source-and-publish failure returns `UZ-CATALOG-002`, but that code is absent from the error-code reference. Clients following the reference cannot map this reachable PATCH failure to its documented cause or present the intended recovery guidance.
How can I resolve this? If you propose a fix, please make it concise.
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
1 participant
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.
Documentation for agentsfleet#519 (M130).
Pages
fleets/library.mdx— corrects a falsehood: an onboarded entry lands as a draft, not immediately visible in every workspace gallery. Adds an "Edit a platform entry" section: name, repository, and ref are editable in place; changing the source discards the stored bundle and returns the entry to draft; installed workspaces keep the exact bundle they installed; a rename and a pinned ref both survive the next fetch; an entry published with no bundle shows as Broken.changelog.mdx— a Jul 14, 2026<Update>covering the honest status column, in-place identity editing, the clipboard surfaces that now report a failed write, the dashboard counting every fleet state, and the live thread showing tool calls and per-event cost. Includes thePATCH /v1/admin/fleet-libraries/{id}reference change.make check-documentation-rulespasses.🤖 Generated with Claude Code
Greptile Summary
This PR documents the M130 Fleet library behavior and dashboard updates. The main changes are:
Confidence Score: 5/5
The documentation is mergeable after its API references and conflicting onboarding guidance are aligned.
changelog.mdx and fleets/library.mdx
Important Files Changed
Prompt To Fix All With AI
Reviews (1): Last reviewed commit: "docs: a pinned ref survives the next bun..." | Re-trigger Greptile