Conversation
…ons date-stamp
Two small, independent fixes from the public-docs audit (2026-05-08):
- protocol/error-codes-and-error-handling-in-cycles.md: the page said
"Cycles defines 16 error codes" — but the runtime OpenAPI spec
(cycles-protocol-v0.yaml) defines 15 ErrorCode values; the 16th is the
admin-plane TENANT_CLOSED lifecycle error covered on the same page.
Clarify scope: 15 runtime + 1 admin-plane covered here, with a pointer
to the admin spec for the full admin-plane enum and to the
tenant-close-cascade semantics page for TENANT_CLOSED context.
- blog/26-integrations-every-ai-framework-one-budget-protocol.md: the
post is a dated announcement (2026-04-02) but read as if the count
were current. The integrations overview now lists 27. Date-stamp the
count inline ("As of this post (2026-04-02)…") and point readers to
the integrations overview for the live list. No other body changes —
the section counts in the post are internally consistent under the
language-variant counting convention used throughout the site.
Verified: vitest 83/83 pass; vitepress build completes.
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.
Summary
Third patch from the public-docs audit (2026-05-08). Two trivial, independent P1s in one PR.
Error-code scope clarification
protocol/error-codes-and-error-handling-in-cycles.mdsaid "Cycles defines 16 error codes." Per the runtime YAML (authoritative —cycles-protocol-v0.yaml'sErrorCodeenum has exactly 15 values), the 16th is the admin-planeTENANT_CLOSEDlifecycle error which is covered on this page but not part of the runtime wire contract. The admin-plane error enum has additional codes that aren't documented here.Replaced the bare "16" line with a scope-clarifying sentence: 15 runtime wire codes + 1 admin-plane lifecycle error covered here, with a pointer to the admin spec for the full admin-plane enum and to the
tenant-close-cascade-semanticspage for TENANT_CLOSED context."26 integrations" post date-stamp
blog/26-integrations-every-ai-framework-one-budget-protocol.mdis a dated announcement (2026-04-02) but the body read like a current claim. The integrations overview now lists 27 (Rust SDK was added after this post shipped).Added an inline date-stamp in the lede sentence ("As of this post (2026-04-02), Cycles ships 26 integrations…") and a pointer to the live integrations overview for the current list. No other body changes — the section counts inside the post are internally consistent under the language-variant counting convention used across the site.
Test plan
vitest run— 5 files, 83/83 tests passvitepress build— completes cleanlyOut of scope
Remaining audit queue: Windows build wrapper (P1, separate PR), SEO title-length sweep (P2), missing
<!-- more -->markers (P2), blog-to-how-to internal links (P2), Shiki promql/conf warnings (P3).