wulf-pulse/.planning/phases/24-aws-route-53-dns-sync-track-changes-crud-operations-full-aud/deferred-items.md
lorentz 8b5e926bb1 feat(24-03): add Route 53 audit lifecycle and pulse_crud history persistence
- createPendingAuditLog/markAuditCommitted/markAuditFailed implement the pending -> committed/failed lifecycle (D-07, SC-3); markAuditFailed always sanitizes via sanitizeAwsError
- insertPulseCrudHistory writes 'pulse_crud' history rows, documented as callable only after a committed write
- upsertMirrorRecord/softDeleteMirrorRecord/loadMirrorRecord manage the route53_records mirror; mirror writes are best-effort and soft-delete only (D-08), audit/history writes are not best-effort
- log same pre-existing itglue-search.test.ts failures (unrelated, out of scope) in deferred-items.md
2026-08-05 20:22:24 -04:00

1.1 KiB

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.