change-data-capture-operationslisted

# Change Data Capture Operations Preserve a defensible chain from source commits through durable connector progress to visible sink state. A task marked RUNNING, a saved offset and a completed snapshot each prove different things. ## Establish the recovery contract Use existing evidence before requesting more. Record only what changes the decision: - Source engine/version, topology and failover manager; Debezium connector build and decoder; Kafka Connect distributed/standalone, Debezium Server, Engine, or another hosting runtime. - Effective connector identity, source database, captured tables, keys/replica identity, transformations, snapshot mode and signaling configuration. Identify any recent DDL or filter changes. - Durable source offsets, snapshot progress, source log availability, PostgreSQL slot/publication or MySQL schema history, and their storage/backup owners. Capture positions and timestamps together. - Sink purpose: reconstruct current state or preserve every transition; accepted duplicate/loss windows, delete handling, side effects, recovery time and retention budget. The references use Debezium **3.3.2.Final**, PostgreSQL **17** and MySQL **8.4** as concrete evidence baselines, not upgrade requirements. Inspect deployed image/plugin/JDK and runtime compatibility before suggesting properties. Connector embedding changes state ownership; never assume an Engine or Flink source stores offsets in Kafka Connect topics. [Debezium state storage](https://de