@intentic/extension-api 1.337.0 → 1.338.0

package/src/testing.ts

@@ -6,6 +6,8 @@ import { type ExtensionEvent, extensionEventsUrl, extensionSettingsUrl } from "@
 import { EXTENSION_TOKEN_HEADER } from "@intentic/sandbox-contract/headers";
 import { activateServerModule, createServerApi, deactivateWithin, healthWithin } from "./runtime.js";
 import type {
+    ApprovedAction,
+    ApprovedActionOutcome,
     ExtensionHealth,
     ExtensionServerApi,
     ExtensionServerModule,
@@ -69,6 +71,8 @@ export interface FakeExtension {
     // Answers whatever the tool's own `call` answers, as ToolDefinition declares it; the host turns that into what the
     // model reads.
     callTool(name: string, args?: ToolArguments, card?: ToolCard, context?: Partial<ToolCallContext>): ReturnType<ToolDefinition["call"]>;
+    // An approved action handed over as the daemon's approvals executor hands it, through the host's door.
+    perform(action: ApprovedAction, signal?: AbortSignal): Promise<ApprovedActionOutcome>;
     // The owner changing its settings: stored, and told to the extension over its event stream as the daemon would.
     setSettings(values: ExtensionSettingValues): void;
     // A frame on its event stream, as the daemon sends it (`files`, `refs`, `repos`, `settings`).
@@ -211,6 +215,13 @@ export const fakeExtensionApi = async (options: FakeExtensionOptions): Promise<F
             }
             return tool.call(args, { signal: context.signal ?? new AbortController().signal, conversationId: context.conversationId });
         },
+        perform: async (action, signal = new AbortController().signal) => {
+            const performer = slots.performer();
+            if (performer === undefined) {
+                throw new Error(`"${id}" carries out no approved actions`);
+            }
+            return performer(action, { signal });
+        },
         setSettings: (values) => {
             const keys = changedKeys(settings, values);
             settings = { ...values };

package/src/version.ts

@@ -187,4 +187,23 @@
 // bot (a mention, a reply, a direct message), as the Discord team assistant does. An older host's parse drops the key,
 // so there the template answers every message on that event. No member or top-level key was added, so the manifest
 // digest is the only grain that records it.
-export const extensionApiVersion = "2.29.0";
+// 2.30.0 lets a cli capability card carry a delegated OAuth sign-in: `refreshToken` names the secret field the refresh
+// token lives in and the fields it is bound to, so the extension's own CLI or process stores a new or rotated token
+// through the daemon's oauth-token route instead of printing it for someone to paste, and `probe.oauth` trades that
+// token for an access token before the card's connection test. An older host's parse drops both keys, so there the
+// token is pasted by hand and the test runs without the trade. No member or top-level key was added, so the manifest
+// digest is the only grain that records it.
+// 2.31.0 versions the UI kit. `@intentic/extension-ui`'s exports are names a bundle links against as it links this
+// package's, and nothing recorded them: `RepoRail` left the kit on 2026-10-12 with no version moving, and every
+// installed extension still importing it failed to load with the browser's link error. The recorded surface grows a
+// `uiKitExports` grain (the kit's names.mjs), and those names, with this package's `moduleExports`, are held to semver
+// by the surface guard: a name joining is a minor, and a name leaving is a major, allowed only once names.mjs declares
+// it deprecated and only at or past the floor it gives. Recorded here: `RepoPicker`, added on 2026-10-12 without a
+// version, and `RepoRail`, back and deprecated until 3.0.0. Additive.
+// 2.32.0 lets a backend carry out an approved action itself: `api.approvals.perform(handler)`. An approvals-queue action
+// whose `performer` names the extension is handed to it by the daemon's approvals executor, through a backend-host door
+// no /x route reaches, only after the daemon matched a person's recorded yes against the item and spent it. Until now an
+// approved action ran as an agent turn following the item's instructions, and a connection's own command could only
+// read the workspace file to decide whether it was approved, which any turn writes. Additive: a backend that never calls
+// it is unchanged, and an action naming no performer still runs as a turn. The recorded surface grows the member.
+export const extensionApiVersion = "2.32.0";