fix(metadata-protocol): refusals and hints state each decision in words instead of a tracker number (stage 2, author-visible)

The thrown refusals, the stored-type preflight and revert refusals, and the
schedule-flow organization hint no longer send the reader to a tracker number:
each says what was decided, or loses only the citation where the sentence
already said it. Text only: no code, field, status or export moves. The
prose-id ledger is recomputed with --census-ledger; only metadata-protocol
rows move.

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

Author: claude

packages/metadata-protocol/src/protocol.ts

@@ -10308,7 +10308,7 @@ export class ObjectStackProtocolImplementation implements
                 `'${param}' entry #${badShape + 1} on object '${object}' is not a field name.`
                 + (retiredForm
                     ? ' The nested-select object form `{ field, fields, alias }` was removed in '
-                      + '@objectstack/spec 17 (#4196) — no engine or driver ever read it.'
+                      + '@objectstack/spec 17 — no engine or driver ever read it.'
                     : '')
                 // [#7532] The dotted-path half of this prescription is GONE.
                 // It pointed at a spelling this same gate now refuses — and
@@ -13320,7 +13320,7 @@ export class ObjectStackProtocolImplementation implements
         this.assertObjectRegistered(request.object); // [#3770]
         const engineInsertMany = (this.engine as any)?.insertMany;
         if (typeof engineInsertMany !== 'function') {
-            throw new Error('insertManyData requires an engine with insertMany (framework#3172)');
+            throw new Error('insertManyData requires an engine with insertMany: the partial-success batch insert, which reports an outcome per row so a bad row neither fails the whole batch nor makes the good rows run their beforeInsert hooks twice');
         }
         // [#5503/#14147] The engine's events are collected WHOLE and merged —
         // the same handling `createManyData` gives them, and for the reason
@@ -14077,7 +14077,7 @@ export class ObjectStackProtocolImplementation implements
             + `overlay"). An operator may set OS_METADATA_WRITABLE=${singular} to grant a runtime escape hatch, `
             + `but note the row still will not survive a restart — the hatch unlocks the write, not the read, `
             + `and boot logs every such row it walks past. `
-            + `See docs/adr/0005-metadata-customization-overlay.md and #6190.`
+            + `See docs/adr/0005-metadata-customization-overlay.md.`
         );
         err.code = 'NOT_OVERRIDABLE';
         err.status = 403;
@@ -15043,7 +15043,7 @@ export class ObjectStackProtocolImplementation implements
                 + `the non-canonical metadata type '${type}' (canonical: '${canonicalType}'). The registry `
                 + `holds exactly one plain key per (type, name) and every reader addresses it through the `
                 + `'/meta' boundary, which folds — an entry minted under '${type}' is a second namespace no `
-                + `canonical read, listing or declaration lookup can reach (#4432). Fold the type at the `
+                + `canonical read, listing or declaration lookup can reach. Fold the type at the `
                 + `producer (canonicalMetaType), not here; see this method's header for why the mint door `
                 + `refuses instead of folding.`,
             );
@@ -15818,8 +15818,8 @@ export class ObjectStackProtocolImplementation implements
         if (await this.metaTypeNamespaceExists(unrecognised.type)) return;
         const err = new Error(
             `'${unrecognised.type}' is not a metadata type. The platform declares `
-            + `no such type, and since #8586 retired 'additionalTypes' a plugin cannot declare one `
-            + `either — so this write would mint a sys_metadata namespace under `
+            + `no such type, and a plugin cannot declare one either: 'additionalTypes' was retired because `
+            + `nothing ever read it — so this write would mint a sys_metadata namespace under `
             + `type='${unrecognised.type}' that nothing reads and nothing serves. Address a real `
             + `metadata type; GET /api/v1/meta/types lists the ones this deployment carries.`,
         );
@@ -18667,11 +18667,11 @@ export class ObjectStackProtocolImplementation implements
                 error: `Draft '${d.type}/${d.name}' is stored under the non-canonical metadata type `
                     + `'${d.type}'; the canonical type for this item is '${canonical}'. Publishing it would `
                     + `mint an ACTIVE row in a second namespace that no registry read and no compliance `
-                    + `query on '${canonical}' can see (#7894 closed this namespace at the '/meta' URL door; `
+                    + `query on '${canonical}' can see (the '/meta' URL door now folds a type to its canonical spelling before it writes; `
                     + `this row predates that). Re-author the item under '${canonical}' `
                     + `(PUT /meta/${canonical}/${d.name}) and drop the '${d.type}' row. Note that `
                     + `POST /meta/_migrate-stored does NOT rewrite a stored type spelling — it canonicalizes `
-                    + `bodies, and reports rows of this class as 'skipped' with that same reason (#8957).`,
+                    + `bodies, and reports rows of this class as 'skipped' with that same reason.`,
                 code: 'STORED_TYPE_NOT_CANONICAL',
                 organizationId: d.organizationId ?? null,
             });
@@ -20873,13 +20873,13 @@ export class ObjectStackProtocolImplementation implements
                         + `metadata type '${it.type}'; the canonical type for this item is `
                         + `'${canonical}'. Restoring it would write the pre-commit body back into a `
                         + `second namespace that no registry read and no compliance query on `
-                        + `'${canonical}' can see (#7894 closed this namespace at the '/meta' URL `
-                        + `door; this row predates that), and the registry refuses to serve it `
+                        + `'${canonical}' can see (the '/meta' URL door now folds a type to its canonical `
+                        + `spelling before it writes; this row predates that), and the registry refuses to serve it `
                         + `(REGISTRY_TYPE_NOT_CANONICAL), so the restored body would reach no reader. `
                         + `Re-author the item under '${canonical}' (PUT /meta/${canonical}/${it.name}) `
                         + `and drop the '${it.type}' row. Note that POST /meta/_migrate-stored does NOT `
                         + `rewrite a stored type spelling — it canonicalizes bodies, and reports rows `
-                        + `of this class as 'skipped' with that same reason (#8957).`,
+                        + `of this class as 'skipped' with that same reason.`,
                     code: 'STORED_TYPE_NOT_CANONICAL',
                 });
                 continue;

packages/metadata-protocol/src/runtime-authoring-gate.ts

@@ -329,7 +329,8 @@ export function findPlatformScheduleOrgGaps(args: {
             hint:
                 `Declare the owning organization on this node: `
                 + `config.fields.${ORGANIZATION_FIELD}. An author-supplied value always wins over the `
-                + `engine's fill (#6153), so this is the one place the answer can come from for a `
+                + `engine's fill, and the engine fills only an organization the run resolved — so this is `
+                + `the one place the answer can come from for a `
                 + `scheduled run. A NULL ${ORGANIZATION_FIELD} is not merely untidy: an `
                 + `(${ORGANIZATION_FIELD}, …) unique index does not constrain across NULL and org-scoped `
                 + `queries never see the row. Alternatively, publish this flow into an organization, or `

scripts/doc-authoring-prose-id.baseline.json

@@ -324,19 +324,10 @@
  },
  "packages/metadata-protocol/src/protocol.ts": {
   "#10377": 1,
-  "#3172": 1,
   "#3770": 1,
-  "#4196": 1,
-  "#4432": 1,
-  "#6190": 3,
+  "#6190": 2,
   "#6992": 1,
-  "#7894": 2,
-  "#8502": 1,
-  "#8586": 1,
-  "#8957": 2
- },
- "packages/metadata-protocol/src/runtime-authoring-gate.ts": {
-  "#6153": 1
+  "#8502": 1
  },
  "packages/metadata-protocol/src/sys-metadata-repository.ts": {
   "#4867": 1