patches

scripts/apply-dependency-patches.mjs applies these during the root postinstall with --error-on-fail, so a patch that stops applying blocks the install instead of vanishing. It skips when patch-package is unresolvable (npm ci --workspace <name>, npm ci --omit=dev); those trees are not what ships, and each section's guard test is what catches an unpatched one.

After bumping a patched dependency, re-run npx patch-package <name> so the filename tracks the installed version.

Every patch needs a reason and a deletion condition, and that is all this file carries — the derivation belongs in the guard test, and the measurements in the upstream issue.

Only dist/ is ever patched: package.json exports resolves there and Maka compiles no vendored src/. The .map files are left stale, so a debugger inside patched code points at upstream src/ lines that no longer describe what runs.

@ai-sdk/provider-utils: a tool-call delta must agree with the call it continues

Fixes #1967 and #1976. StreamingToolCallTracker used tool_calls[].index — an association label a gateway may omit, repeat, or number freely — as storage slot, identity and ordering at once. 5.0.21 (vercel/ai#18382) fixed the crash and promoted id to sole authority, which reproduces the defect with the fields swapped: gateways repeat id too, and function.name is still never consulted, so the Ollama shape — three calls at index: 0, no id, one repeating name — cannot be separated.

The patched tracker keys on nothing. Records live in creation order, each learning the aliases the wire uses for it; a delta resolves to the newest call one of its aliases claims and none contradicts; the emitted id is minted separately, because the wire's id space is not injective and three layers downstream assume ours is. The remaining behaviour and the shapes it cannot decide are stated as measured output in vercel/ai#18440 and pinned case by case in the guard — read those rather than re-deriving either here.

Delete it when the guard holds without it. Remove the patch, reinstall, run packages/runtime/src/__tests__/model-factory-tool-call-index.test.ts, and read the result by property rather than by count: assertInputsSelfContained, assertToolCallIdsUsable, assertEventLifecycle. Cases marked Known boundary, deliberately locked in assert that an undecidable shape fails loudly; an upstream that genuinely fixed the layers below would turn those red for a better implementation, so treat a red run there as a signal to re-read, not a verdict.

@astryxdesign/core: “New messages” must clear at the bottom and on a fresh transcript

Fixes #2205. ChatLayout never resets two pieces of per-conversation state: hasNewMessages clears only through the button‘s dismiss(), so scrolling back down leaves the label up; and a conversation switch reuses the transcript container, so the previous conversation’s last message stays the baseline and the new one's first message reads as unread.

The patch clears the flag whenever the scroll lock re-engages, so “at bottom” owns the badge; adds a conversationKey prop that re-locks and resets the baseline when it changes; and exposes reset() on useChatNewMessages. A prop rather than a remount — remounting drops an in-progress composer draft, since Astryx's composer holds its content in internal state.

Delete it when Astryx clears the badge at the bottom and offers a baseline reset on a conversation switch without a remount. Repro: scroll up, receive a message, scroll back down; then switch conversations with the badge active — the new conversation must start clean and the composer draft must survive.

@astryxdesign/core: List must render the accessible name its interface accepts

Fixes #2189. ListProps extends BaseProps, which includes aria-label, but List destructures a fixed prop set and drops it, so six Maka lists pass localized names that disappear at runtime. The patch forwards aria-label to the root list — narrower than spreading the rest of BaseProps through a vendored component, and it leaves the header / aria-labelledby path alone.

Delete it when packages/ui/src/__tests__/astryx-list-accessible-name.test.tsx passes without the patch.

@astryxdesign/core: a collapsed tool group must still say what it changed

A contiguous run of tool calls is one group, and a group collapses by default. The collapsed header projects the latest call's status icon, name and target alone — additions, deletions, duration and stats are all dropped — so the commonest shape, several edits in one turn, is the one that shows no counts. Nothing reaches that header from the product side; the label prop it accepts is destructured and never used.

The patch adds group-level additions / deletions and renders them beside the wrench count on the collapsed header. ToolTrow passes the run's total; the per-call counts stay on the rows inside.

Delete it when packages/ui/src/__tests__/tool-trow-stability.test.tsx passes without the patch — its grouped-diff case asserts the summed +N / -N on a collapsed run.