# Deferred Items — Phase 24 (AWS Route 53 DNS Sync)

Out-of-scope discoveries logged during execution. Not fixed per the scope
boundary rule (only auto-fix issues directly caused by the current task's
changes).

## Plan 24-01

- **`lib/services/analyzer/itglue-search.test.ts`** — 2 pre-existing test
  failures (`returns capped, redacted doc snippets when the org is found`,
  `tolerates per-call failures (configurations errors, flex still returns)`)
  surfaced by `npm test` (full suite) while verifying Task 2. Neither
  `itglue-search.ts` nor its test file were touched by this plan (git status
  confirms zero changes to either path from Task 1 or Task 2). Unrelated to
  the Route 53 factory/schema work in this plan — not fixed, logged here for
  visibility.

## Plan 24-03

- Same 2 pre-existing `lib/services/analyzer/itglue-search.test.ts` failures
  re-surfaced by `npm test` (full suite) while verifying Task 2's
  `route53-write-persistence.ts`. Neither `itglue-search.ts` nor its test
  file were touched by this plan. Out of scope per the scope boundary rule —
  not fixed.

## Plan 24-05

- Same 2 pre-existing `lib/services/analyzer/itglue-search.test.ts` failures
  re-surfaced by `npm test` (full suite) while verifying Task 3. Neither
  `itglue-search.ts` nor its test file were touched by this plan. Out of
  scope per the scope boundary rule — not fixed.

## Plan 24-07 (checkpoint observation)

- **`/admin/integrations` page load is slow**, observed by the developer
  during checkpoint step 9 (toggling `route53` off/on). Confirmed NOT
  specific to the Route 53 row/toggle — the developer reported the whole
  page feels slow regardless of Route 53. `checkRoute53()`'s own live checks
  (AWS `ListHostedZonesCommand` + D-12 NS-delegation comparison, bounded to
  5 concurrent workers with a 5s-per-zone DNS timeout) are inherently
  bounded to a few seconds at most for the ~3 zones in this account, so this
  plan's code is not the source. Likely another pre-existing integration's
  `liveCheck()` probe lacking a tight timeout (health checks fan out via
  `Promise.all` across every configured integration — one slow/hanging
  probe drags down the whole aggregate). Not investigated further or fixed
  — pre-existing, out of scope for Phase 24.
