[Table Stream] Changes start/end TSO boundary semantics conflict with documentation #67093

Problem

[Table Stream] Changes start/end TSO boundary semantics conflict with documentation

Minimal reproduction path

Create a ROW Binlog table and produce identifiable events at three ordered change positions. Read two adjacent Changes/Table Stream windows, first [start, end) and then [end, next_end), and compare the boundary events. Verify that the documented boundary contract is applied consistently without losing or duplicating the event at the window boundary.

Expected result

The documented Changes boundary semantics are used consistently across adjacent windows.

Source

This report is a sanitized tracking record for Jira DORIS-28062. Internal hosts, paths, artifacts, build identifiers, and private logs are intentionally omitted.