stitchkit 0.96.1 → 0.98.0

package/llms/{upgrading-0.70.0-0.96.0.txt → upgrading-0.72.0-0.98.0.txt}

@@ -1,14 +1,75 @@
-# Upgrading 0.70.0 → 0.96.0 — stitchkit docs slice
+# Upgrading 0.72.0 → 0.98.0 — stitchkit docs slice
 
 > Generated from the `docs/` tree by `bun run gen:llms`. The index of all slices is
 > `llms.txt` in this package.
 
-Contains: Guide: Upgrading, 0.70.0 → 0.96.0  (docs/guide/upgrading.md)
+Contains: Guide: Upgrading, 0.72.0 → 0.98.0  (docs/guide/upgrading.md)
 
 ==============================================================================
-# Guide: Upgrading, 0.70.0 → 0.96.0  (docs/guide/upgrading.md)
+# Guide: Upgrading, 0.72.0 → 0.98.0  (docs/guide/upgrading.md)
 ==============================================================================
 
+## Released migration: 0.98.0
+
+### automatic stdin availability
+
+**Who must act:** CLI applications or scripts relying on automatic stdin routing
+from a producer that can take more than 250 ms to write its first byte.
+
+Automatic routing now probes for the first byte for 250 ms. An empty open pipe
+leaves the required field unset and normal validation reports its name. Once
+data arrives, the entire stream is read until EOF without a total deadline.
+
+```sh
+# before: may now fail if the producer starts late
+slow-producer | myapp generate
+# after: provide the value explicitly after the producer completes
+myapp generate --prompt "$(slow-producer)"
+```
+
+For large input that should stay in a pipe, supply a `CliConfig.stdin` reader
+that waits for the producer and EOF; this existing hook is not wrapped in the
+availability probe. A custom reader owns its limits and error handling.
+`-` remains literal data. TTY and empty EOF produce ordinary validation errors;
+explicit arguments skip stdin. JSONL stream/batch commands, MCP/serve and
+long-running handlers have no new deadline. See ADR 0203.
+
+## Released migration: 0.97.0
+
+### schedule delivery
+
+**Who must act:** consumers of `createAgentScheduleService`, exhaustive switches on
+`AgentSchedule.state`, and operators opening existing agent-runtime SQLite stores.
+
+- Stop old scheduler processes and back up SQLite before startup. The store migrates
+  transactionally to v4; old binaries cannot open it. Rollback uses the backup.
+- Handle `failed` as a terminal schedule state. To refuse future delivery (including
+  recurring delivery), return `{ status: 'terminal', reason: 'destination closed' }`.
+  The occurrence remains unadvanced; `schedule/failed` carries `terminal: true`.
+- A throw or `{ status: 'retry', reason: 'temporarily unavailable' }` retries the same
+  key after 1, 2, 4, 8, 16, 32, then 60 seconds. `nextAt` remains the original due time;
+  `retryAt`, `attempts` and `lastError` expose retry diagnostics. Success clears them.
+- Resolve `void` only after durable consumer admission. Honor the supplied `signal`:
+  dispatch has a 30-second deadline and a 60-second lease. Durable deduplication by
+  `idempotencyKey` is required even after abort or crash; do not implement sleeps in dispatch.
+- Stale/cancelled attempts emit no `schedule/fired` or `schedule/late`. Observe the
+  cancellation event instead of relying on a synthetic cancelled firing.
+
+```ts
+// before
+async function dispatch(request) {
+  if (await destinationClosed(request.conversationId)) throw new Error('closed')
+  await admit(request)
+}
+// after: use this callback as createAgentScheduleService({ dispatch, ... })
+async function dispatch(request) {
+  if (await destinationClosed(request.conversationId)) {
+    return { status: 'terminal', reason: 'destination closed' }
+  }
+  await admit({ ...request, signal: request.signal }) // durably deduplicates idempotencyKey
+}
+```
+
 ## Released migration: 0.96.0
 
 ### resource-context-admission
@@ -1040,108 +1101,3 @@ const snapshot: CreditWindowSnapshot = { state: 'open', capacityBytes: 100, /*
 // after
 const snapshot: CreditWindowSnapshot = { state: 'open', capacityBytes: 100, /* … */ waiting: 0 }
 ```
-
-## Released migration: 0.71.0
-
-The Agent coding tools. Two of the three changes are visible to the compiler;
-the third is the one to read carefully, because nothing will point at it.
-
-### If you implement `authorize`
-
-The operation union gained `edit`, `list` and `glob` and lost `patch`. An
-exhaustive matcher stops compiling and the compiler shows you every arm. **A
-matcher with a default branch does not**, and that is the dangerous case:
-
-```ts
-// before — and after this upgrade, silently wrong in both directions
-if (request.operation === 'patch') return reviewPatch(request)
-return true            // now also authorizes edit, list and glob
-// …or: return false   // now also kills edit_file
-```
-
-```ts
-// after
-switch (request.operation) {
-  case 'edit':   return reviewEdit(request)   // the old `patch` payload, unchanged
-  case 'list':
-  case 'glob':   return true                  // or your own policy
-  // …existing read / write / search / shell / artifact-read arms
-}
-```
-
-`write` gained `createsDirectories` — the workspace-relative directories the
-call would create, outermost first, reported **before** anything is created. A
-host that wants to refuse implicit directory creation now can.
-
-### If you call `apply_patch`
-
-It is `edit_file`, and it is one call:
-
-```ts
-// before
-const read = await readFile({ path })
-await applyPatch({ path, baseSha256: read.sha256, oldText, newText, dryRun: true })
-await applyPatch({ path, baseSha256: read.sha256, oldText, newText, dryRun: false })
-
-// after
-await editFile({ path, oldText, newText })
-```
-
-`expectedSha256` is optional and still refuses a stale base with `CONFLICT` when
-you pass it; `edit_file` returns the resulting `sha256`, so a chain of edits
-never needs to re-read. If you key an approval policy or a UI label on the string
-`apply_patch`, update the key — nothing will fail loudly.
-
-### If you match on `INTERNAL_SERVER_ERROR` from a coding tool
-
-Ordinary outcomes no longer arrive that way. A missing file is `NOT_FOUND`, an
-existing file without `overwrite` is `CONFLICT`, an ambiguous snippet is
-`CONFLICT` with the occurrence count, a path outside the root is `FORBIDDEN`.
-Code that treated any coding-tool failure as an internal fault will now see
-codes it did not before; code that showed the model an empty error now has a
-sentence and a `hint` to show it. Host-level causes are unchanged and still
-scrubbed.
-
-### If you write files into new directories
-
-Nothing to change: `write_file` creates missing parents inside the root. Read
-`createdDirectories` in the result if you want to notice a typo — a path that
-was a failure before is now a successful write into a new tree.
-
-### If you want a step to know its context budget
-
-Opt in by reading it; nothing is injected for you:
-
-```ts
-loop: {
-  prepareStep: ({ contextUsage }) => {
-    const used = contextUsage?.usedTokens
-    if (used?.provenance === 'unavailable') return {}      // no step has landed yet
-    const fraction = (used?.value ?? 0) / (contextUsage?.contextWindow ?? 1)
-    // …render it wherever you put it
-    return {}
-  },
-}
-```
-
-Put it at the **tail** of the conversation rather than in the system
-instructions unless you have a reason: changing the system prompt on every step
-invalidates the provider's prefix cache for the whole conversation, and on a long
-run that is a multiple of the input cost.
-
-## Released migration: 0.70.0
-
-### Descriptor-backed Agent filesystem containment
-
-Built-in coding file/search tools and `createAgentHarnessFileResources` now require a runtime
-that can address an opened directory descriptor: Linux `/proc/self/fd`, or the packaged macOS
-Node-API backend added in 0.70.1. This is what keeps a mutable parent rename or outside-symlink replacement from changing
-the authorized target between validation and the actual effect.
-
-No call-site change is needed on those platforms. The 0.70.0 notes incorrectly inferred macOS and
-FreeBSD support from `/dev/fd`; macOS is restored by 0.70.1 and FreeBSD remains unsupported. On
-Windows or another platform without that
-boundary, move the built-in filesystem operations to a supported worker or replace them with
-application-owned tools backed by an equivalent native handle API. They fail closed rather than
-falling back to path spelling. `run_command` remains separately available under its explicit
-executable alias and authorization policy; this change does not claim an executable sandbox.

package/llms/upgrading.txt

@@ -11,9 +11,9 @@ Contains: Guide: Upgrading, general  (docs/guide/upgrading.md)
 
 Load this slice, then every range slice between your installed version and the target:
 
-- 0.70.0 → 0.96.0: `llms/upgrading-0.70.0-0.96.0.txt`
-- 0.57.0 → 0.69.0: `llms/upgrading-0.57.0-0.69.0.txt`
-- 0.37.0 → 0.56.0: `llms/upgrading-0.37.0-0.56.0.txt`
+- 0.72.0 → 0.98.0: `llms/upgrading-0.72.0-0.98.0.txt`
+- 0.59.0 → 0.71.0: `llms/upgrading-0.59.0-0.71.0.txt`
+- 0.37.0 → 0.58.0: `llms/upgrading-0.37.0-0.58.0.txt`
 
 # Upgrading stitchkit
 

package/llms-full.txt

@@ -68,11 +68,11 @@ own, recorded as an ADR.
 | `stitchkit/geo` | server (Bun or Node) | evolving | managed GeoIP reader generations, last-known-good reload and the optional MaxMind adapter |
 | `stitchkit/oauth` | browser **and** server | evolving | provider-neutral Authorization Code + PKCE request and one-shot callback transaction mechanics |
 | `stitchkit/google` | server (Bun or Node) | evolving | optional Google code exchange and verified OIDC identity adapter |
-| `stitchkit/observability` | server | stable<br>_redefined in 2 of the 41 minors since 0.56.2, most recently 0.92.0_ | request/tool event projections — `createObservability`, trace context, sanitisation |
+| `stitchkit/observability` | server | stable<br>_redefined in 2 of the 43 minors since 0.56.2, most recently 0.92.0_ | request/tool event projections — `createObservability`, trace context, sanitisation |
 | `stitchkit/testing` | tests on Bun or Node | stable | in-process generated clients over a real Fetch handler, plus the managed-resource conformance kit |
 | `stitchkit/declaration` | browser + build and deployment tooling (Bun or Node) | evolving | `ProjectDeclarationSchema` — the one machine-readable statement a repository makes about itself |
 | `stitchkit/react` | browser + server rendering | stable | `createCursorQuery`, `createCacheBridge`, QueryClient and `ApiError` retry policy |
-| `stitchkit/agent-runtime` | server | evolving<br>_redefined in 21 of the 41 minors since 0.56.2, most recently 0.94.0_ | optional durable conversation/run loop, history, models, prompts, fencing and events |
+| `stitchkit/agent-runtime` | server | evolving<br>_redefined in 22 of the 43 minors since 0.56.2, most recently 0.97.0_ | optional durable conversation/run loop, history, models, prompts, fencing and events |
 | `stitchkit/agent-runtime/sandbox` | server | evolving | optional Linux Bubblewrap sessions, durable workspaces and a host HTTP credential gateway; see [sandbox guide](sandbox.md) |
 | `stitchkit/agent-runtime/testing` | tests on Bun or Node | evolving | credential-free replay, scripted provider faults, deterministic race controls and the agent-store conformance kit |
 | `stitchkit/agent-runtime/harness` | server | evolving | resource-aware process-local facade over the canonical Agent runtime; supervision stays outside |
@@ -82,7 +82,7 @@ own, recorded as an ADR.
 | `stitchkit/agent-runtime/sqlite/bun` | server (Bun) | evolving | durable built-in SQLite store for the agent runtime |
 | `stitchkit/agent-runtime/sqlite/node` | server (Node ≥ 22.5) | evolving | durable built-in SQLite store for the agent runtime |
 | `stitchkit-tui` | terminal (Bun) | evolving | optional official OpenTUI host over a caller-composed headless runtime |
-| `stitchkit/application` | browser + server | evolving<br>_redefined in 9 of the 41 minors since 0.56.2, most recently 0.96.0_ | managed resource graph, readiness, admission, schedules, subtree restart and bounded shutdown |
+| `stitchkit/application` | browser + server | evolving<br>_redefined in 9 of the 43 minors since 0.56.2, most recently 0.96.0_ | managed resource graph, readiness, admission, schedules, subtree restart and bounded shutdown |
 | `stitchkit/application/grammy` | server | evolving | a grammY bot as application resources — configuration, then polling with updates admitted by batch — and the webhook adapter |
 | `stitchkit/application/opentelemetry` | server | evolving | maps application snapshots onto an injected OpenTelemetry `Meter` |
 | `stitchkit/application/schemas` | browser + server | evolving | the application's snapshot, health and shutdown schemas alone, without the kernel |
@@ -4846,7 +4846,7 @@ description: Configure Stitchkit's optional durable history, stream loop, run co
 type: architecture
 status: active
 created: 2026-08-22
-updated: 2026-08-29
+updated: 2026-09-26 16:00 +07:00
 ---
 
 # Agent application runtime
@@ -5463,6 +5463,23 @@ has invoked a tool is never automatically replayed.
 `createAgentScheduleService` persists `at`, `after` and `every` input. Repeating
 schedules require an explicit IANA time zone. Dispatch uses a stable
 `schedule:<id>:<occurrence>` idempotency key, and restart lateness is recorded.
+Resolve `void` after durable admission; return `{ status: 'retry', reason }` for a
+transient refusal or `{ status: 'terminal', reason }` to stop the entire schedule in
+`failed` state. Throws retry too. Backoff is 1, 2, 4, 8, 16, 32, then 60 seconds,
+capped at 60 seconds and persisted across restart. `retryAt`, `attempts` and `lastError`
+show retry diagnostics; success resets them. `nextAt` and `lateByMs` retain the original
+occurrence time. Recurring schedules fire once after an idle stretch and advance to the
+next future slot on their original cadence.
+
+Dispatch receives an `AbortSignal`, has a 30-second deadline and holds a unique
+60-second lease. A late or cancelled attempt cannot settle or emit firing events.
+Honor the signal and durably deduplicate the key: a crash after admission but before
+settlement can replay delivery. This is at-least-once, not exactly-once.
+Due selection is indexed, limited to 32 parallel deliveries per tick; one hung batch
+can delay newly due work by at most its deadline. The service keeps one nearest-due
+timer plus per-attempt deadline timers. Storage failures use a bounded recovery timer;
+idle ticks do not write. SQLite v4 migration preserves due times and claims; stop older
+scheduler processes before migration. See [ADR 0202](../decisions/0202-schedule-retries-preserve-occurrence-identity.md).
 `createAgentScheduleTools` exposes the exact `schedule_after`, `schedule_at`,
 `schedule_every`, `schedule_list` and `schedule_cancel` surface.
 
@@ -7936,6 +7953,21 @@ fields in declaration order, so `myapp generate "a fox"` is
 `--prompt "a fox"`. A piped value fills the first required unset field:
 `echo "a fox" | myapp generate`.
 
+Automatic stdin routing skips TTYs and waits at most **250 ms for the first byte**.
+An empty open pipe or EOF without data leaves the field unset, so normal schema
+validation reports the missing field instead of waiting indefinitely. Once any
+byte arrives, the reader collects the entire stream until EOF, including chunks
+separated by long pauses; it decodes UTF-8 after collecting all bytes and trims
+surrounding whitespace. Read errors or a close before EOF fail the invocation.
+Explicit arguments and commands without required unset fields never read stdin.
+
+A producer that takes longer than 250 ms to start must supply its value as an
+argument (for example, `myapp generate --prompt "$(slow-producer)"`) or the
+application must provide an explicit `CliConfig.stdin` reader that waits for it.
+That hook is not wrapped in the availability timeout. `-` remains literal data,
+not a special stdin marker. JSONL stream/batch commands own their input and wait
+for lines as usual; MCP/serve and long-running handlers have no new deadline.
+
 A token is an option only when it is a long form (`--name`, `--name=value`,
 `--`) or `-` followed by a letter. Anything else that starts with `-` is data:
 `myapp note a "- item"` fills a positional, and after an option that expects a
@@ -13002,6 +13034,67 @@ analytics policy belong to the application.
 
 # Upgrading stitchkit
 
+## Released migration: 0.98.0
+
+### automatic stdin availability
+
+**Who must act:** CLI applications or scripts relying on automatic stdin routing
+from a producer that can take more than 250 ms to write its first byte.
+
+Automatic routing now probes for the first byte for 250 ms. An empty open pipe
+leaves the required field unset and normal validation reports its name. Once
+data arrives, the entire stream is read until EOF without a total deadline.
+
+```sh
+# before: may now fail if the producer starts late
+slow-producer | myapp generate
+# after: provide the value explicitly after the producer completes
+myapp generate --prompt "$(slow-producer)"
+```
+
+For large input that should stay in a pipe, supply a `CliConfig.stdin` reader
+that waits for the producer and EOF; this existing hook is not wrapped in the
+availability probe. A custom reader owns its limits and error handling.
+`-` remains literal data. TTY and empty EOF produce ordinary validation errors;
+explicit arguments skip stdin. JSONL stream/batch commands, MCP/serve and
+long-running handlers have no new deadline. See ADR 0203.
+
+## Released migration: 0.97.0
+
+### schedule delivery
+
+**Who must act:** consumers of `createAgentScheduleService`, exhaustive switches on
+`AgentSchedule.state`, and operators opening existing agent-runtime SQLite stores.
+
+- Stop old scheduler processes and back up SQLite before startup. The store migrates
+  transactionally to v4; old binaries cannot open it. Rollback uses the backup.
+- Handle `failed` as a terminal schedule state. To refuse future delivery (including
+  recurring delivery), return `{ status: 'terminal', reason: 'destination closed' }`.
+  The occurrence remains unadvanced; `schedule/failed` carries `terminal: true`.
+- A throw or `{ status: 'retry', reason: 'temporarily unavailable' }` retries the same
+  key after 1, 2, 4, 8, 16, 32, then 60 seconds. `nextAt` remains the original due time;
+  `retryAt`, `attempts` and `lastError` expose retry diagnostics. Success clears them.
+- Resolve `void` only after durable consumer admission. Honor the supplied `signal`:
+  dispatch has a 30-second deadline and a 60-second lease. Durable deduplication by
+  `idempotencyKey` is required even after abort or crash; do not implement sleeps in dispatch.
+- Stale/cancelled attempts emit no `schedule/fired` or `schedule/late`. Observe the
+  cancellation event instead of relying on a synthetic cancelled firing.
+
+```ts
+// before
+async function dispatch(request) {
+  if (await destinationClosed(request.conversationId)) throw new Error('closed')
+  await admit(request)
+}
+// after: use this callback as createAgentScheduleService({ dispatch, ... })
+async function dispatch(request) {
+  if (await destinationClosed(request.conversationId)) {
+    return { status: 'terminal', reason: 'destination closed' }
+  }
+  await admit({ ...request, signal: request.signal }) // durably deduplicates idempotencyKey
+}
+```
+
 ## Released migration: 0.96.0
 
 ### resource-context-admission
@@ -17685,7 +17778,7 @@ Server-only optional application runtime. See the
 | `AgentSandboxProcess` / `AgentSandboxOutputStream` | _types_ | structural child/output interface for optional lifecycle-owned `AgentProcessSandbox.spawn`, without Node ambient type dependencies |
 | `AgentEventSearchResultSchema` / `AgentEventSearchResult` / `createSqliteAgentEventSearch` / `createAgentEventSearchTools` | schema / _type_ / functions | authorized FTS5 search with exact event addresses and `session_*` tools |
 | `createSqliteAgentSpillStore` | function | durable content-address-checked artifact storage, bounded read/search, retention facts and archive participation |
-| `AgentScheduleSchema` / `AgentSchedule` / `AgentScheduleService` / `createAgentScheduleService` / `createAgentScheduleTools` | schema / _types_ / functions | durable `at`/`after`/timezone-explicit `every`, stable dispatch identity and Agent tools |
+| `AgentScheduleSchema` / `AgentSchedule` / `AgentScheduleService` / `AgentScheduleDeliveryOutcomeSchema` / `AgentScheduleDeliveryOutcome` / `createAgentScheduleService` / `createAgentScheduleTools` | schemas / _types_ / functions | durable `at`/`after`/timezone-explicit `every`, indexed retry eligibility, typed retry/terminal failure, bounded dispatch and fenced stable occurrence identity (ADR 0202) |
 | `AgentChildBudgetSchema` / `AgentChildBudget` / `AgentChildStateSchema` / `AgentChildState` / `AgentChildRecordSchema` / `AgentChildRecord` | schema / _type_ | durable child graph, bounded seed and measured budget state |
 | `AgentChildBlockingKindSchema` / `AgentChildBlockingKind` / `AgentChildBlockingSourceSchema` / `AgentChildBlockingSource` / `AgentChildBlockingEventSchema` / `AgentChildBlockingEvent` / `AgentChildBlockingDecision` | schemas / _types_ | parent-owned request identities; responses discriminate approval decisions from JSON input values |
 | `AgentChildHandle` / `AgentChildManager` / `SqliteAgentChildManagerConfig` / `createSqliteAgentChildManager` / `createAgentChildTools` / `agentChildBudgetStopPolicy` | _type_ / functions | host execution port, child lifecycle, cascade (given to `createAgentRuntime` as `children`), messaging, Agent tools, and the child runtime's own budget stop policy — `recordStepUsage` at every step boundary, `policy_stop` as `child-budget` when spent |

package/llms.txt

@@ -16,13 +16,13 @@ Load the slice for each entrypoint your code imports — `import … from 'stitc
 - **stitchkit/tools/contract**: [llms/tools-contract.txt](llms/tools-contract.txt) 0.2 KB
 - **stitchkit/tools/invoker**: [llms/tools-invoker.txt](llms/tools-invoker.txt) 0.2 KB
 - **stitchkit/tools/connections**: [llms/tools-connections.txt](llms/tools-connections.txt) 3.1 KB
-- **stitchkit/cli**: [llms/cli.txt](llms/cli.txt) 41.3 KB → [llms/cli.2.txt](llms/cli.2.txt) 8.1 KB
+- **stitchkit/cli**: [llms/cli.txt](llms/cli.txt) 42.3 KB → [llms/cli.2.txt](llms/cli.2.txt) 8.1 KB
 - **stitchkit/remote**: [llms/remote.txt](llms/remote.txt) 1.0 KB
 - **stitchkit/contract**: [llms/contract.txt](llms/contract.txt) 31.9 KB
 - **stitchkit/primitives**: [llms/primitives.txt](llms/primitives.txt) 9.3 KB
 - **stitchkit/server**: [llms/server.txt](llms/server.txt) 45.3 KB → [llms/server.2.txt](llms/server.2.txt) 14.6 KB → [llms/server.3.txt](llms/server.3.txt) 42.7 KB → [llms/server.4.txt](llms/server.4.txt) 37.5 KB → [llms/server.5.txt](llms/server.5.txt) 21.8 KB
 - **stitchkit/observability**: [llms/observability.txt](llms/observability.txt) 43.4 KB
-- **stitchkit/agent-runtime**: [llms/agent-runtime.txt](llms/agent-runtime.txt) 46.6 KB → [llms/agent-runtime.2.txt](llms/agent-runtime.2.txt) 29.8 KB → [llms/agent-runtime.3.txt](llms/agent-runtime.3.txt) 31.8 KB
+- **stitchkit/agent-runtime**: [llms/agent-runtime.txt](llms/agent-runtime.txt) 36.4 KB → [llms/agent-runtime.2.txt](llms/agent-runtime.2.txt) 41.3 KB → [llms/agent-runtime.3.txt](llms/agent-runtime.3.txt) 32.0 KB
 - **stitchkit/agent-runtime/testing**: [llms/agent-runtime-testing.txt](llms/agent-runtime-testing.txt) 2.2 KB
 - **stitchkit/agent-runtime/harness**: [llms/agent-runtime-harness.txt](llms/agent-runtime-harness.txt) 4.1 KB
 - **stitchkit/agent-runtime/coding-tools**: [llms/agent-runtime-coding-tools.txt](llms/agent-runtime-coding-tools.txt) 4.9 KB
@@ -52,9 +52,9 @@ Load the slice for each entrypoint your code imports — `import … from 'stitc
 
 ## Upgrading slices
 - **Upgrading — how to move across versions**: [llms/upgrading.txt](llms/upgrading.txt) 10.3 KB
-- **Upgrading 0.70.0 → 0.96.0**: [llms/upgrading-0.70.0-0.96.0.txt](llms/upgrading-0.70.0-0.96.0.txt) 46.3 KB
-- **Upgrading 0.57.0 → 0.69.0**: [llms/upgrading-0.57.0-0.69.0.txt](llms/upgrading-0.57.0-0.69.0.txt) 44.4 KB
-- **Upgrading 0.37.0 → 0.56.0**: [llms/upgrading-0.37.0-0.56.0.txt](llms/upgrading-0.37.0-0.56.0.txt) 36.9 KB
+- **Upgrading 0.72.0 → 0.98.0**: [llms/upgrading-0.72.0-0.98.0.txt](llms/upgrading-0.72.0-0.98.0.txt) 44.8 KB
+- **Upgrading 0.59.0 → 0.71.0**: [llms/upgrading-0.59.0-0.71.0.txt](llms/upgrading-0.59.0-0.71.0.txt) 45.6 KB
+- **Upgrading 0.37.0 → 0.58.0**: [llms/upgrading-0.37.0-0.58.0.txt](llms/upgrading-0.37.0-0.58.0.txt) 40.0 KB
 
 ## Guide (web)
 - [Getting started](https://github.com/max-listov/stitchkit/blob/master/docs/guide/getting-started.md): install, entrypoints, and a first contract → server → client app

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stitchkit",
-  "version": "0.96.1",
+  "version": "0.98.0",
   "description": "Contract-first backend framework — one defineContract() into an HTTP API, MCP tools, AI-agent tools and a typed client. Bun and Node.",
   "keywords": [
     "bun",