We need to establish a strategy for resolving data inconsistencies between HBI and Kessel Inventory that occur "X months" post-launch. At this stage, the dedicated Debezium "Migration Connector" and topic will likely have been decommissioned. We need a plan to handle two specific recovery scenarios:

1. Partial/Surgical Resync: Re-replicating specific records identified during auditing as "out of sync." This could happen either via outbox or incremental snapshot via the connector.

1. Full Resync: Re-replicating the entire dataset in the event of catastrophic data loss or corruption. Again via outbox or snapshots and data cleanup.

For Resyncs: Evaluate whether HBI should manually publish host records to the outbox table. This would allow us to leverage the always-running Outbox Connector for full/surgical fixes without needing to redeploy migration infrastructure.