spec: the rename prescription carries no version word; a history comment keeps its era's name

- The allowOrgOverride tombstone's prescription reads "was renamed to
  `allowEnvironmentOverlay` (ADR-0131 D6)": the changeset ships this as
  major on the 18.0.0-next line, so naming an npm major there contradicts
  one of the two. The TSDoc's "in 18" names the protocol major and stays.
  The refusal pin and the generated reference follow.
- sys-metadata-repository.ts: the comment recording commit ee58392
  names the key that commit rolled back, `allowOrgOverride`.

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

Author: claude

content/docs/references/kernel/metadata-plugin.mdx

@@ -269,7 +269,7 @@ const result = MetadataBulkResultSchema.parse(data);
 | **filePatterns** | `string[]` | ✅ | Glob patterns to discover files of this type |
 | **supportsOverlay** | `boolean` | optional (default: `true`) | Whether a stored overlay row of an item a managed package ships may be removed through the ordinary delete door without the type's environment-overlay permission: the removal removes no managed definition, and changes what is served for permission alone; it opens no save and it decides no read |
 | **allowEnvironmentOverlay** | `boolean` | optional (default: `false`) | Whether an environment may overlay an item of this type that a managed package ships (ADR-0131 D6 regime O). Decides the save door, the managed-content seal on write and on read, and Studio's write gate; the OS_METADATA_WRITABLE hatch does not reach a managed item. Default false. |
-| **allowOrgOverride** | `never` | optional | [REMOVED] `MetadataTypeRegistryEntry.allowOrgOverride` was renamed to `allowEnvironmentOverlay` in @objectstack/spec 17 (ADR-0131 D6) — the per-organization overlay axis was retired, and the key now names the one scope it governs: whether an environment may overlay an item of this type that a managed package ships. Rename the key to `allowEnvironmentOverlay`; the value is unchanged. |
+| **allowOrgOverride** | `never` | optional | [REMOVED] `MetadataTypeRegistryEntry.allowOrgOverride` was renamed to `allowEnvironmentOverlay` (ADR-0131 D6) — the per-organization overlay axis was retired, and the key now names the one scope it governs: whether an environment may overlay an item of this type that a managed package ships. Rename the key to `allowEnvironmentOverlay`; the value is unchanged. |
 | **allowRuntimeCreate** | `boolean` | optional (default: `true`) | Allow runtime creation via API |
 | **supportsVersioning** | `boolean` | optional (default: `false`) | Whether version history is tracked |
 | **executionPinned** | `boolean` | optional (default: `false`) | Transaction rows reference a specific version_hash; history GC is disabled and getByHash() MUST resolve old hashes (ADR-0009) |

packages/metadata-protocol/src/sys-metadata-repository.ts

@@ -2031,7 +2031,7 @@ export class SysMetadataRepository implements MetadataRepository {
    * kernel (`environmentId === undefined`) skips the protocol's own two-tier
    * block entirely and lands here instead. That made it the second of the two
    * refusal points #6960 measured: on an environment carrying an overlay row
-   * authored BEFORE commit ee58392e1 rolled `allowEnvironmentOverlay` back to
+   * authored BEFORE commit ee58392e1 rolled `allowOrgOverride` back to
    * `false`, the row kept merging overlay-wins at read time while the ordinary
    * "Reset to package default" answered 403 — the removal reachable only
    * through `OS_METADATA_WRITABLE`. Maintainer ruling, 2026-08-10: the delete

packages/spec/src/kernel/metadata-plugin.zod.ts

@@ -314,8 +314,8 @@ const MetadataTypeRegistryEntryBaseSchema = z.object({
    * `undefined`, which closes every type. Read `allowEnvironmentOverlay`.
    */
   allowOrgOverride: retiredKey(
-    '`MetadataTypeRegistryEntry.allowOrgOverride` was renamed to `allowEnvironmentOverlay` in '
-    + '@objectstack/spec 17 (ADR-0131 D6) — the per-organization overlay axis was retired, and '
+    '`MetadataTypeRegistryEntry.allowOrgOverride` was renamed to `allowEnvironmentOverlay` '
+    + '(ADR-0131 D6) — the per-organization overlay axis was retired, and '
     + 'the key now names the one scope it governs: whether an environment may overlay an item '
     + 'of this type that a managed package ships. Rename the key to `allowEnvironmentOverlay`; '
     + 'the value is unchanged.',

packages/spec/src/kernel/metadata-type-registry-allow-org-override-retirement.test.ts

@@ -56,7 +56,7 @@ describe('MetadataTypeRegistryEntry.allowOrgOverride is renamed to allowEnvironm
     expect(issue!.path).toEqual(['allowOrgOverride']);
     // The prescription IS the migration doc for whoever hits it.
     expect(issue!.message).toMatch(
-      /`MetadataTypeRegistryEntry\.allowOrgOverride` was renamed to `allowEnvironmentOverlay` in @objectstack\/spec 17/s,
+      /`MetadataTypeRegistryEntry\.allowOrgOverride` was renamed to `allowEnvironmentOverlay` \(ADR-0131 D6\)/s,
     );
     expect(issue!.message).toMatch(/Rename the key to `allowEnvironmentOverlay`; the value is unchanged/s);
     // `false` is refused exactly like `true`: the key is gone, not one value of it.