Add deterministic cleanup contract tests

[jununfly]

This was generated by AI during triage.

Parent

Plan: docs/plans/2026-06-20-rust-hybrid-finalization-cleanup-diagnostics-and-batching.md

What to build

Add focused deterministic tests that lock down unresolved-reference cleanup semantics before any batching or SQL-shape optimization is attempted. The tests should prove that cleanup deletes exactly the rows it already intends to delete and preserves unrelated unresolved references.

This is a semantic guard slice. It should not optimize cleanup yet.

Acceptance criteria

• Tests prove successfully resolved unresolved-reference rows are deleted after persistence.
• Tests prove unresolved references that were not resolved remain present unless existing intentionally-unresolved cleanup behavior removes them.
• Tests cover existing intentionally-unresolved cleanup behavior without changing it.
• Tests cover a chunk or batch boundary large enough to catch SQL parameter/batching regressions.
• No production optimization is required in this slice unless needed only to expose a test seam.

Blocked by

• Split finalization write and cleanup profile diagnostics #326 preferred, so the cleanup counters and diagnostics shape are known before optimization guards are expanded.

[jununfly]

This was generated by AI during triage.

Implemented. Added deterministic cleanup contract coverage for non-batched resolved cleanup preserving unresolved refs, batched cleanup deleting terminal resolved/intentionally-unresolved refs, and rowid chunk boundaries. Targeted test: npx vitest run __tests__/resolution.test.ts -t "unresolved cleanup contract".

[jununfly]

This was generated by AI during triage.

Closing as implemented: deterministic cleanup contract tests cover resolved cleanup, intentionally unresolved cleanup, and rowid chunk boundaries.