@pouchy_ai/companion-sdk 0.41.0 → 0.43.0

package/src/index.ts

@@ -91,6 +91,21 @@ export {
 } from './protocol';
 export type { CompanionErrorCode, ControlErrorCode } from './protocol';
 
+// Instant UI ⇄ Google A2UI v0.9 projection (0.42.0) — put `toA2UI` in front of
+// any renderer built against the A2UI catalog and it draws Pouchy panels;
+// `fromA2UI` ingests an A2UI surface back into the Instant UI panel shape.
+// The node-type catalog rides along as data for renderer capability checks.
+export { toA2UI, fromA2UI, INSTANT_UI_NODE_TYPES } from './a2ui';
+export type {
+	A2UISurface,
+	A2UIComponent,
+	A2UIValue,
+	InstantUIInput,
+	DynamicInterface,
+	GenuiNode,
+	EmbeddedAction
+} from './a2ui';
+
 // The framework-agnostic view controller behind the /svelte and /vue subpath
 // adapters (and the separate `@pouchy_ai/react` package) — exported from the
 // root too, so a host on any OTHER framework (or none) can reuse the same

package/src/protocol.ts

@@ -131,6 +131,15 @@ export interface ConfirmRequestPayload {
 	scope: string;
 	/** A human, user-facing summary of what approving will do. */
 	summary: string;
+	/** The same sentence as DATA — an i18n key (`confirmSummary.*`) plus its
+	 *  placeholder values — so a host that knows the user's language can render
+	 *  the approval in it. `summary` stays the English fallback and is always
+	 *  present; these two are absent for a tool that ships no keyed summary and
+	 *  on confirmations recorded before this field existed, so render
+	 *  `summaryKey ? localize(summaryKey, summaryVars) : summary`. The server
+	 *  cannot do this for you: the turn endpoint carries no locale. */
+	summaryKey?: string;
+	summaryVars?: Record<string, string | number>;
 	/** Advisory: when true, the first-party approval surface should require a
 	 *  stronger user gesture — a biometric / passkey (Face ID, Touch ID) — before
 	 *  approving, not just a tap. Set for irreversible money ops (wallet.spend).
@@ -146,6 +155,15 @@ export interface PendingConfirm {
 	scope: string;
 	/** A human, user-facing summary of what approving will do. */
 	summary: string;
+	/** The same sentence as DATA — an i18n key (`confirmSummary.*`) plus its
+	 *  placeholder values — so a host that knows the user's language can render
+	 *  the approval in it. `summary` stays the English fallback and is always
+	 *  present; these two are absent for a tool that ships no keyed summary and
+	 *  on confirmations recorded before this field existed, so render
+	 *  `summaryKey ? localize(summaryKey, summaryVars) : summary`. The server
+	 *  cannot do this for you: the turn endpoint carries no locale. */
+	summaryKey?: string;
+	summaryVars?: Record<string, string | number>;
 	/** Epoch ms when the companion asked. */
 	createdAt: number;
 }