@typeroll/mcp-server 0.45.40 → 0.45.42

package/AGENTS.md

@@ -315,7 +315,7 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
   everything you write through `?version=<branch-id>` lives on the
   branch until you `merge_branch` it back to main. Branches default
   `robots_blocked: true` so a half-finished redesign can't be indexed,
-  and deploys land at a stable `{branch}.{project}.pages.dev` URL. That
+  and deploys land at a stable address (`deploy_url` on the version). That
   branch deploy renders the site's full inherited brand (settings, fonts,
   favicon, header/footer — everything not overridden on the branch), so
   it's a faithful preview of what merging to main will look like, not just
@@ -404,7 +404,7 @@ maps to one HTTP endpoint; the actual logic runs in the customer's portal
   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
+- **Deploys / the branch `deploy_url` are the STATIC BUILD**, refreshed
   only by `trigger_deploy`. Reach for them when you want the real compiled
   output: publishing, a stakeholder link to the built site, or a faithful
   pre-merge check. The branch alias is permanent across re-deploys; the
@@ -592,22 +592,21 @@ Use `set_page_mode` — it snapshots a revision before flipping, so the
 previous state is restorable:
 
 ```
-# Convert an HTML-mode page to blocks with auto-heuristic conversion:
-set_page_mode page_id=about to=blocks convert=true
-
-# Or just switch the mode without converting (empty blocks):
+# Switch the mode without converting the HTML body:
 set_page_mode page_id=about to=blocks
 
 # Switch back to HTML (drops the block tree; revision retains it):
 set_page_mode page_id=about to=html
 ```
 
-The heuristic converter recognises `<h1-4>` → heading, `<img>` → image,
-`<a.btn>` → button, `grid-cols-2` → two-column, `<section>` / hero divs
-→ section. Anything it can't classify becomes a `core/prose` block,
-which preserves the raw HTML losslessly. Run with `convert_page_to_blocks
-dry_run=true` first if you want to inspect the proposal before
-committing.
+`convert_page_to_blocks` previews a heuristic conversion and lists
+`unconverted` text, classes, and markup. It does not write, and
+`set_page_mode` does not apply that preview. A person accepts the
+preview in the page editor. The heuristic recognises `<h1-4>` →
+heading, `<img>` → image, `<a.btn>` → button, `grid-cols-2` →
+two-column, `<section>` / hero divs → section. Link-wrapped card text
+and author classes are reported as unconverted rather than discarded
+silently.
 
 ### "Build a directory or migrate a content family"
 
@@ -985,7 +984,9 @@ design as perfect/approved off a glance or a partial pass.
 
 Preview shows DB state (drafts included). Live (`get_site → urls.production`)
 shows the most recent deploy. Branch deploys live at
-`get_version → deploy_url` (`{branch}.{project}.pages.dev`).
+`read_version → deploy_url`. The publishing setup decides that host (under a
+Hosting Group, a `v-…` host under the group's site address base); never
+construct it or guess a `pages.dev` alias.
 
 ## Branches
 
@@ -1001,7 +1002,7 @@ the live site until you `merge_branch`.
 
 Branches default `robots_blocked: true`. While iterating, preview the branch
 with a reused `get_preview_link` (DB-live, no build). Deploys to a branch land
-at a stable URL (`{branch}.{project}.pages.dev`) — that's the compiled static
+at a stable URL (`deploy_url` on the version) — that's the compiled static
 build, for sharing the finished result / stakeholder review, not per-edit
 preview.
 

package/README.md

@@ -226,8 +226,8 @@ the full reference + concrete operation recipes.
   `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`.
+- **Branches** — create, read, delete, merge. A deployed branch gets its own
+  stable address, reported as `deploy_url` by `list_versions` / `read_version`.
 - **Deploy** — trigger (with `dry_run` to build without publishing), list, get
   status. A finished job reports `cost`: what the build consumed in server
   time, broken down per phase. Estimates from a rate card, not billing records.
@@ -240,6 +240,9 @@ the full reference + concrete operation recipes.
   on the write call; inspect/discard with `read_working_copy` /
   `discard_working_copy`. Status changes and structural operations apply
   immediately.
+- **History** — `list_page_revisions`, `read_page_revision` and
+  `restore_page_revision` (to a draft, or saved with `save: true`) undo page
+  changes from earlier saves.
 
 ## Direct REST API access