experimental-ash 0.7.3 → 0.7.4

package/CHANGELOG.md

@@ -0,0 +1,205 @@
+# experimental-ash
+
+## 0.7.4
+
+### Patch Changes
+
+- ada9d2f: chore(pkg): ship `CHANGELOG.md` in the published tarball
+
+  Adds `CHANGELOG.md` to the `files` allowlist in `packages/ash/package.json`
+  and references it from the package README. Agents installing
+  `experimental-ash` can now read `node_modules/experimental-ash/CHANGELOG.md`
+  directly to evaluate the value of upgrading without leaving the project.
+
+## 0.7.3
+
+### Patch Changes
+
+- 974071d: fix(slack,schedule): repair `ScheduleDispatcher` ↔ `slackChannel.receive` contract; honor `input.auth`
+
+  Every schedule targeting a Slack channel threw `TypeError: send is not
+a function` at cron fire. `ScheduleDispatcher.trigger` called
+  `route.receive(input, { agent, waitUntil })`, but `slackChannel.receive`
+  was designed (per #474) to receive `{ send }`. The dispatcher was the
+  broken half — it never built a `send` via `createSendFn` and never
+  honored the contract `defineChannel` documents. `slackChannel.receive`
+  also hardcoded `auth: null` and ignored `ReceiveInput.auth`, so
+  schedules could not propagate `APP_AUTH` and no cross-channel
+  programmatic initiator could thread its principal through.
+
+  The fix lands the schedule dispatcher cleanly on the `receive` / `send`
+  / `Session` vocabulary from #474: build `send` via `createSendFn`,
+  call `receive(input, { send })`, return the `Session`. Same
+  fire-and-forget discipline HTTP routes already use — the workflow
+  runtime owns terminal completion and its own failure observability,
+  so `dispatchScheduleTask` no longer awaits `handle.result` and drops
+  the logged-only `status` field from its return value.
+  `slackChannel.receive` propagates `input.auth` into `send(...)`, and
+  `ChannelConfig.receive` / `Channel.receive` / `CompiledChannel.receive`
+  gain `auth: SessionAuthContext | null` on the input shape so receive
+  implementers can read the caller's principal.
+
+  Type-system hardening so this kind of drift can't recur:
+  `ResolvedChannelDefinition.receive` was typed
+  `(...args: any[]) => Promise<any>` with an eslint-disable — the
+  escape hatch that let the dispatcher pass a wrong-shape ctx without a
+  typecheck error. Now typed precisely as `CompiledChannel["receive"]`.
+  The matching `as` casts in `resolve-channel.ts` and the `as` cast the
+  dispatcher used go away. The legacy authored `Route` shape
+  (`{ fetch, receive? }`) and every fallback that hedged between it and
+  `CompiledChannel` are deleted — dead in practice (everything authored
+  goes through `defineChannel`), and the union was the only reason the
+  `any[]` typing existed. Reintroducing the original bug shape
+  (destructuring `{ agent, waitUntil }`) now fails typecheck with
+  `Property 'agent' does not exist on type '{ send: SendFn<…> }'`
+  instead of crashing at cron fire.
+
+## 0.7.2
+
+### Patch Changes
+
+- b01d908: refactor(channels): rename the canonical session channel from `http` to `ash`
+
+  The framework's built-in session channel — the routes documented in
+  `docs/external-agent-protocol.md` (`POST /ash/v1/session`, `POST
+/ash/v1/session/:sessionId`, `GET /ash/v1/session/:sessionId/stream`) — is
+  now consistently named `"ash"` across every layer instead of being split
+  between `"http"` (in the function name) and `"default"` (in the override
+  file convention).
+
+  Breaking changes — agents that override the framework default must update:
+
+  - Import path `experimental-ash/channels/http` → `experimental-ash/channels/ash`.
+  - Function `httpChannel(...)` → `ashChannel(...)`.
+  - Type `HttpRouteInput` → `AshChannelInput`.
+  - Override file `agent/channels/default.ts` → `agent/channels/ash.ts`.
+  - Framework channel name `"default"` → `"ash"` (relevant if a project
+    uses `disableRoute()` to disable the framework default; the file must
+    now be named `ash.ts`).
+  - Auto-generated continuation tokens minted by the framework switch
+    from the `http:` prefix to `ash:`. The values stay opaque to clients;
+    the change is only visible in logs.
+
+  Why: "HTTP" said nothing useful (every channel is HTTP — Slack webhooks,
+  custom `defineChannel` routes, etc.), and "default" said nothing about
+  what the file actually was. The new name mirrors the URL prefix
+  (`/ash/v1/...`), the stream headers (`x-ash-session-id`,
+  `x-ash-stream-format`), and the package name itself, so the file convention
+  (`agent/channels/ash.ts`), the function (`ashChannel`), the import path
+  (`experimental-ash/channels/ash`), and the framework channel name (`"ash"`)
+  all say the same thing.
+
+  Migration for an existing app:
+
+  ```diff
+  - // agent/channels/default.ts
+  - import { httpChannel } from "experimental-ash/channels/http";
+  + // agent/channels/ash.ts
+  + import { ashChannel } from "experimental-ash/channels/ash";
+    import { vercelOidc } from "experimental-ash/channels/auth";
+
+  - export default httpChannel({ auth: vercelOidc() });
+  + export default ashChannel({ auth: vercelOidc() });
+  ```
+
+## 0.7.1
+
+### Patch Changes
+
+- 3e4bc51: feat(slack): restore attachment ingest + fix HITL round-trip + defineChannel `attachments` field
+
+  Two regressions introduced by the 0.6 channel redesign (#474) that
+  deleted `createSlackBaseAdapter`, plus a focused public extension
+  point on `defineChannel` for channel-owned attachment resolution.
+
+  **Attachment ingest**
+
+  `slackChannel` now folds Slack file uploads into the user turn as AI
+  SDK `FilePart`s carrying opaque `ash-attachment:` refs, and declares
+  the matching `AttachmentResolver` via the new top-level `attachments`
+  config field on `defineChannel`. The framework's existing staging
+  pipeline resolves the refs with the bot token, writes the bytes to
+  `/workspace/attachments/<sha>/<name>` in the sandbox, and hands the
+  model either inline bytes (small images and PDFs) or a sandbox path
+  the agent's filesystem tools can open. Audio and video attachments
+  are skipped; oversized or disallowed-media attachments are dropped
+  with a warning so a single bad upload never blocks the text portion
+  of a mention. The new `SlackChannelConfig.uploadPolicy` mirrors
+  `httpChannel`'s policy shape; the default cap is 25 MB.
+
+  **HITL widget round-trip**
+
+  The default `input.requested` handler used to encode `action_id` as
+  `ash_input_<requestId>_<optionId>` and decode it by splitting on `_`.
+  Since `requestId` is the AI SDK `action.callId` and always contains
+  underscores (`call_…`, `toolu_…`), the decoder silently dropped every
+  HITL click. It also only rendered buttons and only read
+  `action.value`, so radio-button and static-select widgets could
+  neither be rendered by the default handler nor parsed by the channel
+  route.
+
+  Fixed by:
+
+  - Encoding `action_id` as `ash_input:<requestId>`. The colon
+    delimiter is not valid inside an AI SDK call id, so the decode is
+    unambiguous for any `requestId` shape.
+  - Rendering radio_buttons for select-display requests with ≤6 options
+    and a static_select dropdown above that, matching pre-redesign
+    behavior.
+  - Extracting `selected_option.value` for radio / static_select clicks
+    on the route handler.
+  - Exposing the parsed selection on
+    `SlackInteractionAction.selectedOptionValue` so end-user
+    `onInteraction` handlers that render custom radio / select widgets
+    can read it too.
+
+  **`defineChannel.attachments`**
+
+  `ChannelConfig` gains an optional top-level `attachments?:
+AttachmentResolver` field, mirroring how `state`, `routes`, and
+  `events` are declared:
+
+  ```ts
+  defineChannel({
+    state: {
+      /* … */
+    },
+    routes: [
+      /* … */
+    ],
+    events: {
+      /* … */
+    },
+    attachments: myResolver,
+  });
+  ```
+
+  `AttachmentResolver` is now exported from `experimental-ash/channels`
+  so callers can type their resolver implementations cleanly. The Slack
+  channel is the first consumer; any future custom channel (Discord,
+  Teams, …) that needs an attachment resolver uses the same field.
+
+## 0.7.0
+
+### Minor Changes
+
+- 6bf383a: chore(ash): rename `system` file to `instructions` file
+
+## 0.6.2
+
+### Patch Changes
+
+- 4f875e3: Expose `messageTs` on `SlackInteractionAction` so `onInteraction` handlers can `chat.update` the clicked message in place. `ctx.slack.threadTs` resolves to the thread root when the component lives inside a thread reply, so updates targeting the clicked message previously had no way to learn its `ts`.
+- 224743e: chore: abstract sandbox types to be shared, and reuse AI SDK `Sandbox` abstraction definition where reasonable
+
+## 0.6.1
+
+### Patch Changes
+
+- ff9425d: Export `Channel` from `experimental-ash/channels` and `SlackChannelState` from `experimental-ash/channels/slack` so app authors can use `slack()` / `slackChannel()` from a `channels/slack.ts` module without the TypeScript "inferred type cannot be named" error when `declaration` is enabled. The slack helpers also stop redefining a private `SlackChannelState` and now share the canonical one from `slackChannel.ts`.
+
+## 0.6.0
+
+### Minor Changes
+
+- 90ce74f: Initial changeset release

package/dist/src/internal/application/package.js

@@ -6,7 +6,7 @@ import { ASH_PACKAGE_NAME } from "#package-name.js";
 let cachedPackageInfo;
 // The package build stamps the published version into `dist` so bundled
 // deployments can still report package metadata without resolving package.json.
-const BUNDLED_FALLBACK_PACKAGE_VERSION = "0.7.3";
+const BUNDLED_FALLBACK_PACKAGE_VERSION = "0.7.4";
 const BUNDLED_FALLBACK_PACKAGE_VERSION_PLACEHOLDER = "__ASH_PACKAGE_VERSION_PLACEHOLDER__";
 const WORKFLOW_MODULE_ALIASES = {
     "workflow/api": "src/compiled/@workflow/core/runtime.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "experimental-ash",
-  "version": "0.7.3",
+  "version": "0.7.4",
   "bin": {
     "ash": "./bin/ash.js",
     "experimental-ash": "./bin/ash.js"
@@ -8,6 +8,7 @@
   "files": [
     "bin",
     "dist",
+    "CHANGELOG.md",
     "README.md"
   ],
   "type": "module",