---
summary: "Framework 0.8.20 → 0.9.1: adopt server-level `instructions` on `createApp` (spec orientation text broadcast on `initialize`), summary cap 250 → 350 chars, `bun outdated` parser fix for markdown-style rows, skill resyncs including the new portability lint family in `api-linter`."
breaking: false
security: false
---

# 2.4.8 — 2026-05-16

Maintenance release. Framework catch-up across two minor versions, with the headline change being a new server-level `instructions` block sent on every `initialize` so spec-compliant clients can forward ClinicalTrials.gov-specific orientation to the model as session context.

## Added

- **Server-level `instructions` on `createApp`** ([mcp-ts-core#91](https://github.com/cyanheads/mcp-ts-core/issues/91)) — a single block of orientation text broadcast on every `initialize` response. Covers the NCT ID format, PascalCase field-leaf naming for `fields` / `advancedFilter` / `sort`, the typical `search → get_study_record → get_study_results` workflow, and pointers to the discovery tools (`clinicaltrials_get_field_definitions`, `clinicaltrials_get_field_values`). Replaces text that was previously duplicated across tool descriptions.

## Changed

- **`@cyanheads/mcp-ts-core` 0.8.20 → 0.9.1** — two framework releases rolled up:
  - 0.9.0 — `CreateAppOptions.instructions` and `WorkerHandlerOptions.instructions` ([#91](https://github.com/cyanheads/mcp-ts-core/issues/91)); Workers now boot under `nodejs_compat` ([#124](https://github.com/cyanheads/mcp-ts-core/issues/124)); new portability lint family ([#132](https://github.com/cyanheads/mcp-ts-core/issues/132)) — five rules walk emitted JSON Schema for cross-vendor traps (`format` allowlist, missing branch `type`, OpenAPI `discriminator`, `$defs`/`$ref`, dialect tag); definition linting moves to build-time only (faster cold starts, new lint rules are additive); RFC 8414 §3 path-suffixed well-known mount ([#95](https://github.com/cyanheads/mcp-ts-core/issues/95)); SSRF DNS validation now runs in Workers ([#70](https://github.com/cyanheads/mcp-ts-core/issues/70), [#120](https://github.com/cyanheads/mcp-ts-core/issues/120), [#126](https://github.com/cyanheads/mcp-ts-core/issues/126)) with broader IPv6 coverage; `FileSystemProvider` re-validates `tenantId` at the storage boundary ([#72](https://github.com/cyanheads/mcp-ts-core/issues/72)); rate-limit metric cardinality bounded ([#114](https://github.com/cyanheads/mcp-ts-core/issues/114)); changelog summary cap raised 250 → 350 chars ([#129](https://github.com/cyanheads/mcp-ts-core/issues/129)).
  - 0.9.1 — `Context.notifyPromptListChanged` / `notifyToolListChanged` notifiers; `tasks` capability advertisement gated on actual task-tool registration so strict-parsing MCP `2025-06-18` clients no longer fail on the unknown key; OTel `deployment.environment.name` migrated to the stable typed constant from `@opentelemetry/semantic-conventions` `^1.41`; `scripts/devcheck.ts` `bun outdated` parser fixed (markdown-style rows have an empty leading cell — now reads index `[1]` and strips the `(dev|peer|prod|optional)` workspace marker).
- **Summary cap 250 → 350 chars** — `scripts/build-changelog.ts` `SUMMARY_MAX_LENGTH`, `changelog/template.md`, and the `CLAUDE.md` / `AGENTS.md` changelog sections updated. 250 was forcing operator-relevant context out of recent summaries.
- **`scripts/devcheck.ts` `bun outdated` parser** — synced the index-`[1]` fix and workspace-marker strip from upstream so the outdated allowlist matches bare package names again.
- **Skills resynced from framework** — `add-tool` 2.8 → 2.9, `api-errors` 1.5 → 1.6, `api-linter` 1.2 → 1.3 (portability rule family + landing config rules + error contract rules now documented), `api-workers` 1.3 → 1.4 (`instructions` resolver form), `design-mcp-server` 2.10 → 2.11, `field-test` 2.3 → 2.4, `polish-docs-meta` 1.7 → 1.8, `tool-defs-analysis` 1.1 → 1.2.
- **`@cloudflare/workers-types` ^4.20260510.1 → ^4.20260516.1**, **`@types/bun` ^1.3.13 → ^1.3.14**, **`@types/node` ^25.6.2 → ^25.8.0**, **`@vitest/coverage-istanbul` ^4.1.5 → ^4.1.6**, **`fast-check` ^4.7.0 → ^4.8.0**, **`vite` ^8.0.11 → ^8.0.13**, **`vitest` ^4.1.5 → ^4.1.6** (devDeps).
