Settle the suite-wide fallout of the wave

- The record-settings contract, slug-list, and section-frame tests
  follow the slugs that left the registry (layout children resolve
  their headings from the layout namespace, like production).
- The orphaned settings.sections.<module>.title/description keys leave
  all six locales; the reverse-coverage guard flagged them the moment
  their nav entries stopped existing.
- The operator-cap ledger read fails open on a read error — the
  reservation layer still meters against the same ledger, and a
  transient blip must not take the fallback chain down.
- The reaper queue joins the subsystem surface; its healed count and
  the sweep's nag_dismissed join the job-fact vocabulary.
- The intake-event contract fixture carries the full row the resource
  now declares; the workouts empty-state test asserts the
  source-neutral cue; the persister poll gates on rendered content
  first.

src/__tests__/record-settings-contract.test.ts

@@ -67,7 +67,12 @@ describe("record settings contract", () => {
       guardianWritable: false,
     });
     expect(classifySettingsDestination("ai").kind).toBe("unavailable");
-    expect(classifySettingsDestination("dashboard").kind).toBe(
+    // v1.37.19 — "dashboard" left SETTINGS_SECTION_SLUGS (its URL is
+    // owned by a permanent redirect to /settings/layout/dashboard), so an
+    // unknown destination falls closed to plain unavailable; "layout" is
+    // the surviving adult-shared-unavailable representative.
+    expect(classifySettingsDestination("dashboard").kind).toBe("unavailable");
+    expect(classifySettingsDestination("layout").kind).toBe(
       "adult-shared-unavailable",
     );
     expect(isGuardianSettingsWriteAllowed("account")).toBe(true);