@typeroll/mcp-server 0.42.1 → 0.43.0

package/AGENTS.md

@@ -73,7 +73,9 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
   products, restaurants for a directory site, etc.). Each has a schema
   (`fields[]`) and optional **per-item routing** via `route_template`
   (e.g. `/restaurants/{slug}`). When set, every published item gets its
-  own static URL rendered through `item_template_html`. Set
+  own static URL rendered through `item_template_blocks` (preferred) or
+  `item_template_html`. Native `article` and `checklist` presets are available
+  through `template_kind`. Set
   `route_template=""` to opt out and keep the collection listing-only.
 
 - **Settings.** Site name, tagline, logo, favicon, colors, fonts,
@@ -367,6 +369,9 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
   Discard; `read_working_copy` shows the raw unsaved diff when you need to
   know whose edits are in it. Working copies are per-doc scratch; for
   multi-page efforts branch instead (`create_branch`).
+  `content_mode` is not a writable `update_page` or batch patch field. Save
+  the target HTML/block tree first, then call `set_page_mode`; the API rejects
+  direct PATCH attempts and points at the mode endpoint.
   **Before `trigger_deploy`: commit.** Deploys build saved content only —
   an uncommitted draft silently stays behind.
 - **Deploys / `{branch}.{project}.pages.dev` are the STATIC BUILD**, refreshed
@@ -582,7 +587,7 @@ create_collection
   label_singular="Restaurant" label_plural="Restaurants"
   fields=[ ...title, slug, address, phone, cuisine, body... ]
   route_template="/restaurants/{slug}"
-  item_template_html="<article><h1>{{title}}</h1>… {{{body}}}</article>"
+  template_kind="article"
 
 # For each row in your source data:
 create_collection_item collection="restaurants" fields={…} status="published"
@@ -596,6 +601,15 @@ list_collection_items collection="restaurants" limit=200
 update_page page_id=restaurants patch={ html_content: "<hand-written listing>" }
 ```
 
+For articles and checklists, prefer the native `article` / `checklist`
+`template_kind` presets or an explicit `item_template_blocks` tree. Exact
+bindings such as `core/button.href = "{{item.pdf_url}}"` are supported on
+typed text/URL/image fields. `template/item_body.field`,
+`template/page_date.field`, and `core/table_of_contents.source_field` select
+the named item field. Breadcrumbs and outlines exist in initial HTML. Use
+explicit neighbor fields on `template/item_navigation` only when imported
+navigation must differ from collection sort order.
+
 ### "Migrate a content type (e.g. WP custom post type)"
 
 ```
@@ -733,6 +747,13 @@ something is quietly wrong:
 redone. The in-portal migration workflow enforces the same gate as its first
 step (`skip_preflight: true` overrides it, and logs that it did).
 
+Before converting a content family, pass its proposed `compositions` too.
+The read-only review lists required fields/block types/capabilities and marks
+generic custom blocks, raw HTML, or corrective instance CSS as
+`waiting_for_native_support`. Do not build around that result. Continue
+independent content/SEO work and wait for the required Core release, then
+verify the fixture in both preview and a fresh hosted static build.
+
 ### "Don't lose URLs in a migration"
 
 Two different questions, and you need both answers:
@@ -744,7 +765,9 @@ verify_migration_urls                      # what the SERVER actually answers
 
 `list_migration_urls` classifies every inventory URL against the site's
 current pages + redirects. It's recomputed on read, so creating a redirect
-flips the entry on your next call — no bookkeeping of your own.
+flips the entry on your next call — no bookkeeping of your own. Slash-equivalent
+source URLs share one inventory row, but `observed_paths` preserves the exact
+spellings that were discovered.
 
 `verify_migration_urls` requests each URL against the deployed site (its
 fallback subdomain by default, because the real domain still points at the
@@ -752,8 +775,20 @@ old host pre-cutover) and reports `ok` / `ok_redirect` / `missing` /
 `broken_redirect` / `error`. This is the one that catches a redirect
 pointing at an unpublished page, a typo'd `path`, and redirect loops — all
 of which read as "handled" in the coverage report and as a 404 to Googlebot.
+Every distinct `observed_paths` value is requested, so a slash variant can fail
+even when its normalized inventory row is green; `summary.checked` counts those
+requests rather than normalized rows.
 **Deploy first**: it tests saved, deployed content, not your drafts.
 
+Imports created before plain-text normalization may still contain WordPress
+entities or markup in titles and SEO text. Use
+`repair_migration_plain_text` for those records. It accepts only `title`,
+`seo_title`, `seo_description`, and `excerpt`; it cannot touch rich content,
+slugs, paths, or URLs. The tool defaults to a dry run with exact field diffs.
+Show the full diff/conflict result to the user and obtain approval before
+calling it with `dry_run=false`. Existing working copies are conflicts and are
+never overwritten or committed by the repair.
+
 Every unhandled URL gets exactly one of three outcomes — there is no fourth:
 
 - it moved → `create_redirect`
@@ -798,7 +833,10 @@ Constraints, all enforced at write time rather than discovered in production:
 Rules are emitted most-specific-first, so `/blogg/recept/*` and `/blogg/*`
 can coexist — the narrower one fires. `list_migration_urls` counts
 pattern-covered URLs as `redirected`, so the coverage report reflects what
-production will do.
+production will do. A build emits both slash spellings for redirect sources
+(except root and file/resource paths) and normalizes internal destinations to
+the site's trailing-slash policy. Changing this behavior requires a new build,
+not a migration of stored redirect records.
 
 ### "Link language versions together (hreflang)"
 
@@ -986,14 +1024,14 @@ preview.
 | **Pages — writes** | `create_page`, `update_page`, `replace_page`, `batch_update_pages`, `delete_page`, `clone_page` |
 | **Pages — blocks** | `get_page_blocks`, `add_block`, `update_block`, `move_block`, `remove_block`, `set_page_mode`, `convert_page_to_blocks` |
 | **Pages — meta** | `get_page_preview` |
-| **Global blocks (partials)** | `list_partials` (summary by default), `read_partial`, `create_free_block`, `update_partial`, `replace_partial`, `delete_partial`, `find_pages_using_block`, `list_blocks_with_usage` |
+| **Global blocks (partials)** | `list_partials` (summary by default), `read_partial`, `create_free_block`, `update_partial`, `replace_partial`, `set_partial_mode`, `delete_partial`, `find_pages_using_block`, `list_blocks_with_usage` |
 | **Block types** | `list_block_types`, `read_block_type`, `find_pages_using_block_type`, `export_block_types`, `import_block_types` |
 | **Collections** | `create_collection`, `update_collection_schema`, `delete_collection`, `list_collections`, `read_collection`, `list_collection_items` (richtext hidden by default), `read_collection_item`, `batch_read_collection_items`, `create_collection_item`, `update_collection_item`, `delete_collection_item`, `regenerate_collection_listing` |
 | **Media** | `list_media`, `read_media`, `create_upload_url`, `upload_media_from_url`, `upload_media_inline`, `update_media`, `delete_media`, `finalize_media`, `finalize_all_media`, `generate_image_variants`, `suggest_alt_text_context` |
 | **Redirects** | `list_redirects`, `create_redirect`, `delete_redirect`. `from_path` may be a PATTERN: a trailing `*` (with `:splat` in the target) or `:name` for one segment — one rule retires a whole family of dead URLs (`/category/*` → `/blogg/:splat`). Mid-path splats and query strings are refused, as is any rule that would hide a live page. |
-| **Migration inventory** | `get_migration_readiness` (preflight — CALL FIRST), `list_migration_urls`, `add_migration_urls`, `update_migration_url`, `update_migration_urls`, `delete_migration_url`, `import_sitemap`, `import_gsc_performance`, `verify_migration_urls`. Sitemap indexes are recursive. GSC supports direct Search Console access or CSV and aggregates fragment variants. Verification is compact by default. |
+| **Migration inventory** | `get_migration_readiness` (preflight — CALL FIRST), `list_migration_urls`, `add_migration_urls`, `update_migration_url`, `update_migration_urls`, `delete_migration_url`, `import_sitemap`, `import_gsc_performance`, `repair_migration_plain_text`, `verify_migration_urls`. Sitemap indexes are recursive. GSC supports direct Search Console access or CSV and aggregates fragment variants. Plain-text repair is allowlisted and dry-run-first. Verification is compact by default. |
 | **Forms** | `list_forms`, `read_form`, `create_form`, `update_form`, `delete_form`, `list_form_submissions`, `delete_form_submission` (removes one submission — e.g. cleaning up a test entry; `delete_form` with `delete_submissions` is the bulk path). **Steps (form/* block trees) are the ONLY stored model**: pass `steps` for funnels, or `fields` for simple forms — the server converts a flat field list to a single static step. Place with a `core/form` block on block-mode pages or `<x-form id="…" />` in HTML mode. Both expand server-side to the same complete signed shell and initial state. Email/webhook actions are admin-only in the portal and excluded from agent reads/writes. |
-| **Settings** | `update_site_settings` (whitelist) |
+| **Settings** | `update_site_settings` (whitelist, including shallow-merged native `cookie_consent`) |
 | **Core modules** | `list_apps`, `read_app`, `update_app` (legacy API name; admin; schema-driven config, masked secrets, redeploy when `affects_build` is true) |
 | **Extension installations** | `list_extension_installations`, `read_extension_installation`, `update_extension_installation_config` (admin; schema-driven config, masked secrets preserved, production deploy queued by default) |
 | **Analytics attribution** | `read_funnel_attribution`, `update_funnel_attribution` (specialized Analytics module tools; admin; redeploy after changes) |

package/README.md

@@ -145,18 +145,23 @@ the full reference + concrete operation recipes.
   template, or collection item-template), so one tool family edits
   every block container.
 - **Global blocks (partials)** — list (summary mode by default), read,
-  create free block, update, replace, delete, find-pages-using-block.
+  create free block, update, replace, delete, `set_partial_mode`,
+  find-pages-using-block. New header/footer work should use the native
+  `template/site_logo` + `core/navigation` recipe in `tr-header-footer`.
 - **Block types** — list, read, create, update, delete,
   find-pages-using-block-type, plus `.tcblocks` export/import. Custom
   client-side JS (`script`) is honoured only when the site has enabled
   "Allow AI to write block scripts" (a human-set portal setting) —
   otherwise it's stripped with a warning.
 - **Collections + items** — create/update/delete the collection schema
-  itself (incl. `route_template` for per-item URLs); list/read/batch-
+  itself (incl. `route_template` for per-item URLs and native `article` /
+  `checklist` template presets); list/read/batch-
   read/create/update/delete items. Existing-collection tools consistently
   use `collection` (the old `name` argument remains accepted as an alias).
   Collection repeaters support `group_by`, and item templates can place
-  `template/item_navigation` for deterministic previous/next links.
+  `template/item_navigation` for deterministic or explicitly field-bound
+  previous/next links. Typed context bindings, breadcrumbs, selected body
+  fields, and table-of-contents links render server-side.
 - **Media** — list, read, signed upload URLs, `upload_media_from_url`,
   `upload_media_batch_from_urls` (1–50 sources, max 25 MiB each, with
   partial-success results),
@@ -168,10 +173,12 @@ the full reference + concrete operation recipes.
   variant half of finalize, kept for surgical reruns),
   `suggest_alt_text_context` (returns a tuned prompt for your own
   vision model).
-- **Rendering controls** — `core/table_of_contents`, per-site
+- **Rendering controls** — semantic `core/navigation`, mapped
+  `core/post_card`, `core/table_of_contents`, per-site
   `trailing_slash`, exact `iframe_allowed_hosts`, `icon_192`, and per-page
   `append_seo_suffix=false`. The block editor supports labelled enums,
-  line-based lists, nested repeating arrays and an internal-page URL picker.
+  line-based lists, nested repeating arrays, responsive values in block
+  `data`, and an internal-page URL picker.
 - **Redirects** — list, create, delete. Plus automatic 301 on slug change.
 - **Forms** — list, read, create, update, delete, list submissions.
   Place forms with `core/form` blocks or an HTML-mode `<x-form id="…" />`
@@ -184,8 +191,8 @@ the full reference + concrete operation recipes.
   preserved. Use this for frontend config such as consent copy and policy
   links. It queues a production deploy by default; pass `deploy: false` only
   when batching changes and deploy once afterwards.
-- **Settings** — read + patch, including `scripts_head` /
-  `scripts_body_end` / `custom_css` (trusted because the caller holds an
+- **Settings** — read + patch, including shallow-merged `cookie_consent`,
+  `scripts_head` / `scripts_body_end` / `custom_css` (trusted because the caller holds an
   API key; the in-portal chat AI does NOT get these).
 - **Core modules** — list the legacy `apps` registry, read schema + masked
   state, and enable, configure, or disable any module with the same admin API key used for content
@@ -199,7 +206,9 @@ the full reference + concrete operation recipes.
   block data and schema-defined collection-item fields.
 - **Migration inventory** — bulk add/update decisions, recursive
   `import_sitemap`, direct or CSV-fallback `import_gsc_performance`, and compact
-  `verify_migration_urls` (successful rows omitted unless requested).
+  `verify_migration_urls` (successful rows omitted unless requested), plus
+  `repair_migration_plain_text` for dry-run-first cleanup of legacy WordPress
+  entities and markup in allowlisted plain-text fields.
 - **Branches** — create, read, delete, merge. Branch deploys get their
   own URL at `{branch}.{project}.pages.dev`.
 - **Deploy** — trigger (with `dry_run` to build without publishing), list, get