@typeroll/mcp-server 0.45.19 → 0.45.21

package/AGENTS.md

@@ -1057,3 +1057,45 @@ is the manual numeric order; null clears it. Missing sort values come last and
 IDs break ties. Explicit ID lists keep their order. Typed `list_pages` queries
 inherit type sorting and accept `sort_by`/`sort_order`; unfiltered API lists
 default to stable IDs. See the public Content types guide for editor steps.
+
+## Artifact SEO checks (Core 0.2.22)
+
+`read_publishing_readiness` and dry-run export checks do not validate future HTML.
+After `trigger_deploy`, inspect `get_deploy_status.seo_report`: blocking technical
+errors preserve the current live site, while editorial warnings require review.
+Reports identify URL, generated file/line and block/page/field where available.
+Do not automatically rewrite copy, remove intentional noindex or invent facts.
+`noindex` and `nofollow` are independent Page fields; `sitewide_nofollow` and
+`seo_review` (forbidden_markers, phrase/guidance claims, review notes) are settings.
+All output is rechecked, including reused pages. Schema field maps support direct
+properties only: reject dotted paths rather than inventing nested addresses.
+Read https://typeroll.com/docs/guides/publication-validation/ for the contract
+and customer migration guidance. Update the organization build engine after the
+matching Core release before publishing.
+
+
+## Typed owner answers and pending review (next release)
+
+Core 0.2.24 does not include this contract. Boolean answers distinguish true,
+false and unknown; omit untouched answers and send null only for an intentional
+clear. Structured arrays use an explicit stable text `item_key`. Sources and
+authority apply per schema leaf; unchanged imported values are not confirmed.
+`answer_sources` on Page updates/replacements accepts source_url/import_run_id,
+never actor identity. Owner/reviewer values cannot be overwritten by imports or
+agents. Report conflicts rather than retrying an overwrite.
+
+Owner Extensions submit isolated proposals using the current answer revision.
+Pending proposals are outside Pages, working copies and publication. Review is
+an explicit, idempotent decision; acceptance and publication are separate.
+Site-admin MCP tools list/read/configure/decide/revoke owner proposals and manage
+bounded notification retry/recovery. Never include private review links or
+identities in public content. See the shared owner-review guide for the full
+API and migration contract. Private app authentication remains app-owned.
+
+An ordinary site administrator can use `call_extension_admin` for an enabled app's
+host-approved native admin API. Read that installation's private guide for the
+relative path, schema and effects. This does not expose delegation credentials or
+automatically publish. `read_owner_answers` and `override_owner_answers` provide
+revision-bound, reason-audited administrative correction; a rejected import is not
+permission to override an owner. An app must require the owner-fields descriptor's
+`review_ready` before issuing a visitor editing link.