@typeroll/mcp-server 0.45.76 → 0.45.77

package/dist/init.js

@@ -48,7 +48,7 @@ export async function runInitCli(args) {
     try {
         const result = await runInit({ dir, update, recipes, client });
         console.log(JSON.stringify(result, null, 2));
-        console.log('Next: fill brief/, connect hosted MCP at https://app.typeroll.com/api/mcp?tools=compact, create/select your Site, record its IDs/Version in typeroll.json, then run typeroll doctor. Local MCP uses an injected TYPEROLL_API_KEY; no key is stored by init. See README.md.');
+        console.log('Next: read AGENTS.md. For guidance, start/resume workflows/interview.md; otherwise use workflows/new-site.md or workflows/migration.md. Record decisions in brief/, connect hosted MCP at https://app.typeroll.com/api/mcp?tools=compact, create/select your Site, record its IDs/Version in typeroll.json, then run typeroll doctor. Local MCP uses an injected TYPEROLL_API_KEY; no key is stored by init. See README.md.');
         return 0;
     }
     catch {

package/dist/version.js

@@ -8,4 +8,4 @@
 //
 // Keep it in lockstep with package.json: tests/version.test.ts asserts
 // VERSION === package.json.version, so a bump that forgets this line fails CI.
-export const VERSION = '0.45.76';
+export const VERSION = '0.45.77';

package/dist/workspace.js

@@ -3,6 +3,7 @@ import path from 'node:path';
 import { createHash } from 'node:crypto';
 import { z } from 'zod';
 import { VERSION } from './version.js';
+import { BUNDLED_WORKSPACE_TEMPLATES } from './bundled-content.js';
 import { ApiError, TyperollClient } from './client.js';
 export const workspaceSchema = z.object({
     schema_version: z.literal(1),
@@ -20,11 +21,21 @@ const hash = (value) => createHash('sha256').update(value).digest('hex');
 export const ignores = ['.typeroll/', '.env', '.env.*', '!.env.example', '.mcp.json', '.cursor/mcp.json', '.vscode/mcp.json', 'qa/reports/', 'sources/private/'];
 export const agentInstructions = `# Working on this website
 
-Read typeroll.json, brief/ and decisions.md. Confirm the portal, Organization,
+Read typeroll.json, brief/site.md, brief/rules.md and decisions.md first. Read
+other brief/ files and workflows/ only when relevant. Confirm the portal, Organization,
 Site and working Version before writes. This workspace is not the generated
 publication repository. The CMS owns current content and configuration; local
 sources are proposals unless the user explicitly adopts them.
 
+## Guided start
+
+When the owner needs guidance or a material decision is missing, start or resume
+workflows/interview.md. Read brief/interview.md and existing answers first; ask
+one short question at a time and save progress. Do not repeat confirmed questions
+or treat silence as approval. For a complete brief, proceed directly to
+workflows/new-site.md or workflows/migration.md. All kickoff prompts live here
+in the workspace; public docs explain the flow and link to these source files.
+
 ## Discover only what the task needs
 
 With compact MCP, search_tools then describe_tool; call_read_tool,
@@ -60,12 +71,23 @@ Public documentation: https://typeroll.com/docs/llms.txt
 ## Migrations
 
 Read tr-migration-evidence, then the source-specific recipe (tr-migrate-wp,
-tr-import-url, tr-migrate-astro or tr-migrate-multisite). Record preserve or renew
-intent in brief/migration.md; ask if unclear. Standard blocks first, reviewed
+tr-import-url, tr-migrate-astro or tr-migrate-multisite). Record text_intent and design_intent separately as preserve or renew
+in brief/migration.md; design includes images. Ask if either is unclear. Standard blocks first, reviewed
 custom types next, documented HTML exceptions last. Preserve or meaningfully
 redirect every old public URL. Import completion is not block reconstruction
-or launch acceptance. Compare preserve work to the source, renew work to the
-approved design/content brief. Discover tools and recipes on demand.
+or launch acceptance. Compare text and design/images separately: preserved dimensions to the source,
+renewed dimensions to their approved brief. New design never permits rewriting preserved text. Start with workflows/migration.md for the kickoff
+prompt. The agent rebuilds imported HTML using ordinary block tools; the owner
+does not need to manually convert each Page. No automatic converter is available.
+Discover tools and recipes on demand.
+
+## Project rules and search strategy
+
+Record the owner's preferences and durable constraints in brief/rules.md; put
+approved search intent, topic coverage and URL/indexing strategy in brief/seo.md.
+These are project decisions, not CMS settings or permission to publish. If a
+request conflicts with an agreed rule, ask and record the resulting decision.
+Use workflows/README.md to find the relevant routine, not load every recipe.
 
 ## Everyday requests
 
@@ -82,12 +104,15 @@ Store credentials in the client's private settings or injected environment.
 Run the workspace doctor after setup and after changing the binding.
 `;
 export const workspaceTemplates = {
+    ...BUNDLED_WORKSPACE_TEMPLATES,
     'AGENTS.md': agentInstructions,
-    'README.md': `# Website workspace\n\nKeep project intent here; edit the website through Typeroll CMS.\n\n1. Fill in brief/site.md and brief/brand.md.\n2. Connect hosted MCP at https://app.typeroll.com/api/mcp?tools=compact.\n3. Use an Organization key to create a site, or select an existing one.\n4. Record its IDs and working version in typeroll.json. No secrets belong there.\n5. Run npx @typeroll/mcp-server doctor . (inject TYPEROLL_API_KEY privately).\n\nStart guide: https://typeroll.com/docs/getting-started/agent-workspace/\n\nUpdate the generated scaffold with npx @typeroll/mcp-server init . --update.\nEdited files are preserved and reported for manual reconciliation. Optional local\nrecipes: init . --recipes. They are reference Markdown, not automatically loaded.\n`,
+    'README.md': `# Website workspace\n\nKeep project intent here; edit the website through Typeroll CMS.\n\n1. Read AGENTS.md. For guidance, ask your agent to start or resume workflows/interview.md. Otherwise use workflows/new-site.md or workflows/migration.md. Save confirmed goals, rules and SEO strategy in brief/; record text and design/image choices separately for migrations.\n2. Connect hosted MCP at https://app.typeroll.com/api/mcp?tools=compact.\n3. Use an Organization key to create a site, or select an existing one.\n4. Record its IDs and working version in typeroll.json. No secrets belong there.\n5. Run npx @typeroll/mcp-server doctor . (inject TYPEROLL_API_KEY privately).\n\nStart guide: https://typeroll.com/docs/getting-started/agent-workspace/\n\nUpdate the generated scaffold with npx @typeroll/mcp-server init . --update.\nEdited files are preserved and reported for manual reconciliation. Optional local\nrecipes: init . --recipes. They are reference Markdown, not automatically loaded.\n`,
     'brief/site.md': '# Site brief\n\n## Purpose and audience\n\n## Languages and scope\n\n## Primary user journeys\n\n## Content authority and sources\n\n## Editorial constraints and forbidden internal markers\n',
     'brief/brand.md': '# Brand\n\n## Voice and tone\n\n## Visual direction and references\n\n## Typography, colors and image policy\n\n## Desktop and mobile navigation\n\nRecord intent here; current design tokens belong in CMS settings.\n',
     'brief/content-model.md': '# Content model\n\n## Page types and routes\n\n## Fields and references\n\n## Shared templates and partials\n\n## Taxonomy and navigation\n\nUse the current CMS schema. This document describes decisions, not a second schema store.\n',
-    'brief/migration.md': '# Migration brief (when applicable)\n\n## Intent: preserve or renew\n\n## Source URLs, date and agreed scope\n\n## Design and content acceptance reference\n\n## Retained facts and approved content changes\n\n## Standard blocks, custom types and HTML exceptions\n\n## Old URL to preserved path or relevant redirect\n\n## Prototype and verification evidence\n\nKeep private extracts in sources/private/ and screenshots in qa/reports/.\n',
+    'brief/rules.md': "# Owner preferences and project rules\n\n## Confirmed rules\n\nRecord each rule, its scope, who approved it and the date. Separate confirmed rules from proposals.\n\n## Writing and factual accuracy\n\nVoice, terminology, prohibited claims, source requirements and legal copy that must not be rewritten.\n\n## Design and editing\n\nBrand constraints, accessibility, editable content, standard/custom blocks and documented HTML exceptions.\n\n## Operations and approval\n\nWho may approve content, publication, DNS changes and messages? Credentials stay outside this repository.\n\n## Exceptions and superseded rules\n\nLink decisions.md; do not silently override a confirmed rule. Project notes do not grant permissions beyond the user's authorization or account access.\n",
+    'brief/seo.md': "# SEO strategy\n\n## Business goals, audience, markets and languages\n\n## Search intent and topic coverage\n\nRecord research sources and dates. Distinguish evidence from assumptions; do not invent traffic or ranking forecasts.\n\n## Page roles and URL plan\n\nContent types, useful landing pages, taxonomy, internal links and routes to preserve or redirect. Avoid near-duplicate pages created only for keyword variants.\n\n## Indexing and canonical policy\n\nWhich pages should be indexable, public noindex, or private? Record deliberate canonical overrides and sitemap policy; actual values live in the CMS.\n\n## Editorial standards and structured data\n\nUnique useful copy, supported claims, descriptive titles and links, accessible image text, schema matching visible content. No fixed title length or word count is a hard SEO rule.\n\n## Measurement and review\n\nBaseline, analytics/consent decisions, measures of success and review dates. Never store credentials or private analytics exports here.\n",
+    'workflows/README.md': "# Project routines\n\nRead only the relevant routine and discover current tool schemas through MCP.\nProject files record intent; the CMS owns current content and configuration.\n\n| Task | Project context | On-demand recipe |\n| --- | --- | --- |\n| Guided start | workflows/interview.md, brief/interview.md | Ask one question at a time; resume confirmed answers |\n| New website | workflows/new-site.md, brief/site.md, brief/brand.md, brief/content-model.md | tr-new-site, tr-starter-design |\n| Migration | workflows/migration.md, brief/migration.md | tr-migration-evidence, then tr-migrate-wp or the matching source recipe |\n| Everyday editing | brief/rules.md and the relevant Page | tr-edit-site |\n| SEO | brief/seo.md and current site settings | tr-seo |\n| New reusable block | brief/brand.md and recorded editing needs | tr-custom-blocks |\n| Verification and publication | qa/checklist.md, decisions.md | Current preview/deploy tools and publishing readiness |\n\nAdd project-specific routines here with inputs, steps, acceptance evidence and approval boundaries. Do not copy the complete Typeroll manual or private app guides. Discover enabled app guidance with read_app_documentation. Load a recipe when needed so instructions stay current and context stays small.\n",
     'decisions.md': '# Decisions\n\nRecord date, decision, reason, approved scope and alternatives when useful.\n',
     'sources/README.md': '# Sources\n\nStore research references and copy proposals. Record source URLs and dates.\nPrivate extracts belong in ignored private/ or an approved external store.\nDo not treat local drafts as current CMS content or commit media libraries.\n',
     'scripts/README.md': '# Project automation\n\nKeep repeatable imports and QA scripts here. Use the authenticated REST API\nfor scripted work; keep credentials outside files and inject them at runtime.\nMCP remains the interactive interface. Typeroll currently has no general site CRUD CLI.\n',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeroll/mcp-server",
-  "version": "0.45.76",
+  "version": "0.45.77",
   "description": "Typeroll CMS MCP server – connect AI agents to the REST API to manage content and publish static websites.",
   "license": "MIT",
   "repository": {
@@ -29,7 +29,8 @@
     "dist",
     "AGENTS.md",
     "README.md",
-    "skills"
+    "skills",
+    "workspace-templates"
   ],
   "scripts": {
     "gen": "node scripts/embed-content.mjs",

package/skills/tr-import-url.md

@@ -10,10 +10,10 @@ another MCP client) working through MCP and the public API. The portal's built-i
 AI assistant has no migration tools: it does not import, convert or verify sites.
 
 **Before import or reconstruction:** read `tr-migration-evidence` with
-`read_skill`. Choose preserve (platform change) or renew (new design/content),
-record the brief and verify one prototype per active template before bulk writes.
+`read_skill`. Choose preserve or renew independently for text and design/images,
+record text_intent and design_intent in the brief and verify one prototype per active template before bulk writes.
 Use standard blocks first, reviewed custom types next, rare documented HTML last.
-Both paths must preserve or meaningfully redirect every old public URL. That
+All four combinations must preserve or meaningfully redirect every old public URL. That
 shared contract defines acceptance; this recipe only adds source-specific steps.
 
 
@@ -81,7 +81,7 @@ list_pages limit=5
 ```
 
 Read existing target data to avoid overwriting work. Compare prototypes to the
-source in preserve mode, or to the agreed new design in renew mode. Validate
+source when design_intent is preserve, or to the agreed new design when it is renew. Review text separately. Validate
 standard/custom blocks using `tr-migration-evidence` before mass writes.
 
 ### 3. Fetch and clean each source page
@@ -123,8 +123,8 @@ omit it. Inventory PDFs, download hrefs, srcsets and backgrounds as well.
 
 **d. Adapt to the target's design.**
 Use standard blocks first, then reusable custom types with editable fields.
-Preserve source appearance/text in preserve mode; use the approved new design
-and content plan in renew mode. Raw HTML is the documented last resort.
+Review appearance and text independently according to design_intent and text_intent;
+compare each preserved dimension to the source and each renewed dimension to its approved brief. Raw HTML is the documented last resort.
 
 ### 4. Create pages as drafts
 

package/skills/tr-migrate-astro.md

@@ -10,10 +10,10 @@ another MCP client) working through MCP and the public API. The portal's built-i
 AI assistant has no migration tools: it does not import, convert or verify sites.
 
 **Before import or reconstruction:** read `tr-migration-evidence` with
-`read_skill`. Choose preserve (platform change) or renew (new design/content),
-record the brief and verify one prototype per active template before bulk writes.
+`read_skill`. Choose preserve or renew independently for text and design/images,
+record text_intent and design_intent in the brief and verify one prototype per active template before bulk writes.
 Use standard blocks first, reviewed custom types next, rare documented HTML last.
-Both paths must preserve or meaningfully redirect every old public URL. That
+All four combinations must preserve or meaningfully redirect every old public URL. That
 shared contract defines acceptance; this recipe only adds source-specific steps.
 
 

package/skills/tr-migrate-multisite.md

@@ -10,10 +10,10 @@ another MCP client) working through MCP and the public API. The portal's built-i
 AI assistant has no migration tools: it does not import, convert or verify sites.
 
 **Before import or reconstruction:** read `tr-migration-evidence` with
-`read_skill`. Choose preserve (platform change) or renew (new design/content),
-record the brief and verify one prototype per active template before bulk writes.
+`read_skill`. Choose preserve or renew independently for text and design/images,
+record text_intent and design_intent in the brief and verify one prototype per active template before bulk writes.
 Use standard blocks first, reviewed custom types next, rare documented HTML last.
-Both paths must preserve or meaningfully redirect every old public URL. That
+All four combinations must preserve or meaningfully redirect every old public URL. That
 shared contract defines acceptance; this recipe only adds source-specific steps.
 
 
@@ -69,7 +69,7 @@ required before import; GitHub/build/domain readiness is checked separately for
 publication. Do not infer that every Site shares the same blockers.
 
 Ask explicitly:
-- Which intent applies per Site: preserve or renew? Which source or approved
+- Which text_intent and design_intent apply per Site, each preserve or renew? Which source or approved
   prototype is the **design reference**? Build that one properly first.
 - Are the sites **translations of each other** (same page structure) or
   independent? This decides whether hreflang clusters are mechanical or

package/skills/tr-migrate-wp.md

@@ -10,10 +10,10 @@ another MCP client) working through MCP and the public API. The portal's built-i
 AI assistant has no migration tools: it does not import, convert or verify sites.
 
 **Before import or reconstruction:** read `tr-migration-evidence` with
-`read_skill`. Choose preserve (platform change) or renew (new design/content),
-record the brief and verify one prototype per active template before bulk writes.
+`read_skill`. Choose preserve or renew independently for text and design/images,
+record text_intent and design_intent in the brief and verify one prototype per active template before bulk writes.
 Use standard blocks first, reviewed custom types next, rare documented HTML last.
-Both paths must preserve or meaningfully redirect every old public URL. That
+All four combinations must preserve or meaningfully redirect every old public URL. That
 shared contract defines acceptance; this recipe only adds source-specific steps.
 
 
@@ -80,7 +80,7 @@ Then the ordinary preconditions:
   REST API disabled" if not — common for hardened hosts).
 - The target exists. Establish the source design baseline first, then prove
   representative target templates using `tr-migration-evidence`. Preserve
-  appearance in preserve mode; use the approved design/content brief in renew mode.
+  appearance when design_intent is preserve; use the approved design brief when it is renew. Review text against its separate choice.
 - If the target already has content, you must NOT clobber it — always
   `list_pages` first and only write to slugs that don't already exist.
   Pass the slug explicitly: `create_page` then refuses an address that is
@@ -165,10 +165,10 @@ c. Migrate referenced images with `upload_media_from_url`. The customer's
    media reference only after verification. Stop and report a failed required
    transfer; do not silently hotlink the WordPress source.
 
-The managed importer stores cleaned HTML. Typeroll does not convert HTML into blocks, and `set_page_mode` never rewrites HTML. Pages move to blocks only when someone rebuilds them with blocks.
+The managed importer stores cleaned HTML. Typeroll does not convert HTML into blocks, and `set_page_mode` never rewrites HTML. You, the external agent, rebuild the imported content with ordinary block tools. The owner does not need to convert every Page manually. There is no editor conversion preview; it was removed in Core 0.2.58. Preserve the complete source before switching modes and never publish the empty intermediate Page.
 
 d. Rebuild into editable blocks according to the selected intent. Preserve exact
-   wording in preserve mode; track approved changes in renew mode. Map headings,
+   wording when text_intent is preserve; track approved changes when it is renew, independently of design. Map headings,
    prose, images, buttons and layout to standard fields first, then create
    reviewed custom types where needed. Use raw HTML only for a documented,
    exceptional fragment. Preserve anchors and map every old URL in either mode.

package/skills/tr-migration-evidence.md

@@ -1,6 +1,6 @@
 ---
 name: tr-migration-evidence
-description: Choose preserve or renew intent, map standard and custom blocks, preserve old URLs, and verify content, design and behavior before migration acceptance.
+description: Choose text and design/image preservation independently, map standard and custom blocks, preserve old URLs, and verify content, design and behavior before migration acceptance.
 ---
 
 # Migration evidence contract
@@ -12,22 +12,33 @@ AI assistant has no migration tools: it does not import, convert or verify sites
 Use this shared contract with WordPress, Astro, URL and multisite recipes.
 ## Choose the migration intent before writes
 
-Record `preserve` or `renew` in the workspace's `brief/migration.md` (or the
-project's equivalent brief), with scope, source URLs and the user's decision.
-These are planning labels, not fields accepted by the migration API. Ask when
-the intent is unclear; do not infer redesign permission from “migrate”.
+Record two independent choices in `brief/migration.md` (or the project's
+corresponding brief): `text_intent` and `design_intent`, each `preserve` or `renew`.
+Design includes images. These are planning labels, not migration API parameters.
+Use the starter's `workflows/interview.md` when guidance or decisions are missing;
+resume existing answers. Do not infer either choice from a vague "migrate" or
+"renew", or silently apply an old single-choice brief to both dimensions.
 
-| Intent | Source material | Acceptance reference |
+| Text | Design/images | Acceptance |
 | --- | --- | --- |
-| Preserve: change publishing platform | Keep text, images, structure, visual identity and behavior as closely as practical. | The original site. Record deliberate deviations and their agreed benefit. |
-| Renew: improve design and content | Use source text, images, structure and graphic design as raw material. Agree what to retain, rewrite, combine or replace. | The agreed brief, content plan and approved prototypes, not visual similarity to the old site. |
+| Preserve | Preserve | Compare wording and appearance separately with the source. |
+| Preserve | Renew | Keep wording; compare appearance with approved new prototypes. |
+| Renew | Preserve | Review copy against the editorial brief; keep source appearance, allowing documented layout adjustments for new text length. |
+| Renew | Renew | Review copy and appearance against their separately approved briefs. |
 
-Both paths preserve facts, ownership, required business behavior and historical
-URL continuity. Renewal does not authorize invented claims, removal of useful
-content or an unapproved domain switch. Do not use a partly migrated target as
-an accidental design reference. Protect existing target edits in either path.
+Preserved text includes headings, body copy, CTA labels and captions. Record
+metadata, alt text, legal text and translation rules explicitly; SEO is not an
+exception permitting silent rewrites. With renewed design, list required assets
+and which images may be replaced or generated, including cropping, credits and
+rights. Format/size optimization must not change a preserved image's motif.
 
-## Use editable blocks in both paths
+Record source URLs, dates, approved scope, per-Page exceptions and acceptance
+references separately. Both choices preserve facts, ownership, required behavior
+and historical URL continuity. Renewing design does not authorize text rewrites;
+renewing text does not authorize new imagery. Neither authorizes invented claims,
+unreviewed content removal or domain cutover. Protect existing target edits.
+
+## Use editable blocks for all four combinations
 
 1. Inspect standard block schemas, composition starters, named styles and Page
    templates. Prefer these when they fit.
@@ -60,10 +71,10 @@ still needs a platform fix, not a disguised HTML/CSS workaround.
 
 The managed WordPress importer deterministically stores cleaned HTML and shared
 references, without AI rewriting. That is a source-preserving intermediate step.
-The external agent rebuilds it into reviewed blocks/templates for either intent;
+The external agent rebuilds it into reviewed blocks/templates for all four combinations;
 `set_page_mode` does not perform conversion. Keep the complete source, map every
-in-scope content element, and do not silently truncate long pages. In preserve
-mode retain wording; in renew mode track approved rewrites and source facts.
+in-scope content element, and do not silently truncate long pages. When text_intent is preserve retain wording; when it is renew track approved
+rewrites and source facts, independently of design_intent.
 An import finishing does not mean design, block reconstruction or launch is done.
 
 ## Old URLs must continue to work
@@ -86,10 +97,10 @@ Do not switch traffic until these checks pass and cutover is authorized.
 
 ## Gate 1: source baseline, before conversion
 
-Record the chosen intent, authoritative source URL/date, scope, relevant Core version, active
+Record both chosen intents, authoritative source URL/date, scope, relevant Core version, active
 Page templates and overrides. Inventory home, category/archive, long/short
 articles, downloads, empty related lists and each distinct business surface.
-For preserve, capture source and target geometry; for renew, compare the target
+For design_intent=preserve, capture source and target geometry; for design_intent=renew, compare the target
 with the approved design while retaining source coverage evidence. Capture
 screenshots and computed geometry at matching actual `innerWidth`
 values (320/390/768/1024/1280/1536 where relevant, plus both sides of actual
@@ -249,14 +260,15 @@ pre-cutover scope honestly when DNS or integrations remain out of scope.
 
 The initial route census must combine source sitemaps, internal links, archive
 pagination, CMS inventory and known utility routes. Include homepage, archives,
-404/search behavior and routes outside the sitemap where present. In preserve mode, do not invent
-features absent from the source. In renew mode, include additions in the agreed brief. Assign every route a recipe, template override,
+404/search behavior and routes outside the sitemap where present. Do not invent features absent from the source; include additions only in the agreed brief. Assign every route a recipe, template override,
 composition or documented exception. Inventory the whole shell: content outside
 `main`, header, footer, service navigation and archive heroes are not optional.
 
-Derive required evidence from that census. For preserve, pair every in-scope source/target route
-at mobile and desktop; for renew, compare every target route to its approved
-prototype and account for the source content/URL mapping; add each unique component, breakpoint and interaction
+Derive required evidence from that census. For design_intent=preserve, pair every
+in-scope source/target route at mobile and desktop; for design_intent=renew, compare
+every target route to its approved prototype. Independently compare preserved text
+to the source and renewed text to its editorial brief; account for the source
+content/URL mapping in every combination; add each unique component, breakpoint and interaction
 state. Inspect page-specific media, lists, tables, embeds, CTAs, anchors and related
 content. One representative article cannot attest every article's content.
 

package/workspace-templates/brief/interview.md

@@ -0,0 +1,18 @@
+# Interview progress
+
+Status: not started
+Next question: goal and scope
+
+## Confirmed answers
+
+| Topic | Answer | Source/date | Brief location |
+| --- | --- | --- | --- |
+
+## Proposals and unknowns
+
+Record what is not yet decided, whether it blocks the next step and who can decide.
+
+## Recap and approved next step
+
+Record the owner's confirmation, exact scope and date. Do not infer deployment,
+DNS or message approval from a completed brief. No secrets or raw private transcripts.

package/workspace-templates/brief/migration.md

@@ -0,0 +1,42 @@
+# Migration brief (when applicable)
+
+## Independent choices
+
+- text_intent: undecided (preserve or renew)
+- design_intent: undecided (preserve or renew; includes images)
+
+These are planning labels, not API parameters. Choose each separately. If guidance
+is needed, use workflows/interview.md. A single "renew" must not silently authorize
+both. Expand an older single-choice brief with the owner before dependent writes.
+
+## Source URLs, date and agreed scope
+
+## Text policy and exceptions
+
+Preserve wording, headings, CTAs and captions when text_intent is preserve. Record
+SEO metadata/alt text, legal copy, translation and page-specific exceptions explicitly.
+For renewal, record the approved editorial brief and facts that must remain true.
+
+## Design and image policy and exceptions
+
+Record layout/brand references, required logos/assets, permitted replacements or
+generation, cropping, rights and credits. Design renewal alone never permits text
+rewriting. Preserve image motifs unless a replacement is agreed; format/size
+optimization does not mean changing the image's content.
+
+## Acceptance references
+
+Text: original source for preserve; approved editorial brief for renew.
+Design/images: original source for preserve; approved design/prototypes for renew.
+Record these separately per layout or page when exceptions apply.
+
+## Standard blocks, custom types and HTML exceptions
+
+## Old URL to preserved path or relevant redirect
+
+Both choices retain URL continuity, source facts and required business behavior.
+
+## Prototype and verification evidence
+
+Record text, design/images, links and behavior results separately. Keep private
+extracts in sources/private/ and screenshots in qa/reports/.

package/workspace-templates/workflows/interview.md

@@ -0,0 +1,72 @@
+# Guided website interview
+
+## When to start or resume
+
+Use this routine when the owner asks for guidance or a material decision is missing
+from the brief. Read the existing briefs, decisions and brief/interview.md first.
+Do not restart an interview or ask questions already answered. If the brief is
+complete, summarize it and continue with the relevant routine. This is an agent
+conversation, not a portal wizard or a new API workflow.
+
+## How to conduct it
+
+- Use the owner's language. Ask one short question at a time; offer concrete
+  choices and allow a free answer or "not sure". Explain technical choices plainly.
+- Reuse explicit instructions already given. Distinguish confirmed answers,
+  proposals and unknowns. Never treat silence as approval.
+- If an answer is unknown, suggest an option with its consequences. Research and
+  reversible prototypes may continue; do not perform dependent CMS writes until
+  the necessary decision is confirmed.
+- Save each answer and its source/date in brief/interview.md, and the approved
+  decision in the relevant brief. Keep the next question and unresolved items so
+  another session can resume. Do not store credentials, personal contact lists
+  or raw private transcripts here. No MCP connection is needed to plan locally.
+- Reopen only affected questions when the owner changes direction. Record the
+  change in decisions.md; do not silently replace confirmed rules.
+
+## Interview stages
+
+1. **Goal and scope** — New website or migration? Purpose, audience, language,
+   desired visitor actions, source URL and what is in/out of scope.
+   Save to brief/site.md and brief/migration.md when relevant.
+2. **Target and access** — Existing or new Typeroll Site? Discover accessible
+   Organizations/Sites through MCP and confirm the exact target and Version before
+   writes. Explain any missing storage or access when it becomes relevant; never
+   ask for a secret in chat. Save non-secret IDs to typeroll.json only when known.
+3. **Text decision (migration)** — Preserve existing wording or renew it?
+   Preserve covers headings, body copy, CTA labels, captions and other authored
+   text. Record SEO titles/descriptions, alt text, legal text, translation and any
+   page-specific exceptions explicitly. Renewal needs an agreed editorial brief;
+   it is not permission to invent facts. Save text_intent in brief/migration.md.
+4. **Design and image decision (migration)** — Independently preserve or renew
+   layout, typography, colors and imagery? Offer all four text/design combinations.
+   For renewal, ask which existing assets must remain and which may be replaced
+   or generated. Clarify cropping, logos, credits and image rights. Optimization
+   alone must not change the motif. Save design_intent and asset exceptions in
+   brief/migration.md, and the direction in brief/brand.md. A fresh design never
+   grants permission to rewrite preserved text.
+5. **Content and behavior** — Page types, shared templates, navigation, forms,
+   downloads, integrations and who will edit them. Identify missing capabilities
+   before scaling up. Save to brief/content-model.md. New websites skip migration
+   preservation choices and establish their brand/content brief here.
+6. **SEO and continuity** — Markets, search intent, useful topics and existing
+   valuable URLs. Record evidence separately from hypotheses in brief/seo.md.
+   Confirm metadata policy; text preservation cannot be bypassed as "SEO cleanup".
+   Every old public URL must remain or redirect meaningfully regardless of the
+   two migration choices. Retiring a URL requires a separate agreed exception.
+7. **Owner rules and review** — Non-negotiable copy/design constraints, editing
+   roles and who approves prototypes, publication, DNS or messages. Save confirmed
+   rules to brief/rules.md. Keep technical access separate from user authorization.
+8. **Recap and next action** — Show the scope, both migration decisions (if any),
+   image exceptions, acceptance references, open questions and the next concrete
+   step. Ask the owner to correct/confirm the brief before dependent writes.
+   Reuse existing approval if it already covers that exact step. Brief approval
+   alone does not authorize publication, domain cutover or mail.
+
+## Completion
+
+Mark the interview ready for the agreed next step only when its blocking questions
+are answered; list deferred decisions explicitly. Continue with workflows/new-site.md
+or workflows/migration.md and load only the relevant MCP recipe. Confirm one
+prototype per distinct layout before bulk work. Review preserved dimensions
+against the source and renewed dimensions against the approved brief separately.

package/workspace-templates/workflows/migration.md

@@ -0,0 +1,35 @@
+# Migration kickoff
+
+If guidance is needed, start or resume workflows/interview.md. Otherwise fill in
+this prompt from the confirmed brief. The two preservation choices are independent.
+
+```text
+Migrate [source URL] to Typeroll, Organization [ID/name], Site [ID/name], Version [ID].
+Text: [preserve existing wording / renew against an agreed editorial brief].
+Design and images: [preserve / renew against an agreed design brief].
+Read AGENTS.md and use workflows/interview.md for missing decisions.
+Read tr-migration-evidence, then tr-migrate-wp (or the appropriate source recipe).
+Confirm the target and import readiness before writes. Inventory URLs, content,
+media, templates and integrations; record both choices and exceptions in brief/migration.md.
+Build and verify one prototype per distinct layout before bulk reconstruction.
+Use standard blocks first, editable custom types next, isolated HTML only for
+justified exceptions. Rebuild imported HTML with block tools; a mode switch does not convert it.
+Keep preserved text unchanged even when the design is new. Record which images
+may change. Preserve every old public URL or redirect to a relevant destination.
+Protect existing CMS edits. Review text and design/images against their own
+acceptance references, plus mobile/desktop behavior, downloads, forms and URL coverage.
+Report unverified items separately. Do not publish, switch DNS or send messages
+without explicit approval.
+```
+
+The managed importer stages cleaned HTML, media and shared references in Review.
+The external agent can then reconstruct those Pages; no manual editor conversion
+is required. An agent can also build block Pages directly from source material.
+Neither path includes an automatic HTML-to-blocks converter. Read and preserve the
+full source before switching modes, then save/read back and preview the rebuilt
+Page on the selected Version. Never publish an empty intermediate block Page.
+
+Track import, block reconstruction, separate text/design review, candidate
+publication and domain cutover as separate milestones. Import completion is not
+launch approval. All four text/design combinations use the same block hierarchy
+and URL continuity contract. Planning choices are not migration API fields.

package/workspace-templates/workflows/new-site.md

@@ -0,0 +1,17 @@
+# New website kickoff
+
+Use this prompt only when the brief is already clear. Otherwise start or resume
+workflows/interview.md; the owner does not need to fill in every document alone.
+
+```text
+Create [website] for [audience and purpose] in Typeroll Organization [ID/name].
+Read AGENTS.md, confirm the Site and Version, and use workflows/interview.md for
+missing decisions. Record confirmed goals, brand, content model, owner rules and
+SEO strategy in brief/. Read tr-new-site and relevant tool schemas on demand.
+Build representative desktop/mobile layouts with editable blocks and shared templates.
+Share previews, record accepted decisions and keep unresolved items explicit.
+Do not publish, change DNS or send messages without explicit approval.
+```
+
+The CMS owns current content and settings. The repository owns the brief, rules,
+decisions and evidence. Load recipes when needed, not the whole manual.