@cyanheads/mcp-ts-core 0.6.3 → 0.6.6

package/skills/polish-docs-meta/SKILL.md

@@ -4,7 +4,7 @@ description: >
   Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
 metadata:
   author: cyanheads
-  version: "1.6"
+  version: "1.7"
   audience: external
   type: workflow
 ---
@@ -129,13 +129,13 @@ Two patterns are supported — pick one and stay consistent.
 
 Both are acceptable. The template scaffolds the directory-based structure by default; collapse to monolithic only if the rollup tooling is pure ceremony for this project.
 
-**Directory-based** — per-version files live at `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`), and `CHANGELOG.md` is a rollup regenerated by `bun run changelog:build`. Devcheck's `Changelog Sync` step enforces drift protection. `changelog/unreleased.md` is a **pristine format reference** — never edited, never moved, never renamed. Read it to remember the frontmatter + section layout when scaffolding a new per-version file.
+**Directory-based** — per-version files live at `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`), and `CHANGELOG.md` is a rollup regenerated by `bun run changelog:build`. Devcheck's `Changelog Sync` step enforces drift protection. `changelog/template.md` is a **pristine format reference** — never edited, never moved, never renamed. Read it to remember the frontmatter + section layout when scaffolding a new per-version file.
 
 If the structure doesn't exist yet:
 
 1. Make the `changelog/` directory
-2. Create `changelog/unreleased.md` once from the template (frontmatter stub + H1 `# Unreleased` + empty Added/Changed/Fixed sections) — this file is a format reference only and stays as-is after creation
-3. If the server already has a shipped version (e.g. 0.1.0), create the series directory and initial entry: `changelog/0.1.x/0.1.0.md` with H1 `# 0.1.0 — YYYY-MM-DD`, concrete version and date — do **not** rename or move `unreleased.md` to create the version file; author the per-version file directly
+2. Create `changelog/template.md` once from the template (frontmatter stub + H1 `# <version> — YYYY-MM-DD` placeholder + empty Added/Changed/Fixed sections) — this file is a format reference only and stays as-is after creation
+3. If the server already has a shipped version (e.g. 0.1.0), create the series directory and initial entry: `changelog/0.1.x/0.1.0.md` with H1 `# 0.1.0 — YYYY-MM-DD`, concrete version and date — do **not** rename or move `template.md` to create the version file; author the per-version file directly
 4. Run `bun run changelog:build` to generate `CHANGELOG.md`
 
 Per-version file format:
@@ -157,7 +157,7 @@ Optional narrative intro (1-3 sentences).
 
 **Frontmatter:** `summary` is required (powers the CHANGELOG.md index), `breaking` is optional and defaults to `false` (set `true` for releases requiring consumer code changes).
 
-Never hand-edit `CHANGELOG.md` when using this pattern — it's a build artifact. Never edit `changelog/unreleased.md` — it's the format reference. Never use `[Unreleased]` as a version header in a released file.
+Never hand-edit `CHANGELOG.md` when using this pattern — it's a build artifact. Never edit `changelog/template.md` — it's the format reference. Never use `[Unreleased]` as a version header in a released file.
 
 **Monolithic** — maintain `CHANGELOG.md` directly in [Keep a Changelog](https://keepachangelog.com/) format. To collapse from the template default: delete the `changelog/` directory, remove `changelog:build` and `changelog:check` from `package.json` scripts (and from `devcheck.config.json` if referenced), and drop `"changelog/"` from the `files` array. The `release` skill's directory-specific steps then don't apply — just edit `CHANGELOG.md` and bump version at release time.
 

package/skills/polish-docs-meta/references/readme.md

@@ -101,9 +101,9 @@ Seven tools for working with Acme data:
 
 | Tool Name | Description |
 |:----------|:------------|
-| `search_projects` | Search projects by name, status, or team. |
-| `create_task` | Create a new task in a project. |
-| `get_task` | Fetch one or more tasks by ID, with full or summary data. |
+| `acme_search_projects` | Search projects by name, status, or team. |
+| `acme_create_task` | Create a new task in a project. |
+| `acme_get_task` | Fetch one or more tasks by ID, with full or summary data. |
 ```
 
 **Per-tool subsections:**
@@ -115,7 +115,7 @@ Below the table, add a `### tool_name` subsection for each tool that has meaning
 - Separate subsections with `---` horizontal rules
 
 ```markdown
-### `search_projects`
+### `acme_search_projects`
 
 Search for projects using free-text queries and filters.
 
@@ -124,11 +124,11 @@ Search for projects using free-text queries and filters.
 - Pagination (up to 100 per page) and sorting
 - Field selection to limit response size
 
-[View detailed examples](./examples/search_projects.md)
+[View detailed examples](./examples/acme_search_projects.md)
 
 ---
 
-### `get_task`
+### `acme_get_task`
 
 Fetch one or more tasks by ID, with full data or concise summaries.
 
@@ -137,7 +137,7 @@ Fetch one or more tasks by ID, with full data or concise summaries.
 - Partial success reporting when some tasks in a batch fail
 ```
 
-Skip the per-tool subsection for simple tools where the table description says everything (e.g., a `get_field_values` lookup tool).
+Skip the per-tool subsection for simple tools where the table description says everything (e.g., an `acme_get_field_values` lookup tool).
 
 ### Resources and Prompts (combined)
 

package/skills/release/SKILL.md

@@ -36,12 +36,12 @@ Fix any mismatches. A grep for the **old** version is the fastest way to find st
 
 ### 3. Finalize the Per-Version Changelog File
 
-The changelog is directory-based, grouped by minor series using the `.x` semver-wildcard convention: per-version files live at `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.5.x/0.5.4.md`), and `CHANGELOG.md` is an auto-generated rollup (`bun run changelog:build`). `changelog/unreleased.md` is a **pristine format reference** — never edited, never moved, never renamed. At release time, you're authoring (or finalizing) the per-version file for the version being shipped.
+The changelog is directory-based, grouped by minor series using the `.x` semver-wildcard convention: per-version files live at `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.5.x/0.5.4.md`), and `CHANGELOG.md` is an auto-generated rollup (`bun run changelog:build`). `changelog/template.md` is a **pristine format reference** — never edited, never moved, never renamed. At release time, you're authoring (or finalizing) the per-version file for the version being shipped.
 
 Create or finalize `changelog/<series>/<version>.md`:
 
 1. Determine the series: `0.5.5` → `0.5.x/`. Create the directory if it doesn't exist: `mkdir -p changelog/<series>`
-2. If the file doesn't exist yet, scaffold it by copying the structure of `changelog/unreleased.md` into the new path. Do **not** `git mv` or otherwise rename `unreleased.md` itself — it stays where it is.
+2. If the file doesn't exist yet, scaffold it by copying the structure of `changelog/template.md` into the new path. Do **not** `git mv` or otherwise rename `template.md` itself — it stays where it is.
 3. Set the H1: `# <version> — <date>` (em-dash, ISO date)
 4. **Fill in the frontmatter** at the top of the file:
    - `summary:` — one-line headline, ≤250 chars, no markdown. Write it like a GitHub Release title. Required.
@@ -53,7 +53,7 @@ Create or finalize `changelog/<series>/<version>.md`:
    - **Issue/PR references use full URLs**, not bare `#NN`. GitHub's auto-link only renders inside its own UI; these files are read from `node_modules` too, where bare `#NN` is dead text. Use `[#38](https://github.com/<owner>/<repo>/issues/38)` (or `/pull/NN` for PRs). Only link numbers verified via `gh issue view NN` / `gh pr view NN` — never speculate on future numbers, since GitHub will happily resolve `#42` to whatever unrelated item already owns 42 and pull its title into timeline previews.
 6. Regenerate the rollup: `bun run changelog:build` — warnings about missing summaries are expected during the legacy-file backfill period but should not include this release
 
-Never hand-edit `CHANGELOG.md` — it's a build artifact. Devcheck's `Changelog Sync` step will fail if it drifts. Never edit `changelog/unreleased.md` — it's the format reference, not a worksheet.
+Never hand-edit `CHANGELOG.md` — it's a build artifact. Devcheck's `Changelog Sync` step will fail if it drifts. Never edit `changelog/template.md` — it's the format reference, not a worksheet.
 
 ### 4. Verify README.md
 
@@ -130,7 +130,7 @@ mcp-publisher publish
 
 - [ ] Version consistent across all files (package.json, server.json ×3, CLAUDE.md, README.md, templates)
 - [ ] No stale old-version references found in repo
-- [ ] `changelog/<major.minor>.x/<version>.md` created/finalized with concrete version, date, and frontmatter; `CHANGELOG.md` regenerated via `bun run changelog:build`; `changelog/unreleased.md` untouched
+- [ ] `changelog/<major.minor>.x/<version>.md` created/finalized with concrete version, date, and frontmatter; `CHANGELOG.md` regenerated via `bun run changelog:build`; `changelog/template.md` untouched
 - [ ] README.md current — feature counts, badges, descriptions, examples
 - [ ] Modified skill versions bumped in YAML frontmatter
 - [ ] `docs/tree.md` current (if structure changed)

package/templates/.env.example

@@ -3,6 +3,7 @@
 # MCP_HTTP_PORT=3010                # HTTP port (default: 3010)
 # MCP_HTTP_HOST=localhost           # HTTP host (default: localhost)
 # MCP_HTTP_ENDPOINT_PATH=/mcp      # HTTP endpoint path (default: /mcp)
+# MCP_PUBLIC_URL=                  # Public origin behind a TLS-terminating proxy (e.g. https://mcp.example.com)
 
 # ── Auth ──────────────────────────────────────────────────────────────
 # MCP_AUTH_MODE=none                # none | jwt | oauth (default: none)

package/templates/AGENTS.md

@@ -279,7 +279,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
 
 ## Changelog
 
-Directory-based, grouped by minor series using the `.x` semver-wildcard convention. Source of truth is `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`) — one file per released version, shipped in the npm package. At release time, author the per-version file with a concrete version and date, then run `npm run changelog:build` to regenerate the rollup. `changelog/unreleased.md` is a **pristine format reference** — never edited, never renamed, never moved. Read it to remember the frontmatter + section layout when scaffolding a new per-version file. `CHANGELOG.md` is a **navigation index** (header + link + one-line summary per version), regenerated by `npm run changelog:build`. Devcheck hard-fails on drift. Never hand-edit `CHANGELOG.md`.
+Directory-based, grouped by minor series using the `.x` semver-wildcard convention. Source of truth is `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`) — one file per released version, shipped in the npm package. At release time, author the per-version file with a concrete version and date, then run `npm run changelog:build` to regenerate the rollup. `changelog/template.md` is a **pristine format reference** — never edited, never renamed, never moved. Read it to remember the frontmatter + section layout when scaffolding a new per-version file. `CHANGELOG.md` is a **navigation index** (header + link + one-line summary per version), regenerated by `npm run changelog:build`. Devcheck hard-fails on drift. Never hand-edit `CHANGELOG.md`.
 
 Each per-version file opens with YAML frontmatter:
 

package/templates/CLAUDE.md

@@ -279,7 +279,7 @@ When you complete a skill's checklist, check the boxes and add a completion time
 
 ## Changelog
 
-Directory-based, grouped by minor series using the `.x` semver-wildcard convention. Source of truth is `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`) — one file per released version, shipped in the npm package. At release time, author the per-version file with a concrete version and date, then run `npm run changelog:build` to regenerate the rollup. `changelog/unreleased.md` is a **pristine format reference** — never edited, never renamed, never moved. Read it to remember the frontmatter + section layout when scaffolding a new per-version file. `CHANGELOG.md` is a **navigation index** (header + link + one-line summary per version), regenerated by `npm run changelog:build`. Devcheck hard-fails on drift. Never hand-edit `CHANGELOG.md`.
+Directory-based, grouped by minor series using the `.x` semver-wildcard convention. Source of truth is `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.1.x/0.1.0.md`) — one file per released version, shipped in the npm package. At release time, author the per-version file with a concrete version and date, then run `npm run changelog:build` to regenerate the rollup. `changelog/template.md` is a **pristine format reference** — never edited, never renamed, never moved. Read it to remember the frontmatter + section layout when scaffolding a new per-version file. `CHANGELOG.md` is a **navigation index** (header + link + one-line summary per version), regenerated by `npm run changelog:build`. Devcheck hard-fails on drift. Never hand-edit `CHANGELOG.md`.
 
 Each per-version file opens with YAML frontmatter:
 

package/templates/changelog/{unreleased.md → template.md}

@@ -16,7 +16,7 @@ summary: ""
 breaking: false
 ---
 
-# Unreleased
+# <version> — YYYY-MM-DD
 
 <!--
   FORMAT REFERENCE — do not edit this file. It exists so the per-version file