[bmfmancini]

Summary

Incoming cleanup could delete unarchived events, local archival could duplicate events after interruption, and partition recovery and retention could perform unsafe or ineffective maintenance after downtime.

• Preserve incoming events regardless of age, retry crash-stranded rows, and acknowledge only identities stored in history or the durable remote outbox. Rows missing host/program references remain queued.
• Make transfers transactional, lock overlapping incoming slices, and skip existing source identities on retry.
• Defer automatic overflow reorganization above 100,000 estimated rows or 128 MiB, or when size metadata is unavailable. Report the reason through existing maintenance health and preserve the safety partition.
• Expire partitions using actual UTC upper boundaries rather than partition count. Support epoch and legacy TO_DAYS layouts and retain partitions that span the cutoff.
• Add unit/database regression coverage, run the database checks in CI, and document recovery behavior.

Partially addresses #317; other design and hardening items remain open. This branch contains one new commit on current develop, excluding the history already squash-merged through #418.

Validation

• 503 Pest tests passed on the PR branch.
• 100% measured changed-line coverage (87/87 lines).
• 44 checks passed against disposable MariaDB while implementing this commit, including connection interruption, commit/deletion failure, overlapping transfer attempts, Aria retries, populated overflow deferral, and sparse retention layouts.
• PHP syntax, whitespace, and translation-template checks passed.

Limits

Full atomic recovery across database/host crashes requires InnoDB; Aria retries are deduplicated. Overflow statistics are estimates and do not impose an ALTER execution-time limit. Mixed-age partitions retain older rows until the entire partition expires. Existing duplicate history is not removed. No deployment was performed.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE