@absolutejs/mcp 0.19.0 → 0.20.1

package/dist/src/actionWorkflow.d.ts

@@ -0,0 +1,35 @@
+import type { McpToolRegistry } from "./types";
+export type ActionReview = {
+    /** Set by the tool factory from the available confirmation capability. */
+    canConfirm?: boolean;
+    actionId: string;
+    revision: string;
+    title: string;
+    expiresAt: string;
+    recipients: string[];
+    subject: string;
+    body: string;
+    consequence: string;
+};
+export type ActionConfirmation = {
+    actionId: string;
+    expectedRevision: string;
+};
+export type ActionJob = {
+    actionId: string;
+    status: "awaiting_approval" | "queued" | "running" | "succeeded" | "failed" | "unknown" | "denied" | "expired";
+    title: string;
+    summary: string;
+};
+export declare const projectActionReview: (value: unknown) => ActionReview;
+export declare const projectActionJob: (value: unknown) => ActionJob;
+/** Bind readers and confirmation to the authenticated owner. confirm must compare
+ * the exact reviewed revision and expiry under a database lock, authorize the
+ * immutable payload, and commit its decision plus durable outbox atomically.
+ * Every draft writer must refuse edits after that claim. Never send inline.
+ * Job reads/resume only reattach to saved work, including ambiguous outcomes. */
+export declare const createActionWorkflowTools: (adapter: {
+    review: (actionId: string) => Promise<ActionReview>;
+    job: (actionId: string) => Promise<ActionJob>;
+    confirm?: (request: ActionConfirmation) => Promise<ActionJob>;
+}) => McpToolRegistry;

package/dist/src/actionWorkflow.generated.d.ts

@@ -0,0 +1 @@
+export declare const actionWorkflowScript: string;

package/dist/src/apps.d.ts

@@ -36,3 +36,4 @@ export { createBillingApps } from "./billingApps";
 export { createWorkflowApps } from "./workflowApps";
 export { createWorkflowTools, projectSetupStatus, projectWorkPreview, type McpSetupStatus, type McpWorkPreview, type McpWorkPreviewRequest, } from "./workflowTools";
 export { createSetupSelectionTools, projectSetupSelection, type SetupSelection, type SetupConfirmation, type SetupOption, } from "./setupSelection";
+export { createActionWorkflowTools, projectActionReview, projectActionJob, type ActionReview, type ActionConfirmation, type ActionJob } from "./actionWorkflow";

package/dist/src/index.d.ts

@@ -52,3 +52,4 @@ export { createBillingApps } from "./billingApps";
 export { createWorkflowApps } from "./workflowApps";
 export { createWorkflowTools, projectSetupStatus, projectWorkPreview, type McpSetupStatus, type McpWorkPreview, type McpWorkPreviewRequest, } from "./workflowTools";
 export { createSetupSelectionTools, projectSetupSelection, type SetupSelection, type SetupConfirmation, type SetupOption, } from "./setupSelection";
+export { createActionWorkflowTools, projectActionReview, projectActionJob, type ActionReview, type ActionConfirmation, type ActionJob } from "./actionWorkflow";

package/docs/host-canaries.md

@@ -172,3 +172,28 @@ aggregate evidence. The separate rich-view startup issue is unchanged.
 The [individual Copilot external-checkout review](reviews/vscode-individual-external-checkout.md)
 records the exact eligible deployment scope and activation conditions; the
 synthetic fixture is not a real merchant/OAuth acceptance test.
+
+### September 12 Claude workflow and selection observation
+
+Native Windows Chrome/Claude rendered MCP 0.18.0 setup and preview views from a
+verified onSpark staging connector. One explicit refresh per view produced one
+additional read each; conversation reload remounted both without extra calls.
+MCP 0.19.0's business selector subsequently rendered after one successful
+`get_setup_options` call. Reload left its audit at one read and no mutations.
+These were desktop/light-theme checks on an existing account. Local visible
+bridge fixtures separately covered 390px/light/dark layout and synthetic
+Review/Cancel (zero calls), Confirm (one call/one fixture write), and no replay.
+Native confirmation against a real business was not tested.
+
+After a server release, Claude retained its previous tool list. The connector's
+**More options → Refresh tools list** exposed the new tools without reconnecting.
+Chat discovery still chose the separate production connector until production
+was temporarily disabled in that test chat's **Connectors** submenu. Then the
+explicit staging-only read resolved and rendered. Restore prior toggles after a
+test. The stopped discovery attempts made no server calls. This is qualified
+operational evidence, not a proven general indexing defect: verify the native
+tool list and enabled connector scope before concluding that a deployed tool is
+missing, and do not stack authorization requests to troubleshoot discovery.
+
+Rendering evidence does not expand host commerce eligibility or authorize paid
+work, checkout, outbound actions, or real account mutations.

package/docs/mcp-apps.md

@@ -101,3 +101,29 @@ obtain explicit approval before invoking the write tool. This is a reversible
 setup action with no billing or outbound effects; it does not authorize paid
 work. At most 200 options are supported; IDs/revisions are bounded at 128
 characters and labels at 512. No account selector or credentials enter the view.
+
+### Durable action status and reviewed outbound approval
+
+`createActionWorkflowTools({ review, job, confirm? })` provides
+`get_action_review`, `get_action_job`, `resume_action_job`, and (only with a
+confirmation adapter) `confirm_action_review`. `createWorkflowApps()` supplies
+the shared action view. The review contains the full recipients, subject, body,
+consequences, exact revision, and expiry. The view separates local review/cancel
+from explicit **Approve and queue**, marks that tool as an external destructive
+write, and never calls tools on mount. Host theme changes are applied explicitly.
+
+Bind identity in the adapter. Under a database lock, compare the reviewed
+revision and expiry, authorize the immutable payload, and commit the decision
+and durable outbox together. All draft writers must refuse edits after claim.
+Use a stable effect identity and retain ambiguous outcomes for reconciliation;
+never make provider calls inside this confirmation tool. Returned job identity
+must match the requested action. Error responses require a saved-status read,
+not an automatic approval retry or a newly invented action ID.
+
+`resume_action_job` resumes **tracking**, by reading the existing durable job.
+It does not restart work, grant a new lease, retry, resend, or reconcile an
+unknown outcome. The worker owns safe retries. Project only user-facing status
+and summaries; do not expose raw provider errors, credentials or queue internals.
+The text-only path carries the same review and status; host support does not
+expand authorization or commerce eligibility. Review bodies are bounded at
+100,000 characters, subjects at 2,000, and recipient lists at 100.

package/package.json

@@ -90,5 +90,5 @@
     "canary:checkout": "bun canary/checkout.ts"
   },
   "types": "./dist/src/index.d.ts",
-  "version": "0.19.0"
+  "version": "0.20.1"
 }