chore(spec): cite the sibling retirement by its D3 id, not a tracker number that no longer resolves

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

Author: claude

packages/spec/src/migrations/entries/retired-keys/18.api__RestApiConfig__responseFormat.ts

@@ -9,8 +9,9 @@
 // `retiredKey()` tombstone (a bare deletion would strip the key silently), the
 // ledger row stays `dead` with a REMOVED note, and there is no D2 conversion: a
 // `RestServerConfig` is plugin TS configuration, never a stack collection member
-// or a `sys_metadata` row — the `api/RestServerConfig:openApi31` and #14691
-// precedent. D3 semantic entry `rest-api-config-dead-keys-retired`. Registered
+// or a `sys_metadata` row — the `api/RestServerConfig:openApi31` precedent, and
+// the `rest-server-config-dead-keys-retired` one on the four sibling
+// sub-objects. D3 semantic entry `rest-api-config-dead-keys-retired`. Registered
 // under 18 for the launch-window reason its neighbours state.
 //
 // `responseFormat` is retired WHOLE — `envelope`, `includeMetadata` and

packages/spec/src/migrations/entries/semantic/18.rest-api-config-dead-keys-retired.ts

@@ -8,8 +8,9 @@ import type { SemanticMigration } from '../../types.js';
 // `api/RestApiConfig:responseFormat` and `api/RestApiConfig:documentation.enabled`
 // — four ledger keys, since `responseFormat` retires whole with its three
 // members. No D2 conversion: a `RestServerConfig` is plugin TS configuration,
-// never a stack collection member or a stored row (the #14691 precedent on the
-// four sibling sub-objects), so this entry is where the prescription reaches
+// never a stack collection member or a stored row (the
+// `rest-server-config-dead-keys-retired` precedent on the four sibling
+// sub-objects), so this entry is where the prescription reaches
 // `os migrate meta`, the upgrade guide and `spec-changes.json`.
 export const entry: SemanticMigration = {
   id: 'rest-api-config-dead-keys-retired',

packages/spec/src/migrations/registry.ts

@@ -13308,8 +13308,9 @@ const step18: MigrationStep = {
     // `api/RestApiConfig:responseFormat` and `api/RestApiConfig:documentation.enabled`
     // — four ledger keys, since `responseFormat` retires whole with its three
     // members. No D2 conversion: a `RestServerConfig` is plugin TS configuration,
-    // never a stack collection member or a stored row (the #14691 precedent on the
-    // four sibling sub-objects), so this entry is where the prescription reaches
+    // never a stack collection member or a stored row (the
+    // `rest-server-config-dead-keys-retired` precedent on the four sibling
+    // sub-objects), so this entry is where the prescription reaches
     // `os migrate meta`, the upgrade guide and `spec-changes.json`.
     {
       id: 'rest-api-config-dead-keys-retired',
@@ -16979,8 +16980,9 @@ export const RETIRED_KEYS_BY_MAJOR: Readonly<Record<number, readonly string[]>>
     // `retiredKey()` tombstone (a bare deletion would strip the key silently), the
     // ledger row stays `dead` with a REMOVED note, and there is no D2 conversion: a
     // `RestServerConfig` is plugin TS configuration, never a stack collection member
-    // or a `sys_metadata` row — the `api/RestServerConfig:openApi31` and #14691
-    // precedent. D3 semantic entry `rest-api-config-dead-keys-retired`. Registered
+    // or a `sys_metadata` row — the `api/RestServerConfig:openApi31` precedent, and
+    // the `rest-server-config-dead-keys-retired` one on the four sibling
+    // sub-objects. D3 semantic entry `rest-api-config-dead-keys-retired`. Registered
     // under 18 for the launch-window reason its neighbours state.
     //
     // `responseFormat` is retired WHOLE — `envelope`, `includeMetadata` and