canopycms 0.12.0 → 0.13.0

package/CHANGELOG.md

@@ -5,9 +5,9 @@ packages release together, at one version.
 
 ## This build
 
-Version `0.12.0`, built from [`b67d39a`](https://github.com/safeinsights/canopycms/tree/b67d39a9a60e1c1d9dd23324c78df06c2295afa8).
+Version `0.13.0`, built from [`b5a1131`](https://github.com/safeinsights/canopycms/tree/b5a1131194aa99a6532f84792caf439f6d358e67).
 
-Its entries are [0.12.0](#0120), under **Released**.
+Its entries are [0.13.0](#0130), under **Released**.
 
 If you upgraded from a build on another branch, compare the `<!-- changeset: … -->` slugs in your previous build's `CHANGELOG.md` (`npm pack canopycms@<old>` fetches it) with this one's: entries whose slug your old file lacks are new to you.
 
@@ -24,7 +24,7 @@ Each entry has up to three parts:
 `node_modules/canopycms/CHANGELOG.md`, assembled for that build: its **This build** section lists
 what is new since the previous int on the same branch, or on a stable release links its entries, and its links point at the commit the build
 came from. The copy in the repository holds released history and the entries from before changesets;
-every entry written since is a file in [`.changeset/`](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/.changeset/README.md) until a stable release
+every entry written since is a file in [`.changeset/`](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/.changeset/README.md) until a stable release
 moves it here.
 
 **Find your starting point.** From a stable pin, start at the first version under **Released**
@@ -62,6 +62,284 @@ entries under **Released**.
 
 ## Released
 
+### 0.13.0
+
+#### Focus stays in "Show changes" after an entry-level conflict choice
+
+<!-- changeset: conflict-entry-choice-focus -->
+
+_First in 0.13.0._
+
+**What changed.** After "Keep it", "Keep it deleted", "Restore entry" or "Keep your version" on a
+conflict card, a status line says what happened. Focus moves to "Restore entry" while the entry
+stays deleted, and otherwise to the drawer's title, instead of dropping to the page.
+
+#### "Keep it deleted" on a conflict checks that the entry is still gone
+
+<!-- changeset: conflict-keep-deleted-check -->
+
+_First in 0.13.0._
+
+**What changed.** If an entry came back after "Show changes" opened (from another tab, or a
+restore whose answer was lost), "Keep it deleted" no longer clears its conflicts. The card reloads
+and shows what is left to choose.
+
+#### "Use latest version" never changes another list item
+
+<!-- changeset: conflict-use-latest-other-item -->
+
+_First in 0.13.0._
+
+**What changed.** In a list whose items look alike, a save could give one item the key of an item
+you had removed. That item's conflict card then offered "Use latest version", which overwrote the
+look-alike, and showed it as your version. The card now shows that item as removed, and its
+latest version can't be placed: change it in the form by hand, then choose "Mark resolved".
+
+#### "Get latest changes" works in dev mode
+
+<!-- changeset: dev-get-latest-changes -->
+
+_First in 0.13.0._
+
+**What changed.** In dev mode, "Get latest changes" now shows on an editing branch. The request
+runs the worker's merge for that branch alone and answers before it returns, so the result and
+any conflicts show at once. It brings in the local remote's base; a branch cloned from another
+remote is told so and left as it is. Prod still queues the request for the CMS worker, as before.
+
+#### A refused "Get latest changes" that is a conflict shows yellow
+
+<!-- changeset: get-latest-refusal-colour -->
+
+_First in 0.13.0._
+
+**What changed.** When "Get latest changes" is refused because of the branch's state, for example
+a branch in review or one busy with a save, the message now shows yellow, as other conflicts do.
+Other failures stay red.
+
+#### "Latest changes waiting" in the branch bar
+
+<!-- changeset: latest-changes-waiting -->
+
+_First in 0.13.0._
+
+**What changed.** The automatic sync still skips a branch with saved but uncommitted work and
+commits nothing on a timer. When the base has moved on meanwhile, the branch bar now shows "Latest
+changes waiting", whose tooltip points to "Get latest changes". It clears once the branch holds the
+base again.
+
+#### Approve and Request changes pin the commit the reviewer saw — **behaviour change**
+
+<!-- changeset: review-pins-the-commit-seen -->
+
+_First in 0.13.0._
+
+**What changed.** Approve and Request changes now send the commit the reviewer's page showed, and
+the API refuses either one when the branch has moved since: "This branch changed since you opened
+it. Review the latest changes." The editor then reloads the branch, keeping a Request changes
+note for the next try. An approval records its commit, and the worker sends an approved branch
+back to review when commits come in that are more than that commit with the base merged in. An editor tab opened before this
+release is refused the same way until the page is reloaded.
+
+#### A "CanopyCMS conflicts" status on pull requests — **new GitHub App permission**
+
+<!-- changeset: conflicts-commit-status -->
+
+_First in 0.13.0._
+
+**What changed.** The worker sets a `CanopyCMS conflicts` commit status on each pull request's
+head: it fails with the number of choices still open in the editor, and passes once none are.
+Make it a required check in branch protection to stop a by-hand merge of undecided content, on a
+branch the CMS opens every pull request into: other pull requests never get it.
+`init-github-app` now asks for the "Commit statuses: read and write" permission, and `verify`
+reports an installation without it. Until an installation has it, only the status is refused, and
+System health says so.
+
+**To adopt.** On an existing GitHub App, its owner adds "Commit statuses: read and write" in the
+App's permissions on GitHub, an owner of the account it is installed on accepts the request in the
+installation's settings, then `canopycms init-github-app verify` confirms it. A fine-grained token
+needs "Commit statuses: read and write"; a classic token's `repo` scope already covers it. See
+[Submitting for Review](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#submitting-for-review).
+
+#### List items rewritten to read like one deleted item no longer conflict as a whole list
+
+<!-- changeset: fm-list-items-rewritten-alike -->
+
+_First in 0.13.0._
+
+**What changed.** When one side of a merge rewrote two or more list items to read exactly like an
+item it deleted, the field merge raised a conflict on the whole list. Each rewritten item now
+merges as the item its key names. Where that side also copied an item it rewrote this way, the
+copy now stays a new item instead of being read as the original and dropped.
+
+#### Update branch on GitHub no longer leaves list items under keys that name other items
+
+<!-- changeset: fm-rekey-update-branch -->
+
+_First in 0.13.0._
+
+**What changed.** When "Update branch" on a pull request merges the base into a branch, git keeps each list item under the key the branch's copy held, which can name another item once the base changed it. Later merges could then misread the item and undo a deletion or miss a conflict. The worker now takes such a merge in with one more commit that gives those items the keys the field merge would, and moves the branch's comment threads with them. The commit changes item keys only, so an approved branch stays approved. On GitHub it is a new push to the pull request, which dismisses approvals where the repository dismisses stale approvals.
+
+#### "Get latest changes" reports the conflicts a merge of GitHub's commits leaves
+
+<!-- changeset: get-latest-answer-after-github-merge -->
+
+_First in 0.13.0._
+
+**What changed.** When the latest changes reached a branch through its pull request on GitHub, for example after Update branch, "Get latest changes" merged them, then answered "You already have the latest changes" a cycle later, even where the merge left values for a person to choose. Where that merge holds the base, it now answers as a merge of the base does, with the conflicts to resolve, and the "Latest changes waiting" badge clears at once.
+
+#### An item moved into a list no longer takes the identity of the copy beside it
+
+<!-- changeset: merge-moved-in-item-keeps-identity -->
+
+_First in 0.13.0._
+
+**What changed.** When an editor duplicated a list item, moved the copy to another list, and later moved the original into that list above the copy, the field merge could read the original as the copy. The base's edit of the copy then landed on the original with no conflict shown, and a base deletion of the copy was reported against the wrong item. An item now takes another's identity from a look-alike key only where no item on its side holds that item's own key, and never when the key belongs to an item of another list. Such a moved-in item is also no longer merged into an alike item the other side added to that list, so neither is lost.
+
+#### A rebased branch publishes only the commits the rebase made
+
+<!-- changeset: rewrite-publish-rebased-tip -->
+
+_First in 0.13.0._
+
+**What changed.** After rebasing a branch it had already published onto the base, the worker publishes the rewritten history to the workspace's remote and GitHub. It read the branch's head for that a few steps after the rebase. If the worker had lost its lock and the editor committed saved work in that moment, that unsubmitted work was published too. The worker now publishes the commit the rebase made, and saved work committed after it stays unpublished until it is submitted.
+
+#### An entry deleted or renamed in the editor no longer comes back when GitHub's commits are taken in
+
+<!-- changeset: take-in-keeps-saved-deletes -->
+
+_First in 0.13.0._
+
+**What changed.** When a branch's copy on GitHub had commits the editor's workspace lacked, such as an Update branch or a maintainer's fix, the worker brought them in and wrote back any entry the editor had deleted, or the old path of one it had renamed, while that change was not yet submitted. The deletion was lost, or a renamed entry ended up twice. The worker now waits instead, as it already does for a saved edit to a file those commits change. An editing branch that lacks the base shows that the latest changes are waiting, and the deletion merges with GitHub's commits once it is committed, by "Get latest changes" or a submit.
+
+#### Saved work stays off GitHub until it is submitted — **behaviour change**
+
+<!-- changeset: unsubmitted-work-stays-unpublished -->
+
+_First in 0.13.0._
+
+**What changed.** When the worker brings the base branch, or commits made on GitHub, into a branch
+that holds saved work its author has not submitted, the merge stays in the branch's clone: neither
+the worker's own repository nor GitHub receives it until the author submits, whose push carries it.
+This holds for a withdrawn branch, one sent back with "Request changes", and one whose GitHub branch
+was deleted, which the worker no longer recreates with that work. Finishing an interrupted rewrite
+of a published branch publishes only the rewritten history, never a commit made since.
+
+### 0.12.1
+
+<!-- changeset: field-merge-engine -->
+<!-- changeset: fm-catch-up-main -->
+<!-- changeset: fm-deleted-entry-conflict-card -->
+<!-- changeset: fm-latest-changes-after-publish -->
+<!-- changeset: fm-r1-stale-key-guard -->
+<!-- changeset: fm-stale-first-save-keys -->
+<!-- changeset: fm-trade-off-regression -->
+<!-- changeset: fm-twin-stale-keys -->
+
+#### `canopycms backfill-item-keys` writes every list item's key
+
+<!-- changeset: backfill-item-keys -->
+
+_First in 0.12.1._
+
+**What changed.** A new command writes the `_key` of every object-list item and block into your content, exactly as an editor save of the unedited entry would. Until a file holds its keys, an editor's first save adds `_key` lines beside the real edit, and those lines can conflict with changes the base branch makes to the same entry meanwhile. `--check` writes nothing and exits 1 when any file needs keys. See [Keying list items](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#keying-list-items).
+
+**To adopt.** Once, on a clean checkout of your base branch: run `npx canopycms backfill-item-keys`, review the files it lists as also normalised, and commit the result on its own, with nothing else in the commit. Optionally gate CI on `npx canopycms backfill-item-keys --check`.
+
+#### A damaged conflict record holds its branch until an admin releases it
+
+<!-- changeset: field-merge-conflict-record-hold -->
+
+_First in 0.12.1._
+
+**What changed.** When a branch's record of conflicting changes can't be read, the worker sets it
+aside and the branch waits: Submit for review and Approve refuse, rather than going ahead as if
+nothing needed a choice. Everyone sees "Needs action" in the branch bar, with Submit for review held
+and the reason; an admin also gets "Release hold", whose confirm says which choices are lost. A
+later merge from the base leaves the hold in place, as it can't find the lost choices again. A
+record written in another format is left as it is: Submit and Approve refuse until a developer deals
+with it.
+
+#### A conflict in a list without item keys shows the latest version
+
+<!-- changeset: field-merge-conflict-value-paths -->
+
+_First in 0.12.1._
+
+**What changed.** When the base edited an item in a list whose items carry no keys, the conflict
+card couldn't find the latest version's value: it read as empty, and only editing by hand was
+offered. The merge now records where each version holds the value, so the card shows all three
+versions and "Use latest version" works there too.
+
+#### Submit and approve wait until conflicting changes are resolved
+
+<!-- changeset: field-merge-conflicts-api -->
+
+_First in 0.12.1._
+
+**What changed.** A field that a merge from the base found changed differently on both sides stays
+open until someone chooses a value. Saving the entry with that choice resolves it, and an entry
+that one side deleted or that can't be merged field by field is resolved by keeping, deleting,
+restoring or taking the latest version. While any conflict is open, Submit for review and Approve
+answer 409 and say why. The catch-all route serves the conflicts to the editor, so adopters add
+nothing.
+
+#### "Get latest changes" brings the base branch into an editing branch on request
+
+<!-- changeset: get-latest-changes -->
+
+_First in 0.12.1._
+
+**What changed.** An editing branch's bar and card offer "Get latest changes" (prod). It commits
+the branch's saved work locally, then asks the worker to bring the base branch in at once instead
+of at its next sync. The form is read-only while the worker works, for up to two minutes, and a
+toast reports the result. Withdrawing the open branch from review when it conflicts with its base gets
+the latest changes too. A worker that archives a merged pull request also syncs the other branches
+soon after. Dev mode runs no worker, so it doesn't offer the button.
+
+**Deploy order.** Deploy the worker before the CMS image. An older worker fails the new
+`sync-branch` task, and the request is then answered only by its next regular sync.
+
+#### Choose what to keep when you and someone else changed the same field
+
+<!-- changeset: field-merge-conflict-ui -->
+
+_First in 0.12.1._
+
+**What changed.** When the latest changes come into a branch and a value was changed both there
+and on the branch, "Show changes" opens with a "Conflicts" group above the entry's changes. Each card
+shows how the value read before, in the latest version and in yours, and offers "Use latest version",
+"Keep your version" or "Edit". A value one side removed offers "Remove it" or "Keep it", and long text
+gets one card per changed passage, with "Use both". A choice is saved with the entry. The entry
+says how many fields need a choice, "Submit for review" waits until none do, and the "Get latest
+changes" message counts them. Authors never see a branch name in this copy.
+
+#### A branch in review takes in its base when no field clashes
+
+<!-- changeset: field-merge-review-branches -->
+
+_First in 0.12.1._
+
+**What changed.** When GitHub reports that a submitted or approved branch's pull request conflicts
+with its base, the worker now merges the base in field by field instead of holding the branch. A
+submitted branch stays submitted. An approved branch returns to review, since the merge settled
+what git could not and no reviewer has seen that. A field changed differently on both sides, or
+anything else a person must decide, still holds the branch with "Needs action", and its author
+withdraws it to choose, as before.
+
+#### Base changes are no longer reverted when a branch takes in its base
+
+<!-- changeset: field-merge-worker -->
+
+_First in 0.12.1._
+
+**What changed.** When the base branch moves and an editing branch has changed the same entry,
+the worker merges the two field by field instead of keeping the branch's whole file. Edits to
+different fields, list items or body paragraphs all come in, schema changes made on the base stay,
+and a field changed differently on both sides keeps the author's value and is flagged on the entry,
+as before. An entry renamed on one side and edited on the other merges at the new name. A branch with no
+merge commit still rebases where git takes the base in cleanly and the field merge agrees; any
+other takes the base in with a merge commit.
+
 ### 0.12.0
 
 #### Undo a branch's saved changes from "Show changes"
@@ -118,7 +396,7 @@ _First in 0.9.0._
 
 **What changed.** A new scalar field type, `date`, holds a calendar day as a `YYYY-MM-DD` string, edited with a day picker. `datetime` stores an instant, so a day picked in one zone can read as the day before in another; a `date` is the same day everywhere. A save and a production build refuse a value that is not a real day, such as `2026-02-30` or `2026-5-1`; YAML rolls an unquoted `2026-02-30` forward first, so quote hand-written days. A hand-written unquoted `2024-05-01` in md or mdx frontmatter reads as that day in every zone, and survives a save on its own line. `list: true` is refused on a `date`; use an object list with a `date` field inside, which `itemTitleField` may name. `stampOnPublish` stays on `datetime`, and `datetime` values and checks are unchanged. Editor field errors now meet 4.5:1 contrast.
 
-**To adopt.** Change `type: 'string'` to `type: 'date'` on a field that holds `YYYY-MM-DD`: `TypeFromEntrySchema` still gives `string`, and every `YYYY-MM-DD` value stays as it is. A production build lists any entry whose value is not a real day, such as `2026-5-1`; fix those by hand. A custom field type that was named `date` keeps its `customRenderers` entry but is now checked as a `date`, so rename it if its values differ. See [Field Types](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/.changeset/README.md#field-types).
+**To adopt.** Change `type: 'string'` to `type: 'date'` on a field that holds `YYYY-MM-DD`: `TypeFromEntrySchema` still gives `string`, and every `YYYY-MM-DD` value stays as it is. A production build lists any entry whose value is not a real day, such as `2026-5-1`; fix those by hand. A custom field type that was named `date` keeps its `customRenderers` entry but is now checked as a `date`, so rename it if its values differ. See [Field Types](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/.changeset/README.md#field-types).
 
 **Now deletable.** A `string` field with a hand-written `YYYY-MM-DD` format check, and site code that reads a `datetime` back into a day.
 
@@ -394,7 +672,7 @@ _First in 0.7.0._
 
 **What changed.** The pull request a submit opens now lists the branch's unresolved editor comment threads: where each one is, the first line of its first comment (80 characters at most) and a link to it in the editor. Once every thread is resolved, it says so. The list is updated whenever a comment is added, replied to or resolved, as well as on submit. Comment excerpts are visible to everyone who can read the pull request, which on a public repository means everyone. Open threads do not block the merge or keep the pull request in draft. A pull request opened before this release shows no list until its branch is next submitted.
 
-**To adopt.** Nothing, if your deploy replaces the worker along with the CMS, as `cdk deploy` of the canopycms-cdk stack does with the default `workerCode`. A worker on an earlier release fails each update of the list and marks the branch's sync failed until a later task succeeds, so a pipeline that leaves the worker behind must roll it no later than the CMS: see [Rolling the worker from CI](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#rolling-the-worker-from-ci).
+**To adopt.** Nothing, if your deploy replaces the worker along with the CMS, as `cdk deploy` of the canopycms-cdk stack does with the default `workerCode`. A worker on an earlier release fails each update of the list and marks the branch's sync failed until a later task succeeds, so a pipeline that leaves the worker behind must roll it no later than the CMS: see [Rolling the worker from CI](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#rolling-the-worker-from-ci).
 
 #### Pull request bodies link back to the editor
 
@@ -404,7 +682,7 @@ _First in 0.7.0._
 
 **What changed.** The pull request a submit opens links to the branch in the editor, and each changed entry to that entry. A notice tells reviewers that comments on the pull request do not reach the editor, so the author will not see them. The links use the editor's URL from the submit, accepted only when its host is the one the request was addressed to (`X-Forwarded-Host`, else `Host`), which holds behind `canopycms-cdk`'s CloudFront distribution as it stands.
 
-**To adopt.** Nothing, unless a proxy in front of the CMS sets neither header to the editor's public host: then set `editorUrl` in your Canopy config to the editor page's URL, e.g. `editorUrl: 'https://cms.example.org/edit'`. See [the config reference](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#definecanopyconfig-options).
+**To adopt.** Nothing, unless a proxy in front of the CMS sets neither header to the editor's public host: then set `editorUrl` in your Canopy config to the editor page's URL, e.g. `editorUrl: 'https://cms.example.org/edit'`. See [the config reference](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#definecanopyconfig-options).
 
 #### CloudFront origin read timeout accepted up to 120 s; the editor waits 135 s
 
@@ -490,7 +768,7 @@ _First in 0.6.0._
 
 **What changed.** `CanopyCmsService` takes `clerkOrganizationsAsGroups` (default `true`, unchanged), which the worker honours; in a deployment it, not the plugin's `useOrganizationsAsGroups`, decides the groups. When Clerk refuses the organization list with a 403 (Organizations disabled), the refresh now writes users with no groups and logs a warning, instead of failing whole; any other failure still keeps the last snapshot. Memberships are fetched instance-wide rather than per user. The scaffolds write `false` explicitly: `useOrganizationsAsGroups` in `canopycms init`'s `canopy.ts`, and `clerkOrganizationsAsGroups` in `canopycms init-deploy aws`'s CDK stack.
 
-**To adopt.** On a Clerk instance without Organizations, set `clerkOrganizationsAsGroups: false` on `CanopyCmsService` and `useOrganizationsAsGroups: false` in `createClerkAuthPlugin`. See [Deploying to AWS](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md).
+**To adopt.** On a Clerk instance without Organizations, set `clerkOrganizationsAsGroups: false` on `CanopyCmsService` and `useOrganizationsAsGroups: false` in `createClerkAuthPlugin`. See [Deploying to AWS](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md).
 
 ### 0.5.0
 
@@ -502,7 +780,7 @@ _First in 0.5.0._
 
 **What changed.** A `type: 'reference', list: true` field now edits as rows in stored order, like an `object` list: drag a row or use its "…" menu to move or remove it, open a row to swap its entry in place, and pick from Add under the rows to append. Neither control offers an entry the list already holds. Any `list: true` field, and any `block` field, takes `maxItems`. The editor stops adding at the cap and says why, a save over it is refused, and a production build fails on an entry over it, naming the entry, field, count and cap. Adding `maxItems` to a list that already holds more therefore fails the build until an editor removes the extra items. `maxItems` on a field that holds no items is refused when the entry schema registry is created.
 
-**To adopt.** Set `maxItems: 3` on the list field in its entry schema. See [Field Types](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#field-types).
+**To adopt.** Set `maxItems: 3` on the list field in its entry schema. See [Field Types](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#field-types).
 
 #### SEO field location moves into config; reference pickers mark hidden entries and take a sort order — **breaking: `createNextCanopyContext({ seo })` and `AIContentConfig.seo` are removed**
 
@@ -512,7 +790,7 @@ _First in 0.5.0._
 
 **What changed.** `defineCanopyConfig` takes `seo: { group?, fields? }`, the one place every surface reads an entry's `noindex` flag: the sitemap and `entryToMetadata` that `createNextCanopyContext` returns, AI content and the editor's reference picker. A per-call `seo`/`group`/`fields` still overrides it. The free `generateContentSitemap` takes `seo` as an argument and refuses to run without it when the config sets one; `createNextCanopyContext` and the AI content config refuse a leftover `seo`. A reference picker now badges an entry hidden from search as "Hidden from search", and picking one adds a note naming the setting on that entry's form, since a page listing only indexed entries won't show it. A reference field takes `optionSort`: `'label'` (the default), `'collection'`, or `{ field, direction }`. Point `field` at an ISO date, since strings compare as text.
 
-**To adopt.** Move `seo` from `createNextCanopyContext({ seo })` and from `defineAIContentConfig({ seo })` into `defineCanopyConfig({ seo })`. See [Sitemap and SEO Metadata](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#sitemap-and-seo-metadata) and [How References Work in the Editor](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#how-references-work-in-the-editor).
+**To adopt.** Move `seo` from `createNextCanopyContext({ seo })` and from `defineAIContentConfig({ seo })` into `defineCanopyConfig({ seo })`. See [Sitemap and SEO Metadata](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#sitemap-and-seo-metadata) and [How References Work in the Editor](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#how-references-work-in-the-editor).
 
 **Now deletable.** A shared `seo` constant passed separately to the Next context and the AI content config.
 
@@ -540,7 +818,7 @@ resolved without it.
 **To adopt.** Where a reference renders its target's prose, set `includeBody: true` on that
 reference field. Code that reads the body from a link-only reference's resolved type now sees
 `string | undefined`; either set `includeBody: true` or handle the missing value. See
-[Resolving References in a Listing](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#resolving-references-in-a-listing).
+[Resolving References in a Listing](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#resolving-references-in-a-listing).
 
 ### 0.3.3
 
@@ -957,7 +1235,7 @@ URL.
 2. For a branch preview: wrap views with `withCanopyPreview` in a `'use client'` module, add
    `app/preview/[[...path]]/page.server.tsx`, set `editor.previewPrefix: '/preview'`, and serve that
    route with `frame-ancestors 'self'`, not `X-Frame-Options: DENY` (see
-   [Live Preview](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#live-preview)).
+   [Live Preview](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#live-preview)).
 3. A test reading view content from the route's server HTML must load the page in a browser.
    Server output rendered during a preview request carries the signed-in asset prefix; keep it out
    of cross-request caches (`unstable_cache`, module memos).
@@ -972,7 +1250,7 @@ kept site styles ahead of Mantine's in the preview.
 server components. A string path marks the form's spelling (`'a.0.b'` marks `a[0].b`), and an empty
 path marks nothing. The editor counts and logs marks naming no field. `createEntrySchemaRegistry`
 refuses a field name that is empty, all digits or contains `.`, `[` or `]`. See
-[Live Preview](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#live-preview).
+[Live Preview](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#live-preview).
 
 **To adopt.** Fix each path that stops compiling; the error lists valid ones. Rewrite computed paths
 as literal segments, or type that component's prop as plain `FieldProps`. Pass `fieldProps` as
@@ -1054,7 +1332,7 @@ or a failed render) renders as its plain text, with no URL; any other form of th
 fields are nested or renamed, pass the AI config's `seo` the same object you pass
 `createNextCanopyContext({ seo })`, so the sitemap and AI content read the flag from the same
 place. A field that links to a hidden section by plain URL needs a field transform; the README
-shows [the recipe](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#ai-content-configuration).
+shows [the recipe](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#ai-content-configuration).
 
 **Now deletable.** An `exclude.where` that re-read the `noindex` flag by hand.
 
@@ -1076,7 +1354,7 @@ A `markdown` field with `renderAs: 'mdx'` is checked as MDX, and `mdxAllow` narr
 field or site-wide. New: field options `renderAs`, `mdxAllow`; config key `mdxAllow`; type
 `MdxAllowlist`. (int.110) A component prop allowance can be `'string'` (or
 `{ type: 'string', maxLength }`): a quoted value only, never bare or `{…}`. See
-[MDX content cannot run code](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#mdx-content-cannot-run-code).
+[MDX content cannot run code](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#mdx-content-cannot-run-code).
 
 **To adopt.** Set `renderAs: 'mdx'` on each `markdown` field your site compiles as MDX, and
 `mdxAllow` to what your renderer takes. Set `executable: true` only on a field whose editors you
@@ -1213,7 +1491,7 @@ a format check.
 
 - (int.93) Submit commits gain an `Edited-by: Name (id)` trailer; PR bodies gain a section that
   re-submits replace, keeping human text. Options: `gitEditedByTrailers`, `gitCoAuthoredByTrailers`
-  ([reference](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#definecanopyconfig-options)).
+  ([reference](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#definecanopyconfig-options)).
 - (int.110) Submit-commit trailers name every user who saved since the last submit commit, and
   the PR-body section every user who edited the branch, not only the submitter; settings commits
   (permissions, groups) carry the acting user's trailer.
@@ -1237,7 +1515,7 @@ saves only push the branch, and no failing PR task lands in System health.
 that entry type goes unavailable: the editor says so, and its entries answer 503 with
 `code: 'SCHEMA_UNAVAILABLE'`. Builds, static deploys and `generate-ai-content` still fail. The
 worker holds the base branch for up to 30 minutes while that lasts; see
-[New schemas wait for the editor deploy](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#new-schemas-wait-for-the-editor-deploy).
+[New schemas wait for the editor deploy](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#new-schemas-wait-for-the-editor-deploy).
 Public types gain optional `unavailable` on `EntryTypeConfig` and `FlatSchemaItem`, optional
 `ApiResponse.code`, and a required `SchemaResolutionResult.issues`.
 
@@ -1275,7 +1553,7 @@ hang until the drain heartbeat lets termination continue. Its in-flight task is
 new stack needs no steps.
 
 **What changed.** (int.109) Detailed in
-[The worker instance](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#the-worker-instance): IMDSv2 with a hop limit of 1; the
+[The worker instance](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#the-worker-instance): IMDSv2 with a hop limit of 1; the
 bundle is one file whose sha256 user data checks, readable as that one object; a file-system policy
 refusing clients without TLS or IAM, replacing the worker's
 `AmazonElasticFileSystemClientReadWriteAccess`; an encrypted gp3 root volume; a boot-time upgrade to
@@ -1329,10 +1607,10 @@ failure and exits non-zero on `selfStopped`, with a code outside `RestartPrevent
   with its hash, as `worker/dist/index.js` and `index.js.sha256`. The default, `'asset'`, is
   unchanged.
 - `CanopyCmsService` alarms when the worker logs no git sync for 30 minutes. See
-  [Worker-down alarm](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#worker-down-alarm).
+  [Worker-down alarm](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#worker-down-alarm).
 
 **To adopt.** Optional. For parameter-only change sets, see
-[Rolling the worker from CI](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#rolling-the-worker-from-ci). For the alarm, pass
+[Rolling the worker from CI](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#rolling-the-worker-from-ci). For the alarm, pass
 `alarmTopic`.
 
 **Now deletable.** A manual `cdk deploy` after each canopycms bump whose only purpose is moving the
@@ -1343,7 +1621,7 @@ worker, and a hand-built alarm on the worker log group.
 **What changed.** (int.112) The boot's `dnf upgrade` could be OOM-killed on every retry. A 1 GiB
 swap file now goes on first; an upgrade that still fails starts the worker unpatched and notifies
 `alarmTopic` if set; a retried step names itself when it gives up. See
-[The worker instance](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#the-worker-instance).
+[The worker instance](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#the-worker-instance).
 
 **To adopt.** Deploy, which replaces the worker instance. The bundle needs none of this, so it is
 not Template first and the worker contract stays at 1.
@@ -1409,7 +1687,7 @@ and operations may reuse GitHub fetches under 30 seconds old.
 
 **To adopt.** Nothing. Seeding `remote.git` stages a copy of the repository beside the gateway's
 mirror, so the root volume needs room for two
-([details](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#the-worker-instance)).
+([details](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#the-worker-instance)).
 
 #### The worker follows a rebased or deleted GitHub branch
 
@@ -1431,7 +1709,7 @@ changes the template too (the fallback bundle's key and hash), so only the contr
 bundle-only roll is safe.
 
 **To adopt.** Parameter mode: gate bundle-only rolls on the contract
-([recipe](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#rolling-the-worker-from-ci)). The gate refuses a stack without the
+([recipe](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#rolling-the-worker-from-ci)). The gate refuses a stack without the
 `WorkerContract` output, so `cdk deploy` the template once, which adds it. A hand-installed unit
 copies its `Environment=CANOPYCMS_WORKER_CONTRACT=` line from `worker/canopy-worker.service`.
 
@@ -1448,8 +1726,8 @@ units from the bundle's contract: 2 gets the split, an older bundle the single u
 template, then roll the bundle; on an older template it stops with `template too old for this
 bundle`. Inspect EFS only through `sudo /opt/canopy-worker/canopy-inspect <command>`, never from a root shell. A hand install
 takes `worker/`'s three units and `gateway.env.example`
-([steps](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#installing-the-units-by-hand)). After the first deploy, run the
-[checklist](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#first-deploy-checklist).
+([steps](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#installing-the-units-by-hand)). After the first deploy, run the
+[checklist](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#first-deploy-checklist).
 
 #### `canopycms-cdk`: `CanopyCmsService.attachTo`, and editor response headers — **behaviour change if you frame the CMS**
 
@@ -1460,7 +1738,7 @@ response headers policy. `CanopyCmsDistribution` sends the same headers: `frame-
 `X-Frame-Options: SAMEORIGIN`, `nosniff`, HSTS and `X-Robots-Tag: noindex`. Unless your app sends
 its own framing headers, no other origin can frame the editor or any page the CMS domain serves. Every such page is
 marked `noindex`. The editor's default preview is same-origin and unaffected. See
-[Serving the editor from a distribution you already own](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#serving-the-editor-from-a-distribution-you-already-own).
+[Serving the editor from a distribution you already own](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#serving-the-editor-from-a-distribution-you-already-own).
 
 **To adopt.** If you wired the Function URL into your own distribution by hand, delete those
 behaviors and call `attachTo`, passing your CMS build's `assetPrefix` as `editorAssetPrefix` and a
@@ -1636,7 +1914,7 @@ one the exclusions leave out. A throw or any other return is logged and treated
 **To adopt.** If your site's routes, sitemap or bylines decide that some entries have no page,
 apply the same rule here, for example `referenceLink: (target, { body }) =>
 !body?.trim() ? false : undefined` in `defineAIContentConfig` from `canopycms/ai`. See
-[AI Content Configuration](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#ai-content-configuration).
+[AI Content Configuration](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#ai-content-configuration).
 
 **Now deletable.** A `fieldTransforms` entry that re-renders a reference field only to drop or
 change its link.
@@ -1711,7 +1989,7 @@ _First in int.115._
 entry the base branch also changed, the "updated on the base branch" notice and the branch's
 conflict count now stay until the branch merges, so a reviewer still sees which entries replaced a
 base change. They used to clear on the next sync, about five minutes later. README's new [Drafts
-and Unpublishing](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#drafts-and-unpublishing) section covers long-lived branches and
+and Unpublishing](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#drafts-and-unpublishing) section covers long-lived branches and
 unpublishing.
 
 #### The editor calls the content drawer "All content"
@@ -2023,7 +2301,7 @@ editor carries an unsaved draft of a stamped entry onto its stamped version.
 The flag is refused off a top-level `datetime`, on `list: true`, and with `required: true`.
 
 **To adopt.** Add `stampOnPublish: true` to the date field your site sorts or labels by, such as
-`{ name: 'publishedAt', type: 'datetime', stampOnPublish: true }`. See [Stamping a publication date](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#stamping-a-publication-date).
+`{ name: 'publishedAt', type: 'datetime', stampOnPublish: true }`. See [Stamping a publication date](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#stamping-a-publication-date).
 
 **Now deletable.** A build step or hook that writes a missing publication date into new entries.
 
@@ -2070,7 +2348,7 @@ preview/form divider is now keyboard-resizable within the same 15–85% the spli
 stored at, and `react-split-pane` is no longer a dependency.
 `EditorPanes`, `EditorPanesProps`, the `PaneLayout` type and the `SPLIT_PERCENT_*` and `DEFAULT_*_SPLIT_PERCENT` constants are
 no longer exported from `canopycms/client`. See
-[Your root layout](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#editor-customization).
+[Your root layout](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#editor-customization).
 
 **To adopt.** Nothing, unless you import `EditorPanes` or those constants: render `CanopyEditor`
 instead, which lays out its own panes. Hiding your site chrome on the editor route is now
@@ -2181,7 +2459,7 @@ never ended. `canopycms-auth-clerk` skips it while the editor is mounted, and ex
 **To adopt.** Nothing for the editor, if your edit page uses `useClerkAuthConfig()` or
 `ClerkSignIn`. If your CMS build renders `<SignIn>`, `UserButton` or `OrganizationSwitcher` on your
 own pages, mount the hook as in
-[Clerk components on your own pages](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/packages/canopycms-auth-clerk/README.md#clerk-components-on-your-own-pages).
+[Clerk components on your own pages](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/packages/canopycms-auth-clerk/README.md#clerk-components-on-your-own-pages).
 Your own Server Actions in the CMS build still 403 behind OAC.
 
 **Now deletable.** Any local patch of `window.__internal_onBeforeSetActive` (or 6.x's
@@ -2222,12 +2500,12 @@ fast naming the ARN, the field and the keys present, never a value.
 **To adopt.** Nothing, unless one of those secrets holds a JSON document: then set the matching
 prop. The scaffolded stack fills them from the repository _variables_
 `CANOPY_GITHUB_TOKEN_SECRET_JSON_FIELD` and `CLERK_SECRET_KEY_SECRET_JSON_FIELD`
-([why the prefix](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#repository-secrets-and-variables)); a stack scaffolded earlier
+([why the prefix](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#repository-secrets-and-variables)); a stack scaffolded earlier
 adds the props to `infrastructure/bin/app.ts` and `infrastructure/lib/cms-stack.ts` and the two `env`
 lines to `.github/workflows/deploy-cms.yml`, or re-runs the generator and diffs. `cdk synth` refuses a `…JsonField` prop without its `…SecretArn`, and an ARN carrying the ECS `:KEY::` suffix
 (also in `secretsArns`). Don't use CDK's `secretValueFromJson`: it resolves the plaintext into the deployed
 resource's configuration, readable by anyone who can describe it. Only `CLERK_SECRET_KEY` goes through Secrets Manager; `CLERK_JWT_KEY` and the publishable
-key are public material ([Security Model](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#security-model)).
+key are public material ([Security Model](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#security-model)).
 
 **Now deletable.** A wrapper that fetches the secret, parses it and re-exports one field into the
 worker's environment, such as a `jq` step in user data or a wrapper entrypoint around
@@ -2239,7 +2517,7 @@ worker's environment, such as a `jq` step in user data or a wrapper entrypoint a
 `githubToken` is not deprecated and stays the documented default; `canopycms` neither depends on
 nor imports `@octokit/auth-app`. Register one App per site, not one shared across repositories:
 anyone holding an App's key can mint a token for any of its installations
-([why](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/ARCHITECTURE.md#why-one-github-app-per-site-not-one-shared-across-an-organisation)).
+([why](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/ARCHITECTURE.md#why-one-github-app-per-site-not-one-shared-across-an-organisation)).
 
 **To adopt with `canopycms-cdk`** (existing stacks need no edit). `CanopyCmsServiceProps` takes
 `githubAppId`, `githubAppInstallationId`, `githubAppPrivateKeySecretArn` and
@@ -2252,7 +2530,7 @@ anyone holding an App's key can mint a token for any of its installations
    `verify` checks an existing installation's permissions: run it, since an App missing a
    permission only shows up later, as `sync-failed`. `create` needs an interactive terminal and
    never edits an existing JSON secret (create one and point the JSON-field prop at it)
-   ([details](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#register-it-with-canopycms-init-github-app)).
+   ([details](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#register-it-with-canopycms-init-github-app)).
 2. Set the three props and **remove `githubTokenSecretArn`** (with its JSON field). A partial set
    of the three is refused at synth, and so is an App alongside a token.
 3. In the generated workflow, store them as `CANOPY_GITHUB_APP_ID`,
@@ -2263,7 +2541,7 @@ anyone holding an App's key can mint a token for any of its installations
 
 The private key is ARN-only; passing the key itself is refused at synth. Its ARN joins the worker's
 IAM policy automatically, so you need not add it to `secretsArns`. See
-[Authenticating as a GitHub App](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#authenticating-as-a-github-app).
+[Authenticating as a GitHub App](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#authenticating-as-a-github-app).
 
 ```bash
 canopycms init-github-app create -- \
@@ -2311,7 +2589,7 @@ downloads the `.pem` from the App's settings page.
 
 **What changed.** The worker re-reads a Secrets Manager secret (the GitHub token or the Clerk secret
 key) when the operation using it fails. Timings, costs and the store-before-revoke order are in
-[Rotating a secret](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#rotating-a-secret).
+[Rotating a secret](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#rotating-a-secret).
 
 **To adopt.** Nothing for credentials from `*_SECRET_ARN`, which is every scaffolded deployment. A
 GitHub App private key is still read only at boot: store the new key, replace the instance, and
@@ -2365,12 +2643,12 @@ also check the bucket policy for its grant.
 5. `withCanopy()` adds sharp's libvips to Next's file tracing (not for a static export) and, on
    Next 16 and later, sets `turbopack: {}` when your config has neither `turbopack` nor your own
    `webpack` and it can read your Next version. A webpack build still fails its image transforms
-   ([Dual Build Support](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#dual-build-support)).
+   ([Dual Build Support](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#dual-build-support)).
 
 **Breaking:** a stack setting `platform` on `fromImageAsset` without `architecture` gets an arm64
 function while `platform` still decides the image, so `Platform.LINUX_AMD64` builds an image the
 function cannot run. A stack setting neither moves to arm64 with a matching image, built under QEMU
-on an x86 host ([Where the image is built](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#where-the-image-is-built)).
+on an x86 host ([Where the image is built](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#where-the-image-is-built)).
 
 **To adopt.**
 
@@ -2399,7 +2677,7 @@ reason; `platform` on `fromImageAsset`; and, with `withCanopy()`, a hand-written
 
 **What changed.** `media.uploadUrl` (s3 adapter; an absolute http(s) URL or a site-relative path)
 replaces the `url` that `beginUpload()` returns, leaving the presign's `fields` untouched, so
-uploads can be same-origin. See [Media Configuration](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#media-configuration) for the
+uploads can be same-origin. See [Media Configuration](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#media-configuration) for the
 CloudFront behavior it expects.
 
 **To adopt.** Optional. Set it from an environment variable: a site-relative value works only where
@@ -2424,7 +2702,7 @@ needs `lazyPublicTransforms: true`) let you pass a deterministically named role,
 bucket's stack computes `arn:aws:iam::<account>:role/<name>` from literals instead of a
 `Fn::GetStackOutput` reference only the CDK CLI resolves. The constructs re-attach
 `AWSLambdaBasicExecutionRole` (and the VPC policy) that `lambda.Function` drops from a role you
-pass. See [Cross-account asset bucket](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#cross-account-asset-bucket).
+pass. See [Cross-account asset bucket](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#cross-account-asset-bucket).
 
 **To adopt.** Optional:
 
@@ -2534,7 +2812,7 @@ public JWKS PEM, used only to verify signatures.
 to variables (Settings → Secrets and variables → Actions → Variables); `bin/app.ts` refuses the
 deploy at synth while it is unset. Check that `bin/app.ts` passes `CLERK_SECRET_KEY` as
 `clerkSecretKeySecretArn` (read by the worker), never in the Lambda's `environment`, unless you keep
-`clerkMiddleware` ([Security Model](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/docs/deploying-to-aws.md#security-model)).
+`clerkMiddleware` ([Security Model](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/docs/deploying-to-aws.md#security-model)).
 
 #### `readByUrlPath` answers only where `listEntries` publishes — **breaking (routing)**
 
@@ -2633,7 +2911,7 @@ basePath: process.env.NEXT_PUBLIC_BASE_PATH,
 Then pass `baseUrl` to `assetUrl` only if Next serves `/assets` (local adapter, `next dev`, S3 with
 no distribution): `assetUrl(image, { width: 960, baseUrl: BASE_PATH })`. Assets on CloudFront via
 `AssetSupport` stay at the distribution root; pass no `baseUrl` (mount table under "Where `/assets`
-is mounted" in [Media Configuration](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#media-configuration)). Two traps:
+is mounted" in [Media Configuration](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#media-configuration)). Two traps:
 
 - Don't pass a deployment `basePath` to `contentStaticParams({ basePath })`; that option filters by
   a nested route prefix and emits zero params, building green.
@@ -2792,7 +3070,7 @@ Under `exactOptionalPropertyTypes: true`, omit keys instead of assigning `undefi
 `withTrailingSlash` and `isAbsoluteUrl` from `canopycms/server`; `defineSeoFieldGroup()` from
 `canopycms`; `generateContentSitemap` and `entryToMetadata` from `canopycms-next`, bound on
 `createNextCanopyContext`'s result. See
-[Sitemap and SEO Metadata](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#sitemap-and-seo-metadata). Every routable entry type is in
+[Sitemap and SEO Metadata](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#sitemap-and-seo-metadata). Every routable entry type is in
 the sitemap unless `exclude`d or `noindex`; one `noindex` predicate drives both robots metadata and
 sitemap exclusion. `trailingSlash` is never inferred. `lastModified` defaults to `updatedAt`, a
 filesystem mtime. An empty SEO field counts as unset. `siteUrl` must be absolute, colliding URLs are
@@ -2849,7 +3127,7 @@ underscore-prefixed files are skipped.
 
 **What changed.** New scaffolds write `defaultBranchAccess: 'deny'` and
 `defaultPathAccess: { read: 'allow' }`
-([Public read on server deployments](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#public-read-on-server-deployments)).
+([Public read on server deployments](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#public-read-on-server-deployments)).
 
 **To adopt.** An older scaffold's `defaultBranchAccess: 'allow'` is wider than recommended;
 consider `'deny'`. If you deleted `defaultPathAccess: { read: 'allow' }`, anonymous visitors get no content until you
@@ -2902,7 +3180,7 @@ re-checked an entry's type (a `switch` on `meta.entryType` can merge them into o
 **What changed.** `BlockComponentRegistry<Blocks>` (types only, from `canopycms`; `BlockValueOf<Blocks, 'hero'>`
 gives one template's value type) requires exactly
 one component per block template name when written as an object literal. See
-[Block Component Registries](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#block-component-registries) and
+[Block Component Registries](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#block-component-registries) and
 `apps/example1/app/components/PostView.tsx`.
 
 ```ts
@@ -2924,7 +3202,7 @@ templates against the schema.
 
 **What changed.** Spreading a `const` field array into several schemas, and nesting
 `defineInlineFieldGroup()` inside a block template, are documented
-([Reusable Field Fragments](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#reusable-field-fragments)); `defineFieldFragment()` is an
+([Reusable Field Fragments](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#reusable-field-fragments)); `defineFieldFragment()` is an
 identity helper for them.
 
 ```ts
@@ -2943,7 +3221,7 @@ field by composing from the same `const` field object.
 A block template holding a `reference` field is a shared block; `read()`/`readByUrlPath()` resolve
 it, and listings do with
 [`resolveReferences`](#listings-resolve-references-and-a-resolved-reference-carries-urlpath-and-optionally-its-body-16--breaking-type-level)
-(0.0.64). See [Shared / Referenced Blocks](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#shared--referenced-blocks).
+(0.0.64). See [Shared / Referenced Blocks](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#shared--referenced-blocks).
 
 **Now deletable.** A second `read()` in page code to unwrap a shared block's reference.
 
@@ -2965,7 +3243,7 @@ Not retro-documented, apart from these:
 
 #### The registry is keyed by entry-type name (0.0.42)
 
-**What changed.** `createEntrySchemaRegistry` keys are the entry-type names that `.collection.json` files name in `entry.schema`, and `EntryTypesFromRegistry` derives the typed entry-type map from them. Schema-variable keys (`{ postSchema }`) still work but derive nothing; [README's registry convention](https://github.com/safeinsights/canopycms/blob/b67d39a9a60e1c1d9dd23324c78df06c2295afa8/README.md#convention-why-key-the-registry-by-entry-type-name) says when to keep them.
+**What changed.** `createEntrySchemaRegistry` keys are the entry-type names that `.collection.json` files name in `entry.schema`, and `EntryTypesFromRegistry` derives the typed entry-type map from them. Schema-variable keys (`{ postSchema }`) still work but derive nothing; [README's registry convention](https://github.com/safeinsights/canopycms/blob/b5a1131194aa99a6532f84792caf439f6d358e67/README.md#convention-why-key-the-registry-by-entry-type-name) says when to keep them.
 
 **To adopt.**