chore(spec): regenerate the migration registry and the schemaless-node-config reference after the ruling C prose

`gen:migration-registry` concatenates the edited D3 entry into
`registry.ts`'s semantic:18 region; `build && gen:docs` re-renders the
`mode` describe. `check:generated`: all 15 artifacts up to date on the
regenerated tree.

Claude-Session: https://claude.ai/code/session_01ARcDurZ5j34RdqsGgc4jgH
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

content/docs/references/automation/schemaless-node-config.mdx

@@ -143,7 +143,7 @@ const result = DecisionConditionSchema.parse(data);
 | Property | Type | Required | Description |
 | :--- | :--- | :--- | :--- |
 | **conditions** | `{ label: string; expression: string }[]` | optional | Ordered decision branches (first true expression wins; omit to branch purely on edge conditions) |
-| **mode** | `Enum<'exclusive' \| 'inclusive'>` | optional | Declares how many out-edges an edge-branched decision takes when more than one out-edge condition holds: 'exclusive' = only the first, in the order the edges are declared (what an omitted mode means; the siblings after it are not evaluated and record a skipped step); 'inclusive' = every one that holds, one after another. When none holds the isDefault edge runs either way. Refused beside a non-empty conditions list, which is first-match on its own: delete mode there, or move the branches onto the out-edges, delete conditions, and keep mode. Flows written while every true branch ran keep that behaviour through the os migrate meta --from 17 conversion, which writes mode: inclusive onto every edge-branched decision with two or more conditioned out-edges. |
+| **mode** | `Enum<'exclusive' \| 'inclusive'>` | optional | Declares how many out-edges an edge-branched decision takes when more than one out-edge condition holds: 'exclusive' = only the first, in the order the edges are declared (what an omitted mode means; the siblings after it are not evaluated and record a skipped step); 'inclusive' = every one that holds, one after another. When none holds the isDefault edge runs either way. Refused beside a non-empty conditions list, which is first-match on its own: delete mode there, or move the branches onto the out-edges, delete conditions, and keep mode. Authored sources written while every true branch ran keep that behaviour through the os migrate meta --from 17 conversion, which writes mode: inclusive onto every edge-branched decision with two or more conditioned out-edges; a flow stored in sys_metadata is not rewritten and takes the first-match reading on upgrade (os migrate meta --stored lists those decisions). |
 
 ### Nested Shape: `DecisionConfig.conditions[number]`
 

packages/spec/src/migrations/registry.ts

@@ -10459,11 +10459,17 @@ const step18: MigrationStep = {
         + 'old behaviour was the bug), so the mechanical edit list the chain replay prints is '
         + 'where that judgment is made, node by node. And the conversion replays ONLY there: it is a '
         + 'default flip, so the authoring funnel never rewrites a source written against the '
-        + 'new contract, the automation engine\'s flow rehydration seam refuses it by id (a '
-        + 'code-shipped flow, a REST body and a Studio save all arrive there undated), and the '
-        + 'stored-row pass (`os migrate meta --stored`) canonicalizes through that same seam — so '
-        + 'a decision saved from the Studio BEFORE this release, with two or more conditioned '
-        + 'out-edges and no `mode`, now runs first-match and is rewritten by nothing.',
+        + 'new contract, and the automation engine\'s flow rehydration seam and the '
+        + 'artifact-ingestion door both refuse it by id (a code-shipped flow, a REST body, a Studio '
+        + 'save and a scaffolded artifact all arrive undated). BREAKING for stored rows, by '
+        + 'maintainer ruling: the promise that a flow keeps its behaviour is kept by authored '
+        + 'sources and built artifacts only. A decision stored in `sys_metadata` '
+        + 'with no `conditions` list, no `mode` and two or more conditioned out-edges takes the new '
+        + 'meaning on upgrade — it evaluates first-match — and nothing rewrites the row: no '
+        + 'stored-row migration, no cutoff, no read-path completion, because nothing about a stored '
+        + 'row says it was saved before the flip. The one-line fix, for a stored node that meant '
+        + 'every branch, is `mode: \'inclusive\'`; `os migrate meta --stored` lists every such node, '
+        + 'report only, so an operator can review the candidates before and after the upgrade.',
       acceptanceCriteria:
         'Review every `flow-decision-mode-inclusive-explicit` line the chain replay lists for '
         + 'each authored stack: (1) where the two (or more) '
@@ -10475,11 +10481,12 @@ const step18: MigrationStep = {
         + 're-run the flow on a record that satisfied both and confirm exactly one successor '
         + 'ran — the passed-over branch now leaves a `skipped` step in the run log. `os validate` '
         + 'reports `flow-decision-inclusive-overlap` on every decision that keeps the key with '
-        + 'two or more conditioned out-edges, so the review list is the lint output. Then the '
-        + 'half no command reaches: list the `sys_metadata` flow rows of each deployment whose '
-        + 'decision nodes carry two or more conditioned out-edges and no `mode` — the stored '
-        + 'pass reports these rows canonical and rewrites nothing — and declare `mode` on each in '
-        + 'the Studio designer by the same three-way judgment. A decision registering with '
+        + 'two or more conditioned out-edges, so the review list is the lint output. Then each '
+        + 'deployment: `os migrate meta --stored` lists, under `decisionModeReview`, every stored '
+        + 'decision with two or more conditioned out-edges and no `mode` — each one already '
+        + 'evaluates first-match, and the pass writes none of them — so where one of those nodes '
+        + 'meant every branch, declare `mode: \'inclusive\'` on it in the designer; a node '
+        + 'that declares `mode` either way leaves the list. A decision registering with '
         + '`mode` beside a non-empty `conditions` list, or with a `mode` outside '
         + '`\'exclusive\' | \'inclusive\'`, is refused at registration and by `os validate` with the '
         + 'schema\'s own sentence; nothing else about `conditions`-list decisions changes. '