✨ Retain which provider turn each workflow Prompt was

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",

packages/acp/deno.json

@@ -3,7 +3,8 @@
  "version": "0.9.0",
  "license": "MIT",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "imports": {
  "acpx": "npm:acpx@0.12.0",

packages/acp/embedded-adapters.ts

@@ -0,0 +1,26 @@
+/**
+ * @module
+ *
+ * The ACP adapters this build carries, and how a host puts one on disk.
+ *
+ * Its own entrypoint, and deliberately not part of `@executablemd/acp`. This is
+ * a temporary arrangement: no published Codex or Claude release names the turn
+ * a Prompt completed, so a workflow run executes the snapshots under
+ * `vendor/adapters` instead. Issue #636 removes them, one provider at a time,
+ * as qualifying releases appear.
+ *
+ * Anything on the package root is a stable contract somebody may build on, and
+ * withdrawing one is a compatibility break. A workaround should not be able to
+ * earn that, so it lives here and goes away with the thing it exists for.
+ *
+ * The workflow Agent profile is the only caller.
+ */
+
+export {
+ AdapterSnapshotError,
+ carriesEmbeddedAdapter,
+ createEmbeddedAdapters,
+ embeddedAdapterIdentities,
+ overlaidAdapterRegistry,
+} from "./src/adapter-snapshots.ts";
+export type { EmbeddedAdapters, EmbeddedAdapterSnapshot } from "./src/adapter-snapshots.ts";

packages/acp/mod.ts

@@ -15,6 +15,11 @@
  */
 
 export { createAcpxProvider } from "./src/provider.ts";
+// The embedded ACP adapters are deliberately absent from this entrypoint. They
+// are a temporary arrangement with an exit gate (#636), and anything exported
+// here is a stable contract somebody may depend on — removing it later would be
+// a compatibility break earned by a workaround. A host reaches them through
+// `@executablemd/acp/embedded-adapters`, which goes away with them.
 export type {
  AcpMcpServer,
  AcpxProviderDependencies,

packages/acp/package.json

@@ -4,7 +4,8 @@
  "description": "ACPX agent provider for executable.md documents: drives coding agents over the Agent Client Protocol.",
  "type": "module",
  "exports": {
- ".": "./mod.ts"
+ ".": "./mod.ts",
+ "./embedded-adapters": "./embedded-adapters.ts"
  },
  "dependencies": {
  "@agentclientprotocol/sdk": "1.3.0",