Record the six shipped changes the changelog was missing - #368
Merged
Conversation
Twelve commits have landed since v0.0.6 and six of them had no entry, so the release notes would have described half of what is in the release. Reconciled against the commits rather than against the pull request bodies: every claim below was checked in the tree. Three are things a person will see. Writing a skill in the conversation (`skill-creator` in the example package, `examples/fintech/skills.yaml:89`), making a coworker in the conversation and having it start able to reach nothing (`bot-creator`, `:187`, both granted to `general-assistant`), and a conversation having a name of its own, which also changes what the roster's second line says and sends the opening exchange to the model the Bots already use as housekeeping (`MAX_EXCERPT_CODE_POINTS = 600` in `server/src/channels/summary.ts`). Three are fixes. A blank `agentId` on a channel activity answered `404 Agent not found` where the field was the problem, and now names the field with a 400. Audit payload redaction ran only in the wrapper, so the exported store's `insert` would have written secrets in cleartext for any future direct caller, and now redacts too. And a `null` part in an MCP tool result threw and failed the turn that had just called the tool, where it is now named `[unknown]` like every other unrecognised part.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso and
tylerslaton
as code owners
September 4, 2026 18:01
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.
Twelve commits have landed since v0.0.6 and six had no changelog entry, so a release cut now would describe half of what is in it.
Reconciled against the commits and the tree, not against the pull request bodies. Every claim below was checked in code.
Did not happenfor a failed callagentIdnames the fieldNODE_ENVnullMCP result part no longer throwsWhat the six say
Three a person will see.
skill-creatorandbot-creatorship in the example package (examples/fintech/skills.yaml:89and:187), both granted togeneral-assistant, and the grant is the whole gate: the app offers the four authoring tools only to a Bot holding the slug. Conversation naming changes what the roster's second line says, and sends the opening exchange,MAX_EXCERPT_CODE_POINTS = 600inserver/src/channels/summary.ts, to the model the Bots already use. That is not new egress but it is sent as housekeeping rather than because somebody asked, so the entry says so.Three fixes. A blank
agentIdanswered404 Agent not foundwhen the field was the problem, and now names the field with a 400 (server/src/channels/routes.ts:932). Audit redaction ran only inrecordAuditEvent, so the exported store'sinsertwould have written secrets in cleartext for any future direct caller;redactAuditPayloadnow runs there too, idempotently, so the existing path is unchanged (server/src/audit.ts:490). And anullpart in an MCP tool result threw, failing the turn that had just called the tool, where it is now[unknown]like every other unrecognised part (server/src/plugins/mcp.ts:52).The audit one changes no current behaviour, since every caller goes through the wrapper. It is in the notes because somebody deciding whether to upgrade cares about where the floor is, and the entry says plainly that it is a floor rather than a fix.
Next
This is the gate on cutting v0.0.7. Merge this, then the release PR.