[dgesteves-release]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

signoff-ui@0.10.1

Patch Changes

• #173 e264d59 - ai is an optional peer dependency, so npm and pnpm no longer install the AI SDK, its provider packages and zod in an app that doesn't use them: an AG-UI or ACP app now installs 11 fewer packages, about 25 MB. signoff-ui/ag-ui and signoff-ui/acp declare the AI SDK types they return (UIMessage, ChatStatus and token usage) themselves, so they type-check without ai, and their messages still go to AgentMessage and useChat as they are, on AI SDK 6 and 7. The components' props keep the AI SDK's own types: without ai, TypeScript reads them as any, so install it, as a dev dependency if nothing else needs it, to have them checked. The shadcn ag-ui item no longer lists ai either.

• #172 b458d6f - riskFromMcpAnnotations(annotations), in signoff-ui/core and the main entry, gives an approval card a risk level from what an MCP server says about its tool: high for destructiveHint: true, low for readOnlyHint: true, and medium for readOnlyHint: false or openWorldHint: true. Only hints the server set count, so a tool with no annotations still shows no risk, rather than the high the MCP spec's defaults would give it. With AI SDK 7's MCP client, read them from a call's part as part.toolMetadata?.annotations. It is a hint, not a guarantee: a server you don't trust can mark any tool read-only. RiskLevel is now exported from signoff-ui/core too. The useApprovalPolicy docs add a recipe for an organization's @ai-sdk/policy-opa policy first, with a person's rules deciding the calls it has no rule for.

• #204 e35edea - safeUrl, and so links and images in Markdown, Sources and file attachments in AgentMessage, no longer slow down on a URL from the agent that starts with a long run of spaces or control characters and has no colon: 100,000 of them took about 30 seconds and blocked the page, and now take under a millisecond. The scheme is still read past them, so javascript:alert(1) still renders as text. fromAcpDiffs and toAcpDiffs no longer slow down on a root with a long run of slashes that are not at its end either.