@typeroll/mcp-server 0.15.4 → 0.16.1

package/AGENTS.md

@@ -103,9 +103,20 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
     media URL (run `generate_image_variants` first) and optionally set
     `radius`. Note: the in-portal preview shows the plain `<img>` — the
     `<picture>` upgrade appears on the deployed site.
-  - **`core/icon` / `core/icon_box` icons do not render yet** — they
-    emit `data-icon` placeholders awaiting an icon pipeline. Prefer
-    numbered markers, emoji, or CSS shapes until that ships.
+  - **Icons render inline SVG** (since template_capabilities_version
+    0.16.0). Every `type: 'icon'` schema field — on `core/icon`,
+    `core/icon_box`, `core/step_card`, and custom block types — renders
+    a stroke-based inline SVG when the value is a name from
+    `get_site_capabilities → core_icon_names` (a curated Lucide subset:
+    `check`, `star`, `shield-check`, `mail`, `arrow-right`, `zap`,
+    `truck`, `chart-line`, …). Any other value (emoji, plain text) is
+    rendered as escaped text, so emoji stand-ins keep working. Icons
+    size with `font-size` (the SVG is 1em) and paint with
+    `currentColor`. Custom block templates opt in by placing the derived
+    raw token `{{{<field>_svg}}}` where the icon should appear. On
+    pre-0.16.0 portals icons don't render — use emoji or CSS markers.
+    `core/tabs` label icons are the remaining gap (tab strip is built
+    client-side).
   - **`core/section` is natively full-bleed on block pages** (since
     template_capabilities_version 0.14.0): the section's background runs
     edge-to-edge and meets the header with zero gap; content inside is
@@ -424,6 +435,16 @@ update_page page_id=about patch={ slug: "om-oss" }
 
 The 301 fires automatically — you don't have to remember.
 
+Redirect hygiene is automatic in both directions (since 0.16.1):
+
+- When a **live** (published/unlisted) page takes over a URL — via slug/path
+  change, publish, or create — any redirect FROM that URL is retired; the
+  response lists them under `retired_redirects`. A real page always beats a
+  redirect (on Cloudflare Pages a redirect would otherwise shadow the page).
+- When a page is **deleted**, auto-generated redirects pointing TO its URL
+  are removed (reported as `removed_redirects`). Manually created redirects
+  are kept — delete them yourself via `delete_redirect` if they're obsolete.
+
 ### "Change the site's fallback URL (slug)"
 
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.15.4",
+  "version": "0.16.1",
   "description": "Model Context Protocol server for the Typeroll public API. Use with Claude Code or any MCP-compatible client to manage a Typeroll site.",
   "license": "MIT",
   "repository": {

package/skills/tr-brand.md

@@ -172,9 +172,23 @@ Use **either** a background-color shift **or** a horizontal divider line at a se
 
 ### Sections are full-bleed; content is container-width
 
-The section element ALWAYS spans the full viewport (its bg, border, decorative line). Content inside is constrained by `.container` / `.container.narrow`.
-
-The renderer wraps `html_content` in `<main class="page-content">` with `max-width: var(--container-medium)` — so a section's bg-color rule alone gives a "1080px-wide stripe in the middle of the page", which is wrong. Every section that has a bg/border must apply the negative-margin escape:
+The section element ALWAYS spans the full viewport (its bg, border, decorative line). Content inside is constrained to a readable column.
+
+**Block-mode pages (the default):** this is native. Top-level
+`core/section` blocks are full-bleed out of the box — set `background`
+on the section and it runs edge-to-edge, meeting the header with zero
+gap; the section's `width` field (narrow/normal/wide/full) constrains
+the content column. **NEVER add 100vw negative-margin hacks on block
+pages** — they double-bleed and break. Anchor ids / custom classes on
+sections are safe from template_capabilities_version ≥ 0.15.3 (older
+versions wrapped the section in a div and silently killed full-bleed —
+there, put the anchor on a block inside the section).
+
+**HTML-mode pages (`html_content`) only:** the renderer wraps the body
+in `<main class="page-content">` with `max-width: var(--container-medium)`
+— a section's bg-color rule alone gives a "1080px-wide stripe in the
+middle of the page", which is wrong. Every section that has a bg/border
+must apply the negative-margin escape:
 
 ```css
 .my-page .section {
@@ -266,13 +280,20 @@ Open in browser. Check:
 - **Dark themes need dark surface too.** Setting `background: #0f0f0f`
   but leaving `surface: #f8fafc` (white) breaks every card/input. Always
   update all 7 tokens as a set.
-- **The renderer's `.page-content` layout shell.** The renderer wraps
-  `html_content` in `<main class="page-content">` with constrained
-  `max-width` and default typography. The typography defaults now sit
-  inside `:where()` so they have specificity 0 — a customer's class
-  rules trivially win. The layout shell (width + padding) is still at
-  normal specificity by design: it's what gives a brand-new page
+- **The renderer's `.page-content` layout shell (html-mode only).** The
+  renderer wraps `html_content` in `<main class="page-content">` with
+  constrained `max-width` and default typography. The typography defaults
+  now sit inside `:where()` so they have specificity 0 — a customer's
+  class rules trivially win. The layout shell (width + padding) is still
+  at normal specificity by design: it's what gives a brand-new page
   reasonable margins out of the box. If a section needs to escape the
   shell (full-bleed bg, full-width hero), apply the negative-margin
   pattern shown in Step 4b. Don't fight the shell with `overflow-x`
-  hacks.
+  hacks. Block-mode pages don't have the width problem — sections are
+  natively full-bleed there.
+- **The shell's global `img` rule leaks into custom figures.** Both modes
+  apply `:where(.page-content) img { margin: …; border-radius: … }`. A
+  hand-built image card (rounded clipping wrapper around an `<img>`) gets
+  phantom margins inside the wrapper — visible as white bands above and
+  below the photo. Zero it explicitly in your figure CSS:
+  `.my-figure img { margin: 0; border-radius: 0 }`.

package/skills/tr-new-site.md

@@ -172,10 +172,19 @@ passing the whole tree inline (`block={ type: 'core/columns', slots:
 slot_index=0|1`. Requires template_capabilities_version ≥ 0.15.2 — on
 older sites use `core/grid` (children flow into columns) instead.
 
+Icons (template_capabilities_version ≥ 0.16.0): `type: 'icon'` fields on
+`core/icon`, `core/icon_box`, and `core/step_card` render inline SVG when
+the value is a name from `get_site_capabilities → core_icon_names` (a
+curated Lucide subset — `check`, `star`, `shield-check`, `mail`,
+`arrow-right`, `truck`, `chart-line`, …). Any other value (emoji, plain
+text) renders as text, so emoji stand-ins keep working. Icons inherit
+size from font-size and color from `currentColor`/the block's color
+field. On older sites icons don't render — use emoji or CSS markers.
+
 Known limitations (honest list — don't fight them):
 
-- **`core/icon` / `core/icon_box` icons don't render yet** (pending icon
-  pipeline). Use `step_card` numbers, emoji, or CSS markers.
+- **`core/tabs` label icons don't render** (the tab strip is built
+  client-side without the icon pipeline). Text labels only.
 
 Theming: block primitives render neutral. Brand color/typography comes
 from settings (step 2). For page-specific polish (e.g. a colored card