wip(spec): the absorbed rename's registry entry and the timeout fixture note name the resilience removal

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QcAS3qiYYZNezaxZxaUdMV

Author: claude

packages/spec/src/conversions/registry.ts

@@ -9190,8 +9190,9 @@ const connectorConnectionTimeoutMsRemoved: MetadataConversion = {
       connectors: [
         // Minimal by the §3 disjointness contract: the retired key and nothing
         // else this major's other `connectors[]` entries also walk
-        // (`errorMapping`, `health.circuitBreaker.monitoringWindow`,
-        // `triggers[].interval`), so every notice here is attributable to this id.
+        // (`errorMapping`, `health` / `status` / `webhooks` — `health` once as
+        // `health.circuitBreaker.monitoringWindow` — and `triggers[].interval`),
+        // so every notice here is attributable to this id.
         { name: 'ledger_api', label: 'Ledger API', type: 'api', connectionTimeoutMs: 15000 },
         // A connector that never authored the key keeps its identity — the
         // copy-on-write contract `stripKeys` / `mapCollection` are built on.

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

@@ -13,4 +13,14 @@
 // the D2 conversion `connector-health-and-trigger-durations-unit-in-key`:
 // `connectors:` is a stack collection and a published connector row lands whole
 // in `sys_metadata`, so the chain has a seam that sees it.
+//
+// ⚠️ Superseded in the same unreleased step: the whole `health` block was then
+// retired under ADR-0049 (the connector resilience family), so
+// `integration/CircuitBreakerConfig` left whole (`RETIRED_DEFS_BY_MAJOR[18]`) and
+// this tombstone left with it. The row STAYS — the whole-def removal steady
+// state gate (b3) exempts — because it is still the record that the bare
+// `monitoringWindow` spelling was retired. The rename's breaker half was absorbed
+// by `connector-resilience-keys-removed`, which strips the block an author
+// holding either spelling still carries; the `health` tombstone's prescription
+// names both spellings.
 export const entry = 'integration/CircuitBreakerConfig:monitoringWindow';

packages/spec/src/migrations/registry.ts

@@ -16549,6 +16549,16 @@ export const RETIRED_KEYS_BY_MAJOR: Readonly<Record<number, readonly string[]>>
     // the D2 conversion `connector-health-and-trigger-durations-unit-in-key`:
     // `connectors:` is a stack collection and a published connector row lands whole
     // in `sys_metadata`, so the chain has a seam that sees it.
+    //
+    // ⚠️ Superseded in the same unreleased step: the whole `health` block was then
+    // retired under ADR-0049 (the connector resilience family), so
+    // `integration/CircuitBreakerConfig` left whole (`RETIRED_DEFS_BY_MAJOR[18]`) and
+    // this tombstone left with it. The row STAYS — the whole-def removal steady
+    // state gate (b3) exempts — because it is still the record that the bare
+    // `monitoringWindow` spelling was retired. The rename's breaker half was absorbed
+    // by `connector-resilience-keys-removed`, which strips the block an author
+    // holding either spelling still carries; the `health` tombstone's prescription
+    // names both spellings.
     'integration/CircuitBreakerConfig:monitoringWindow',
     // ADR-0049 enforce-or-remove on `ConnectorSchema.connectionTimeoutMs`
     // (maintainer ruling 2026-09-22, letter A — the narrower SECOND decision this