| summary | Bump @cyanheads/mcp-ts-core 0.6.17 → 0.7.0, resync 5 skills and 2 framework scripts, adopt expanded CLAUDE.md/AGENTS.md checklist and Changelog/Agent-skill-dir callouts |
|---|---|
| breaking | false |
Maintenance release — no functional code changes in src/. Framework bump is transparent (this server doesn't use any of the reshaped surfaces), and the rest is documentation + skill/script bookkeeping so the next maintenance run starts from a clean baseline.
- Framework bump:
@cyanheads/mcp-ts-core0.6.17 → 0.7.0. Non-breaking per upstream. New features not exercised here: flat ZodError messages with structuredissuesonerror.data(no ZodError surfaces insrc/), locale-awareformat-paritysentinel matching, devcheck changelog-guard hardening. - Skills resynced from framework.
api-linter1.0 → 1.1 (primitive-array recursion note),maintenance1.4 → 1.5 (template review default-adopts framework-authored updates; Step 6 splits framework-vs-third-party adoption defaults),release-and-publish2.0 → 2.1 (transient-failure retries + docker prune on buildx retry),report-issue-frameworkandreport-issue-local1.2 → 1.3 (primary/secondary label split,--assignee "@me"CLI guidance). - Scripts resynced from framework.
scripts/devcheck.tsandscripts/build-changelog.tspicked up the single-file-CHANGELOG guard from cyanheads/mcp-ts-core#51. No effect on this project (we use the directory-based changelog) — resynced to keep scaffold scripts aligned with the package. CLAUDE.md/AGENTS.mdadopted framework template improvements. Expanded Checklist with form-client guard + three external-API hygiene items (directly applicable — this server wraps ClinicalTrials.gov), updatedformat()client-surface wording (Claude Code readsstructuredContent, Claude Desktop readscontent[]— both must carry the same data), added "Agent skill directory" callout documenting the.claude/skills/sync, and added a "Changelog" section documenting the directory-based convention this project already uses.
CLAUDE.md/AGENTS.mdserver-config example now matches implementation. The example showed the staleServerConfigSchema.parse({ ...process.env.X })pattern;src/config/server-config.tshas been usingparseEnvConfig(better env-var-named error messages) for some time. Docs now reflect reality.