@typeroll/mcp-server 0.15.2 → 0.15.4

package/AGENTS.md

@@ -112,7 +112,11 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
     constrained by the section's own inner container (`width` field:
     narrow/normal/wide/full). Never use 100vw negative-margin hacks.
     Top-level blocks that are NOT sections still get a classic centered
-    container as fallback.
+    container as fallback. Anchor ids and custom classes via
+    `style_overrides` are safe on full-bleed sections since 0.15.3 —
+    they merge into the `<section>` element itself. On 0.14.x–0.15.2
+    they wrapped the section in a `<div>`, which silently disabled
+    full-bleed for that section.
   - **`core/html`** is the raw-HTML escape hatch for block-mode pages —
     one `html` field rendered verbatim (then sanitized like HTML-mode
     content). Use it for the genuinely unique thing no block covers: a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.15.2",
+  "version": "0.15.4",
   "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-new-site.md

@@ -110,7 +110,11 @@ create_page title="Start" slug="" status="draft" content_mode="blocks" blocks=[.
 A proven landing-page skeleton (every top-level block is a `core/section`
 — sections are **natively full-bleed**: the background runs edge-to-edge,
 content is constrained by the section's own inner container via the
-`width` field. NEVER use 100vw negative-margin hacks):
+`width` field. NEVER use 100vw negative-margin hacks. Anchor ids and
+custom classes via `style_overrides` are safe on sections from
+template_capabilities_version ≥ 0.15.3; on 0.14.x–0.15.2 they wrap the
+section in a div and silently break full-bleed — there, put the anchor
+on a block *inside* the section instead):
 
 ```json
 [