1.0.0-rc.6
The sixth release candidate for 1.0.0. All six packages move to 1.0.0-rc.6 together. Only @silverprotocol/richtext changes; the other five change only their version. The spec revision stays 1.0.0-rc.3 (AGJSON_VERSION), and its text gains one erratum.
Installing the release candidate
The release candidate is published under the rc tag. latest is on 0.12.10:
npm i @silverprotocol/core@rc
Install each framework package you use the same way, so every @silverprotocol/* package in your lockfile is on 1.0.0-rc.6. While a release candidate is the most recent publish, a package’s page on npmjs.com shows no README; each package still carries its README.
0.12.10 ships the same rich text fix on the 0.12 line, and 1.0.0-rc.6 carries everything 0.12.10 changes.
Who should upgrade
- You render chat text with
parseRichTextfrom@silverprotocol/richtext. Nested emphasis and indented continuation lines under a list item now parse as written. Read “Upgrading from rc.5” below first. - Anyone else gets the same events and fold results as from rc.5:
@silverprotocol/coreand the four framework packages change only their version.
Upgrading from rc.5
- A table or heading line indented under a list item is now item text. rc.5 ended the list there: an indented pipe table became a top-level table, and an indented
# headingline a paragraph. The line now joins the item’s text, as the README’s subset already states for block content inside a list item. The AST types don’t change: aRichTextListItemstill holds inline content only.
@silverprotocol/richtext
- An emphasis run closes the innermost open emphasis whose marker it matches exactly.
*a **b** c*now parses as an em holding a strong; rc.5 closed the em at the strong’s**and left* c*as literal text.*a *b* c*and_a __b__ c_parse the same way.**a *b** cand***runs parse as before, and emphasis still never closes across a[. - An indented line directly under a list item continues that item. A line indented by spaces or a tab joins the item’s inline content after a
break, and the item’s lines parse as one inline run, so emphasis can span them.- item one,continued line,- item twois now one list of two items, where rc.5 gave a list, a paragraph and a second list. An unindented line or a blank line still ends the list.
Spec
The revision stays 1.0.0-rc.3, so no closed set, schema or fold rule changes. Its text carries the spec’s first erratum, in §15:
Erratum (2026-10-27) — the host-reading gloss in §4. It corrects rc.3; the sentence entered at rc.1. §4’s second informative parenthetical of the
costUsdnote, which read “— aturn.abort, or aturn.errororturn.donewhoseusageis absent or carries no token counter —”, now reads “— aturn.abort, or aturn.errororturn.donewhoseusageis absent or carries no top-level token counter —”. The token counters that parenthetical and §10 item 67 name are the seven top-level members ofAgUsage(inputTokens,outputTokens,cacheReadTokens,cacheWriteTokens,reasoningTokens,toolUseInputTokensandtotalTokens), and a nestedbyModelentry carries its owncumulativeflag; the word pair states the reading the enumeration already gives and changes no meaning. The sentence is informative; no field, event, fold or requirement moves, and no version moves.
Verified versions
Unchanged from rc.5. Each framework package is verified end to end, tool calls included, against a live run at:
@anthropic-ai/claude-agent-sdk0.3.310;@openai/agents0.21.0;@google/adk2.3.0, with@google/genai2.31.0;ai7.0.153, with@ai-sdk/openai4.0.102.
Wire version
1.0.0-rc.3, unchanged.
The 1.0.0-rc.6 packages are built from typescript-sdk commit 2b49c89c, the commit npm’s provenance for all six 1.0.0-rc.6 packages attests.