@introspection-ai/recipes 0.20.0 → 0.22.0

package/docs/channels.md

@@ -0,0 +1,166 @@
+# Channel tools
+
+A Recipe that answers a chat message declares a **channel connector**. The host
+then registers a fixed set of `channel_*` tools, named and shaped identically
+for every provider, and bound to the one conversation the task came from.
+
+Two properties follow from that, and both are structural rather than
+conventional:
+
+- **The agent cannot address anything else.** No `channel_*` tool takes a
+  channel, thread, workspace, or user argument. The conversation is closed over
+  by the host from the task origin, so a compromised prompt has no vocabulary
+  for "post this somewhere else". The invariant is asserted by a test that
+  walks every registered tool's input schema.
+- **A tool that the provider cannot support is absent, not failing.** Each
+  adapter declares a capability descriptor, and registration filters on it.
+  For example, an adapter with no history API has no `channel_read` tool.
+
+Before the first model call, the channel extension adds origin metadata to the
+system prompt. The metadata contains the provider, the conversation name and
+permalink when the adapter can resolve them, whether the origin is a thread,
+and the available channel tools. It contains no provider conversation IDs and
+no messages.
+`channel_read` remains the only way to fetch earlier messages when the
+provider supports it.
+
+## The tools
+
+| Tool | Model arguments | Requires |
+| --- | --- | --- |
+| `channel_reply` | `text` (Markdown) | always |
+| `channel_read` | `limit?`, `cursor?` | `read` |
+| `channel_react` | `message`, `emoji`, `action?` (`add` or `remove`) | `react` |
+| `channel_edit` | `message`, `text` | `edit` |
+| `channel_retract` | `message` | `retract` |
+| `channel_attach` | `path`, `title?`, `comment?` | `attach` |
+| `channel_fetch_file` | `file` (a `file_…` handle), `variant?` | `fetch_file` |
+| `channel_post_document` | `title`, `markdown` | `documents` |
+
+`channel_reply`, `channel_read`, and `channel_react` are active by default when
+the provider supports them. The other selected tools start inactive, and the
+model can find them through `tool_search`.
+
+Reply content is **Markdown**. Each adapter renders it in the provider's own
+format. There is no raw provider payload because the same tool contract must
+work with every adapter.
+
+### Message and file references
+
+`channel_react`, `channel_edit`, and `channel_retract` take a `message`, which is
+an opaque handle minted by the host for the current session. It is not a Slack
+timestamp or another provider message ID. Handles come back from
+`channel_reply` and `channel_read`, so the model can only act on a message that
+a channel tool returned.
+
+`channel_react` adds a reaction when `action` is omitted. Set `action` to
+`remove` to remove the agent's reaction with the same emoji.
+
+Edit and retract have an extra check. They accept only a handle for a message
+that this agent posted. Reading the same message again keeps its original
+handle and authorship record.
+
+`channel_fetch_file` works the same way. Attachments returned by `channel_read`
+carry a `file_…` handle, and that is the only value the tool accepts. A bot can
+usually read files from every conversation it belongs to, so accepting a raw
+provider file ID would let the model reach files outside the bound conversation.
+
+### Enrichment, not lookup tools
+
+Author names and permalinks are resolved by the adapter in trusted code and
+attached to what the agent is already reading: `channel_read` rows carry
+`author.display_name`, and `channel_reply` returns a `permalink` where the
+provider has one. There is no `resolve_user` or `get_permalink` tool, because
+each would require another model turn. Each lookup would also take an
+addressing argument.
+
+### Unsupported operations
+
+Workspace search, channel listing and joining, directory lookup, and posting to
+another conversation are unsupported. The proposal does not choose an API or
+access model for those operations. A separate proposal can define them when a
+concrete use case requires them.
+
+Typing indicators and presence are runtime effects rather than model decisions.
+Streaming controls how a reply is delivered. The runtime derives idempotency
+keys, and the webhook already removes duplicate inbound events.
+
+## Declare a channel connector
+
+```json
+{
+  "dependencies": {
+    "@introspection-ai/recipe-channel-slack": "^0.1.0"
+  },
+  "pi": {
+    "connectors": [
+      {
+        "provider": "slack"
+      }
+    ]
+  }
+}
+```
+
+The connector declaration enables the provider package and its supported tool
+catalog. The agent YAML file is the only place that narrows the catalog:
+
+```yaml
+tools: [channel_reply, channel_read, channel_react, channel_edit, channel_retract, channel_fetch_file]
+```
+
+The host fails when an agent selects a tool that the provider does not support.
+
+Because the vocabulary is neutral, the same declaration and the same agent
+prompt work against another provider by changing the dependency and `provider`.
+Each provider package declares the capabilities that it can support.
+
+## Write an adapter
+
+An adapter supplies transport and a capability descriptor. It writes no tool
+schemas. The shared schema keeps providers from defining different forms of
+the same operation, and it prevents a provider from adding an addressing
+argument.
+
+```ts
+import {
+  createChannelConnectorModule,
+  type ChannelAdapter,
+} from "@introspection-ai/recipes/channels";
+
+const capabilities = {
+  react: false, edit: true, retract: true, read: false,
+  attach: false, fetchFile: false,
+  documents: false, resolveAuthors: true, permalinks: false,
+};
+
+class MyAdapter implements ChannelAdapter {
+  readonly provider = "my-channel";
+  readonly capabilities = capabilities;
+  async reply(ctx, { text }) { /* post into ctx.target */ }
+  async edit(ctx, { ref, text }) { /* edit an agent-authored message */ }
+  async retract(ctx, { ref }) { /* retract an agent-authored message */ }
+}
+
+export default createChannelConnectorModule({
+  provider: "my-channel",
+  capabilities,
+  createSession: ({ env }) => ({
+    adapter: new MyAdapter(/* client from env */),
+    // A function, so a task with no channel origin still starts: the tools
+    // fail when called, the session does not fail to open.
+    target: () => resolveTargetFrom(env),
+  }),
+});
+```
+
+Registration checks that the adapter implements every method its capabilities
+claim, so a descriptor cannot promise a tool the adapter does not have.
+
+The result is an ordinary `RecipeConnectorModule`. Manifest validation, agent
+tool selection, and `tool_search` work without provider-specific code in the
+Recipe.
+
+## Provider pages
+
+- [Slack](slack.md)

package/docs/index.md

@@ -17,6 +17,8 @@ task lifecycle, protocols, and deployment.
 | Compose agents and subagents | [Agent composition](agent-composition.md) |
 | Ask for user input across hosts | [Interactions](interactions.md) |
 | Declare capability policy and bindings | [MCP configuration](mcp-configuration.md) |
+| Answer a chat message from a Recipe | [Channel tools](channels.md) |
+| Add Slack tools to a Recipe | [Slack channel connector](slack.md) |
 | Define portable evaluation judges | [Recipe judges](recipe-judges.md) |
 
 ## Boundary

package/docs/mcp-configuration.md

@@ -91,10 +91,12 @@ to hide all authorized tools for a server, then optionally list exact tools in
 or a sole `"*"` selector. `eager` wins when a tool matches both fields, but
 neither field can authorize a tool excluded by `include`/`exclude`.
 
-Deferred tools remain authorized and discoverable. When at least one exists,
-Recipes registers `mcp_search`; calling it searches only the authorized
-deferred catalog and adds matches to Pi's current active tool set for the next
-model request. It never grants access beyond `servers`.
+Deferred tools remain authorized and discoverable. When at least one connector
+or MCP tool is deferred, Recipes registers `tool_search`. Calling it searches
+the inactive tools already allowed for the agent and adds the best matches to
+Pi's active tool set for the next model request. It never grants access beyond
+the Recipe manifest and agent policy. Recipes also registers `mcp_search` as a
+compatibility alias when MCP tools are deferred.
 
 `defer` and `eager` are invalid in CLI mode. An omitted agent `mcp` block
 inherits its base policy. Once a child declares `mcp`, the complete block

package/docs/pi-extension.md

@@ -53,9 +53,10 @@ For the selected agent, the extension:
 1. reads the root `package.json#pi` resource declarations;
 2. resolves the agent YAML, including `from:` inheritance;
 3. selects the model, thinking level, and tool allowlist;
-4. loads selected skills, package prompts, and the complete Recipe extension closure;
-5. materializes declared MCP bindings from host or local configuration;
-6. exposes only the declared subagents through the shared `agent` tool.
+4. loads providers from `pi.connectors` and registers the tools selected by the agent;
+5. loads selected skills, package prompts, and the complete Recipe extension closure;
+6. materializes declared MCP bindings from host or local configuration;
+7. exposes only the declared subagents through the shared `agent` tool.
 
 See [Recipe Format](recipe-format.md) for the authored contract and
 [Agent composition](agent-composition.md) for inheritance and selection.
@@ -115,9 +116,8 @@ skills, prompt templates, and context files by default.
 
 ## Validation
 
-Every `pi --recipe` launch automatically runs the shared Recipe Format
-validator. Invalid Recipes are rendered in Pi and stop the session before any
-model call.
+A `pi --recipe` launch does **not** validate the Recipe. Validation runs where
+it can be acted on: while authoring, and in whatever host starts the session.
 
 For an explicit manual or CI check, run:
 
@@ -125,8 +125,12 @@ For an explicit manual or CI check, run:
 introspection check
 ```
 
-Both paths use the same Rust validation core. The binary embedded in the npm
-package is an internal bridge for Pi startup, not a second user-facing CLI.
+That command uses the Rust validation core (`introspection-recipe-check`),
+which is also published as a crate and a Python binding so a host can embed it
+- the Introspection platform validates there, and blocks task creation on a
+failure. This npm package no longer ships a validator binary: a launch-time
+check was a third run of the same engine in the one place whose failure mode is
+a dead session, including when the binary simply could not be spawned.
 
 ## Host parity
 

package/docs/recipe-format.md

@@ -81,6 +81,43 @@ MUST commit one supported dependency lockfile: `package-lock.json`,
 `npm-shrinkwrap.json`, `pnpm-lock.yaml`, or `yarn.lock`. npm lockfiles MUST
 carry the same package name and version as `package.json`.
 
+## Connector tools
+
+`pi.connectors` declares official provider tools that the host may register for
+the Recipe. The declaration does not contain a connector ID, workspace ID, or
+credential. A host binds those values when it starts a task.
+
+```json
+{
+  "dependencies": {
+    "@introspection-ai/recipe-channel-slack": "^0.1.0"
+  },
+  "pi": {
+    "connectors": [
+      {
+        "provider": "slack"
+      }
+    ]
+  }
+}
+```
+
+Each provider may appear once. The host derives the package name from the
+provider. For example, `slack` resolves to
+`@introspection-ai/recipe-channel-slack`. The package owns its tool catalog
+and marks which tools are active by default.
+
+The provider package must be in the Recipe's production dependencies and
+lockfile. The host imports the package only when the Recipe declares the
+provider. The agent YAML file is the only place that narrows the package tool
+catalog. An agent lists each allowed tool by its full name, such as
+`channel_reply`, in its `tools` list. The host fails when the agent names a
+tool that the connector does not register.
+
+Chat providers share one connector shape. A channel connector registers the
+provider-neutral `channel_*` tools that its capabilities support. See
+[Channel tools](channels.md).
+
 ## Agents
 
 `pi.agents` may declare YAML agent definitions explicitly. When omitted,

package/docs/slack.md

@@ -0,0 +1,135 @@
+# Slack channel connector
+
+`@introspection-ai/recipe-channel-slack` is the Slack adapter for the
+[channel tools](channels.md). It supplies Slack Web API transport and a
+capability descriptor; the tool names and schemas are the neutral `channel_*`
+set, so a Recipe written against it is not written against Slack.
+
+Slack sends inbound events to the existing Events API webhook. The tools make
+ordinary HTTP requests to the Slack Web API with the bot that received the
+task. The package does not use Socket Mode, WebSockets, or a streamed tool
+protocol.
+
+## Declare it
+
+```json
+{
+  "dependencies": {
+    "@introspection-ai/recipe-channel-slack": "^0.1.0"
+  },
+  "pi": {
+    "connectors": [
+      {
+        "provider": "slack"
+      }
+    ]
+  }
+}
+```
+
+Commit the package manager lockfile. The host loads the package only for a
+Recipe that declares the connector.
+
+The connector package provides the complete Slack tool catalog. Each agent
+lists the exact `channel_*` tools it may call in its YAML file. `channel_reply`,
+`channel_read`, and `channel_react` are active from the start. Other selected
+tools are available through `tool_search`.
+
+## What Slack registers
+
+| Tool | Slack operation |
+| --- | --- |
+| `channel_reply` | `chat.postMessage` into the origin channel and thread |
+| `channel_read` | `conversations.replies` in a thread, else `conversations.history` |
+| `channel_react` | `reactions.add` or `reactions.remove` |
+| `channel_edit` | `chat.update` for a message the agent posted |
+| `channel_retract` | `chat.delete` for a message the agent posted |
+| `channel_fetch_file` | `files.info` plus a private file download |
+
+Slack history returns at most 15 messages to the agent per call. For a thread,
+the first call reads the thread and returns the newest messages. The adapter
+keeps older messages in the current session, and the returned opaque cursor
+pages backward through that cache without another `conversations.replies`
+request.
+
+The connector uses a customer owned internal Slack app. Slack gives internal
+apps the larger `conversations.replies` page and rate limits needed to read a
+thread before selecting its newest messages. The connector does not support a
+commercially distributed Slack app outside the Slack Marketplace, because
+Slack restricts those installations to 15 replies and one request per minute.
+
+`channel_attach` and `channel_post_document` are not registered: `files.uploadV2`
+and canvases are not implemented in this package yet, and the capability
+descriptor says so rather than registering tools that fail.
+
+None of these take a channel or thread argument. Every tool acts on the
+conversation the task came from. Author display names (`users.info`) and
+permalinks (`chat.getPermalink`) are resolved inside the adapter and attached to
+message rows and reply results, so there is no user lookup or permalink tool.
+Edit and retract also require an opaque reference for a message posted by this
+agent. They cannot act on another author's message.
+
+Workspace search, channel listing and joining, directory lookup, and
+cross-channel posting are unsupported. Their contract and access model are
+deferred to a separate proposal.
+
+## Cloud access
+
+The Recipe never receives the Slack bot token. The adapter sends the task
+locator to `INTROSPECTION_EGRESS_URL`, the provider proxy inside the
+Introspection environment, with the Slack host as the proxy route. The proxy
+verifies and removes the locator, checks the connector's granted scope and
+allowed path, and adds the bot token before the request leaves for Slack.
+
+The adapter refuses to send a task locator when the provider proxy URL is
+missing. It never falls back to sending the locator to Slack.
+
+After `channel_reply` succeeds in cloud, the adapter posts the `connector_posted`
+task event to the Data Plane, which checks the agent session, current run,
+provider, and origin channel before recording the new thread root. A later Slack
+reply then resumes the same task.
+
+Slack writes are attempted once. The adapter does not retry `chat.postMessage`,
+because Slack accepts no idempotency key for it. If Slack accepts the post but
+event recording fails, the tool returns the message reference and a
+`bridge_error`. It does not post again.
+
+## Test with introspection dev
+
+Run `introspection dev` from the Recipe repository. A Slack event sent to the
+development runtime starts a cloud sandbox with the local Recipe overlay, so the
+adapter uses the cloud task origin and provider proxy and needs no local Slack
+credential. Use `introspection dev --logs` for sandbox logs.
+
+## Test with introspection local
+
+An `introspection local` run has no inbound Slack event, cloud task origin, or
+credential proxy. Install dependencies, then set a bot token and a conversation:
+
+```bash
+pnpm install --frozen-lockfile
+export SLACK_BOT_TOKEN='xoxb-...'
+export SLACK_CHANNEL_ID='C0123456789'
+export SLACK_THREAD_TS='1234567890.123456' # optional
+introspection local -p 'Summarise this thread and reply.'
+```
+
+Local tools call Slack directly with `SLACK_BOT_TOKEN`. Local posts create no
+inbound task or reply bridge, because no Data Plane task exists.
+
+## File downloads
+
+`channel_fetch_file` writes a file under the task files directory and returns its
+path, media type, size, and SHA-256 digest. The bytes land in the workspace and
+not in model context. It accepts only a `file_…` handle from a `channel_read`
+attachment, so the bot's cross-channel file read is not reachable from model
+input. On the wire it accepts only `files.slack.com` download URLs, rejects
+redirects, caps the body at 100 MiB, checks the declared size, and removes
+partial files after a failure. The `video_low` variant uses Slack's smaller MP4
+rendition when one exists.
+
+## Direct host use
+
+The package exports `SlackChannelAdapter`, `createSlackChannelSession` and
+`slackChannelTarget` for custom hosts and tests, alongside the default
+`slackRecipeConnectorModule`. A normal Recipe uses `pi.connectors` instead.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@introspection-ai/recipes",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "The open format for vertical agents, built on Pi.",
   "license": "Apache-2.0",
   "type": "module",
@@ -9,8 +9,6 @@
   },
   "files": [
     "dist",
-    "vendor/mcp-client",
-    "vendor/introspection-recipe-check",
     "docs",
     "README.md",
     "package.json"
@@ -60,6 +58,10 @@
       "types": "./dist/api/session.d.ts",
       "import": "./dist/api/session.js"
     },
+    "./channels": {
+      "types": "./dist/channels/index.d.ts",
+      "import": "./dist/channels/index.js"
+    },
     "./test-utils": {
       "types": "./dist/test-utils.d.ts",
       "import": "./dist/test-utils.js"
@@ -78,7 +80,7 @@
     "@introspection-sdk/introspection-pi": "^0.22.0",
     "@opentelemetry/api": "^1.9.1",
     "ajv": "^8.20.0",
-    "mcporter": "0.13.6",
+    "mcporter": "0.13.7",
     "yaml": "^2.9.0"
   },
   "peerDependencies": {
@@ -89,24 +91,31 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@earendil-works/pi-agent-core": "0.84.2",
-    "@earendil-works/pi-ai": "0.84.2",
-    "@earendil-works/pi-coding-agent": "0.84.2",
-    "@earendil-works/pi-tui": "0.84.2",
+    "@earendil-works/pi-agent-core": "0.84.3",
+    "@earendil-works/pi-ai": "0.84.3",
+    "@earendil-works/pi-coding-agent": "0.84.3",
+    "@earendil-works/pi-tui": "0.84.3",
     "@types/node": "^26.1.2",
     "esbuild": "^0.28.1",
     "typebox": "^1.0.56",
     "typescript": "^7.0.2",
     "vitest": "^4.0.18"
   },
+  "optionalDependencies": {
+    "@introspection-ai/mcp-client-linux-x64": "0.22.0",
+    "@introspection-ai/mcp-client-linux-arm64": "0.22.0",
+    "@introspection-ai/mcp-client-darwin-arm64": "0.22.0",
+    "@introspection-ai/mcp-client-darwin-x64": "0.22.0"
+  },
   "scripts": {
     "build": "pnpm build:ts && pnpm build:native",
-    "build:ts": "rm -rf dist && tsc && node scripts/build-mcp-daemon.mjs",
-    "build:native": "cargo build --release -p pi-mcp-client && cargo build --release -p introspection-recipe-check --bin introspection-recipe-check && node scripts/package-mcp-client.mjs && node scripts/package-introspection-recipe-check.mjs",
+    "build:workspace-packages": "pnpm --filter './packages/**' build",
+    "build:ts": "rm -rf dist && tsc && node scripts/build-mcp-daemon.mjs && pnpm build:workspace-packages",
+    "build:native": "cargo build --release -p pi-mcp-client && node scripts/package-mcp-client.mjs",
     "bench:mcp-client": "pnpm build:ts && cargo build --release -p pi-mcp-client && node scripts/benchmark-mcp-client.mjs",
-    "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.test.json",
-    "test": "pnpm build:ts && cargo test -p pi-mcp-client -p introspection-recipe-check && cargo build -p pi-mcp-client && cargo build -p introspection-recipe-check --bin introspection-recipe-check && MCP_CLIENT_BIN=target/debug/mcp-client node scripts/package-mcp-client.mjs && vitest run",
-    "pack:check": "pnpm pack --dry-run --json | node scripts/check-npm-pack.mjs",
-    "clean": "rm -rf dist .turbo node_modules target vendor/mcp-client vendor/introspection-recipe-check"
+    "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.test.json && pnpm --filter './packages/**' typecheck",
+    "test": "pnpm build:ts && cargo test -p pi-mcp-client -p introspection-recipe-check && cargo build -p pi-mcp-client && MCP_CLIENT_BIN=target/debug/mcp-client node scripts/package-mcp-client.mjs && vitest run",
+    "pack:check": "pnpm pack --dry-run --json | node scripts/check-npm-pack.mjs && pnpm --filter './packages/**' pack:check",
+    "clean": "rm -rf dist .turbo node_modules target vendor/mcp-client"
   }
 }

package/dist/mcp-chunks/call-arguments-MCCBPJMY.js

@@ -1,15 +0,0 @@
-import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
-import {
-  parseCallArguments
-} from "./chunk-24FKKIXI.js";
-import "./chunk-FW5QVG6V.js";
-import "./chunk-NMF5S5DC.js";
-import "./chunk-EEYUPDRX.js";
-import "./chunk-ILSK6AWI.js";
-import "./chunk-SHZVDY6Z.js";
-import "./chunk-LYZRCACV.js";
-import "./chunk-DIIFWDZ7.js";
-import "./chunk-LRKZP7DJ.js";
-export {
-  parseCallArguments
-};

package/dist/mcp-chunks/client-B3FMQNGF.js

@@ -1,21 +0,0 @@
-import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
-import {
-  DaemonClient,
-  resolveDaemonPaths
-} from "./chunk-GQHTGV5E.js";
-import "./chunk-MDVNQ4HM.js";
-import "./chunk-XRRT3SZM.js";
-import "./chunk-JJG2OEHI.js";
-import "./chunk-LYZRCACV.js";
-import "./chunk-5HQYKAE7.js";
-import "./chunk-ETYYCEQF.js";
-import "./chunk-2CTVPSHF.js";
-import "./chunk-VREKED5H.js";
-import "./chunk-DIIFWDZ7.js";
-import "./chunk-AJPFOQLF.js";
-import "./chunk-LWVFSQYX.js";
-import "./chunk-LRKZP7DJ.js";
-export {
-  DaemonClient,
-  resolveDaemonPaths
-};

package/dist/mcp-chunks/daemon-command-BAREANTC.js

@@ -1,35 +0,0 @@
-import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
-import {
-  handleDaemonCli
-} from "./chunk-LI4L4FOV.js";
-import "./chunk-HULRE4D2.js";
-import "./chunk-RYAUNXFA.js";
-import "./chunk-WKUCIR2F.js";
-import "./chunk-VC6SKXTI.js";
-import "./chunk-FNQV2ONG.js";
-import "./chunk-VJ2TSA5R.js";
-import "./chunk-MNAVFYYV.js";
-import "./chunk-B4XFULJ6.js";
-import "./chunk-MWD5PZ4G.js";
-import "./chunk-RXSZ2W6Y.js";
-import "./chunk-NSZY5WLR.js";
-import "./chunk-54UGGTOX.js";
-import "./chunk-ZNKNF2BV.js";
-import "./chunk-K56RW4HB.js";
-import "./chunk-N2HVJU7X.js";
-import "./chunk-GQHTGV5E.js";
-import "./chunk-MDVNQ4HM.js";
-import "./chunk-XRRT3SZM.js";
-import "./chunk-JJG2OEHI.js";
-import "./chunk-LYZRCACV.js";
-import "./chunk-5HQYKAE7.js";
-import "./chunk-ETYYCEQF.js";
-import "./chunk-2CTVPSHF.js";
-import "./chunk-VREKED5H.js";
-import "./chunk-DIIFWDZ7.js";
-import "./chunk-AJPFOQLF.js";
-import "./chunk-LWVFSQYX.js";
-import "./chunk-LRKZP7DJ.js";
-export {
-  handleDaemonCli
-};

package/dist/mcp-chunks/runtime-Z45IVD24.js

@@ -1,39 +0,0 @@
-import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
-import {
-  callOnce,
-  createRuntime
-} from "./chunk-WKUCIR2F.js";
-import "./chunk-VC6SKXTI.js";
-import "./chunk-FNQV2ONG.js";
-import "./chunk-VJ2TSA5R.js";
-import "./chunk-MNAVFYYV.js";
-import "./chunk-B4XFULJ6.js";
-import "./chunk-MWD5PZ4G.js";
-import "./chunk-RXSZ2W6Y.js";
-import {
-  MCPORTER_VERSION
-} from "./chunk-NSZY5WLR.js";
-import "./chunk-54UGGTOX.js";
-import "./chunk-ZNKNF2BV.js";
-import "./chunk-K56RW4HB.js";
-import "./chunk-XRRT3SZM.js";
-import "./chunk-JJG2OEHI.js";
-import "./chunk-LYZRCACV.js";
-import "./chunk-5HQYKAE7.js";
-import {
-  readJsonFile,
-  writeJsonFile
-} from "./chunk-ETYYCEQF.js";
-import "./chunk-2CTVPSHF.js";
-import "./chunk-VREKED5H.js";
-import "./chunk-DIIFWDZ7.js";
-import "./chunk-AJPFOQLF.js";
-import "./chunk-LWVFSQYX.js";
-import "./chunk-LRKZP7DJ.js";
-export {
-  MCPORTER_VERSION,
-  callOnce,
-  createRuntime,
-  readJsonFile,
-  writeJsonFile
-};

package/dist/recipe-check.d.ts

@@ -1,18 +0,0 @@
-export interface RecipeCheckDiagnostic {
-    code: string;
-    path: string;
-    span?: {
-        line: number;
-        column: number;
-    };
-    message: string;
-    help?: string;
-}
-export interface RecipeCheckReport {
-    valid: boolean;
-    diagnostics: RecipeCheckDiagnostic[];
-    resources?: Record<string, number>;
-}
-export declare function checkRecipeAtLoad(recipeDir: string, env: NodeJS.ProcessEnv): Promise<RecipeCheckReport>;
-export declare function formatRecipeDiagnostics(diagnostics: readonly RecipeCheckDiagnostic[]): string;
-//# sourceMappingURL=recipe-check.d.ts.map

package/dist/recipe-check.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"recipe-check.d.ts","sourceRoot":"","sources":["../src/recipe-check.ts"],"names":[],"mappings":"AAiBA,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC;IACxC,OAAO,EAAE,MAAM,CAAC;IAChB,IAAI,CAAC,EAAE,MAAM,CAAC;CACf;AAED,MAAM,WAAW,iBAAiB;IAChC,KAAK,EAAE,OAAO,CAAC;IACf,WAAW,EAAE,qBAAqB,EAAE,CAAC;IACrC,SAAS,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACpC;AAwPD,wBAAsB,iBAAiB,CACrC,SAAS,EAAE,MAAM,EACjB,GAAG,EAAE,MAAM,CAAC,UAAU,GACrB,OAAO,CAAC,iBAAiB,CAAC,CAyC5B;AAED,wBAAgB,uBAAuB,CACrC,WAAW,EAAE,SAAS,qBAAqB,EAAE,GAC5C,MAAM,CAUR"}