[Quality] Correctness prevention: SQL semantics, lifecycle testing and bounded Verus proofs

Recent correctness reports motivate a focused follow-up to the existing quality work: expand the semantic cases tests can reach, strengthen what a passing test establishes, exercise recovery histories, and add small production-used Verus proofs.

This issue tracks proposed quality improvements from the October 22 research review. It does not claim new runtime reproductions, reopen the entire historical Verus roadmap, or make every future proof an immediate release gate.

Work items and recommended order

First: strengthen executable tests

[Quality] Expand DVM generators and regression coverage for PostgreSQL semantic boundaries #1217 — Expand SQL-semantic generators and permanent regressions: composite NULLs, three-valued transitions, exceptional values, evaluation protection, histories and consumer order.
[Quality] Strengthen result oracles, negative controls and changed-data execution witnesses #1218 — Strengthen result observations, expected negative-control failures, changed-data route witnesses and local semantic mutants.
[Quality] Add bounded lifecycle and deterministic concurrency tests for recovery #1219 — Add bounded lifecycle histories and witnessed concurrency/recovery schedules using existing Testcontainers barriers.

Next: deliver proofs in bounded production slices

[Quality][Verus] Verify production predicate visibility and aggregate lifecycle decisions #1220 — First proof pilot: predicate visibility and aggregate lifecycle decisions.
[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 — CDC normalization and observation-safe change elision, including protected consumer windows.
[Quality][Verus] Verify receipt batching, cleanup eligibility and recovery transitions #1222 — Receipt batch completeness, cleanup eligibility and recovery transitions.
[Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 — Restricted join-plan checking with snapshot provenance and expression safety.
[Quality][Verus] Verify bounded row-identity framing and encoding #1224 — Lower-priority row-identity framing and bounded encoding.

This is a prioritization recommendation, not a serial execution requirement. The SQL tests and protocol tests provide runtime evidence for the corresponding proof slices. The source-to-SQL and database boundaries must remain visible even after a proof passes.

Relationship to existing work

bug(dvm): COUNT(composite) drops non-NULL records containing NULL fields #1203, bug(dvm): aggregate FILTER evaluates excluded arguments and raises errors #1204, bug(dvm): HAVING UNKNOWN transition leaves stale group after differential refresh #1205, bug(dvm): deleting numeric Infinity corrupts differential SUM with NaN #1209, bug(cdc): numeric scale changes are lost by equality-based changed_cols mask #1210 and bug(dvm): inner JOIN delta evaluates invalid cross-snapshot predicates #1211 retain ownership of the six reports in BUG: Several correctness issues in differential refresh #1201. Reuse their regressions; these quality issues target broader prevention.
bug: WAL UPDATE-to-NULL retains the old decoded column value #1172–Scheduler pause can report drained while an inline refresh is still active #1187 provide additional lifecycle/capture leads with their existing evidence and confirmation status. A source-supported report is not automatically a reproduced defect.
[Quality] Trustworthy results, recovery, and releases #1090 narrowed the previous quality program; Epic: [Verus] Deliver production-connected verified correctness in safe slices #1056 and its historical proof issues were deferred, not all implemented. The new issues revisit explicitly bounded opportunities prompted by the recent reports.
ci: rebalance PR correctness coverage across component, E2E, and nightly tiers #1188 owns CI allocation work. Current CI already runs execution-backed DVM component tests. Extend those tests for cheap semantic combinations, retain installed-extension coverage for parser/capture/scheduler behavior, and use scheduled jobs for larger products.
Preserve Make public-result and schema comparisons trustworthy #1091–Exercise critical unsafe boundaries under assertions and sanitizers #1098's existing oracles, runtime checks, LSN proof and candidate-binding mechanisms rather than creating parallel evidence infrastructure.

Acceptance criteria (proposed)

R1: Each linked issue records its scoped outcome, actual verification evidence and remaining limits. Correct baselines pass; representative semantic defects are rejected for the intended reason.
R2: Existing regression protection is retained and new checks run in the documented CI tier. Empty selection, skipped paths, fallback masking and infrastructure errors cannot masquerade as semantic coverage.
R3: Every claimed proof uses the production executable implementation, enforced caller assumptions and a reviewed specification. SQL lowering, PostgreSQL semantics, transactions and FFI remain separately qualified where unproved.
R4: Progress and release wording distinguish implemented tests, model proofs, executable proofs and runtime-qualified behavior. Partial delivery can ship without implying whole-extension verification.

Verification — PROPOSED — NOT RUN

Use each work item's focused verification plan and existing CI/release records. Record candidate revision, material configuration, actual runtime path and semantic-control outcomes. Follow repository formatting/linting and SQL-facing testing requirements for implementation changes.

Evidence and limits

Research baseline: 00d21749bc20af8b19940b857fae461e0ccfe471. The linked issues include inspected source locations and primary PostgreSQL/Verus references.

The preparatory review was read-only and sampled; no project code, tests, builds or proofs were executed. Acceptance criteria are proposals, and no separate saved Intentline contract was created.

Current delivery status (2026-11-01)

[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 remains open. PR #1310 merged at 8c9c86b2b7758682127fb0bf07b2f752c8d3ca75 from exact head 2b999b2225642f57ba12d95e444baff50081fada. Exact-head CI run 41315604683 passed after the sensitive E2E shard rerun; S1 qualification run 41315604568 passed. The bounded slice does not complete [Quality][Verus] Verify CDC normalization and observation-safe change elision #1221: PostgreSQL reduction/capture semantics, valid multi-row history enforcement and all protected consumer-window equivalence remain open.
regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198 remains open. PR #1199 is at exact head 9ba4d32c574018a050a3b54f923219d4b7a5fa12, has no review yet, and still requests the sole-owner source review from BaardBouvet.
[Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 and the other completed linked quality issues are closed. Keep this umbrella open until [Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 and its remaining acceptance are complete.

Progress since the merged #1232 integration candidate: #1220 is now closed against its narrow acceptance using the pinned Verus baseline, five rejected executable mutants, packaged PostgreSQL 18 lifecycle cases, and candidate-binding evidence from CI run 40853118868. #1217 and #1222 are also closed. #1218, #1219, #1221, #1223, and #1224 remain open with exact partial evidence and limits recorded in their issue comments; #1198 remains open pending exact-head CI and required sole-owner source review. The umbrella acceptance is still incomplete.

Update: #1219 is now closed after exact-main DVM deep-tier run 40866922269 passed the 10-seed × 12-cycle histories; its 10 traces and 21/21 extended-history suite are retained in the run artifact. #1220, #1217 and #1222 are also closed. #1218, #1221, #1223 and #1224 remain open with their bounded implementation evidence and explicit limits recorded; #1198 remains open on the React 0.108.4 admission gate and pending owner review. The umbrella acceptance remains incomplete.

Update: #1218 is now closed after its bounded acceptance was verified on merged main candidate PR #1232 (run 40853118868). Exact numeric-scale observation, declared negative-control failures and setup rejection, the 12-case trigger/WAL × FULL/DIFFERENTIAL route witness, four SQL semantic mutants, and the installed receipt-prefix control passed; case and candidate evidence are retained in run artifacts.

#1219, #1220, #1217 and #1222 are also closed. #1221, #1223 and #1224 remain open with broader proof/qualification gaps recorded. #1198 remains open: PR #1199 has green exact-head CI, but the separate React 0.108.4 admission audit fails and the required sole-owner review is absent. Umbrella acceptance remains incomplete.

Update: #1218 and #1224 are now closed against merged main candidate PR #1232 after all bounded acceptance criteria passed in exact CI run 40853118868. Their comments link the semantic-control, identity-frame proof, and candidate-binding artifacts and state the remaining scope limits.

#1219, #1220, #1217 and #1222 are also closed. #1221 and #1223 remain open with explicit proof and runtime qualification gaps. #1198 remains open: PR #1199 has green exact-head CI, but its separate React 0.108.4 admission audit fails and the required sole-owner review is absent. Umbrella acceptance remains incomplete.

Current delivery status

[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 now has candidate PR #1286, covering a production-used, verified truncate-barrier compaction guard and its packaged PostgreSQL regression.
[Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 now has candidate PR #1287, covering the verified legacy nested-join correction branch and a packaged runtime witness.
Both PRs are mergeable and their CI is still running; at this update fix(cdc): preserve truncate barriers during compaction (#1221) #1286 has 15 checks passed/10 pending and fix(dvm): correct nested join delta corrections (#1223) #1287 has 12 passed/8 pending, with no failures.
regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198 remains open on its pinned React MDM package-admission failure and pending sole-owner review. No admission list or qualified checksum has been changed.

The new PRs close only their documented bounded slices. #1221 and #1223 remain open for the acceptance recorded in their latest comments, so this umbrella issue remains open as well.

CI update for candidate PRs

fix(cdc): preserve truncate barriers during compaction (#1221) #1286 remains conflict-free. One job, Release evidence runtime controls, failed in the existing test_dvm_failpoint_preserves_last_committed_result_and_recovers: CI observed effective_refresh_mode=NO_DATA where the assertion expected DIFFERENTIAL. Its scenario contains no TRUNCATE and does not exercise the new compaction guard. The same focused test passed twice locally, so a scheduler timing race is suspected but not yet confirmed. The parent workflow still has Unsafe ASan, Sensitive E2E 2/2, and packaged LSN runtime jobs in progress; I will rerun the failed job when the workflow completes.
fix(dvm): correct nested join delta corrections (#1223) #1287 remains failure-free with 14 checks passed and six pending.

No PR has been merged. The #1198 compatibility admission and checksum remain unchanged pending the requested authorization.

CI update for candidate PRs

fix(cdc): preserve truncate barriers during compaction (#1221) #1286 remains conflict-free. Sensitive E2E gate (1/2) failed in the existing test_sum_case_differential_inserts: after the first insert refresh, the stream table held 20 while the defining query returned 50. The exact focused test passed locally, and the complete eight-test SUM CASE file passed on the same candidate. This points to a possible full-shard timing issue, but causality is not established.
The prior Release evidence runtime controls failpoint test also passed twice locally; its CI failure remains unexplained. The packaged checked-LSN runtime job passed. Sensitive E2E gate (2/2) is still running; I will retry only failed jobs once the parent workflow completes.
fix(dvm): correct nested join delta corrections (#1223) #1287 remains failure-free so far. No PR has been merged. regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198’s pinned React MDM admission and checksum remain unchanged pending the requested authorization.

Candidate CI update

fix(cdc): preserve truncate barriers during compaction (#1221) #1286 is green on its failed-job retry (attempt 2), with all exact-head CI checks passing. The PR remains open, conflict-free and mergeable, with BaardBouvet review still requested and no review submitted.
fix(dvm): correct nested join delta corrections (#1223) #1287’s retry confirmed the SUM CASE insert and multi-cycle failures in the full 530-test shard. These tests called refresh_st(), which can return after a lock-busy notice; commit 06f6d584 switches the SUM CASE scenarios to the existing convergence helper. All eight tests pass locally on the updated fix(dvm): correct nested join delta corrections (#1223) #1287 package; new exact-head CI is pending.
No PR has been merged. regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198’s pinned React MDM admission and checksum remain unchanged pending the requested authorization.

Delivery update

PR fix(dvm): correct nested join delta corrections (#1223) #1287 ([Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 bounded join-plan slice) merged as c0b06387 after 17/17 CI jobs passed on the final head.
PR fix(cdc): preserve truncate barriers during compaction (#1221) #1286 ([Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 truncate-barrier slice) merged as 9e07d049 after 26 checks passed and GitHub confirmed a clean merge state.
[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 and [Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 remain open for their broader issue acceptance; the merged PRs delivered scoped slices only.
regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198 remains open and unchanged. Its React MDM package-admission audit is still unresolved, and no admission list or qualified checksum was edited.
Per updated user scope, mutation issues [Testing][Mutation] Pilot two reachable source-level DVM mutants against loaded extension #1289, [Testing][Mutation] Run a bounded cargo-mutants pilot on pure Rust correctness helpers #1290 and [Testing][Mutation] Kill LEFT/FULL JOIN snapshot and match-guard mutants in E2E #1291 were excluded.

Progress update: #1221 now has a bounded follow-up in PR #1293 at candidate 89ea301. The shared compaction eligibility decision is used by base and ST buffers, with local unit/lint/verification and 19 targeted E2E tests passing. GitHub CI is queued; full history and protected-window proof obligations remain open. #1221 and #1223 are still open, and previously excluded mutation issues remain excluded.

Additional scoped progress: #1292 now has a design-only PR, #1295, at candidate 980fe38. It records a source-traced design and preserves the INTERSECT admission guard until implementation and qualification. #1292 remains open; CI is queued. Existing #1221 and #1223 work also remains partial, and the excluded mutation issues remain out of scope.

Updated linked-issue status — 2026-10-31

[Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 is closed for its bounded acceptance after the production-used checker, nested correction work, expression-safety route and installed conformance slices merged. The remaining arbitrary SQL binding and unsupported-shape proof limits are recorded on that issue.
[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 remains open. Candidate PR test: verify signed CDC image event weights #1306 at b21a8e5946ed8892e467c975a88bdb89c17fd86f adds the checked signed image-event coefficients and repeated-image SQL case. Exact-head CI currently has 14 passed, 5 pending and no failures. This does not prove complete history equivalence, PostgreSQL aggregate semantics, transaction/source-incarnation transitions or all protected consumer windows.

The umbrella remains open while #1221's broader acceptance and any other outstanding linked criteria remain unresolved. The mutation issues remain excluded.

Updated linked-issue status — 2026-10-31

[Quality][Verus] Verify a restricted join plan checker with snapshot and expression safety #1223 is closed for its bounded acceptance; commit 47a93f89 is already included in merged PR fix(dvm): fall back for unsafe nested projections #1303.
[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 remains open. PR test: verify signed CDC image event weights #1306 is at 9fc6b3941466810a4b073b5e05dd177f6a85ea87, with signed image-event coefficients, a repeated-image SQL case, and two scheduler E2E stability repairs prompted by exact-head CI. The affected local suites pass (45 tests), and exact-head CI is still running.
regression(dvm): nested inner USING joins break Delta V1 conformance after #1197 #1198 remains open. PR fix(dvm): preserve proven merged keys in chained inner USING joins #1199 has one failing joint-audit: the pinned pg-MDM revision lacks the runtime-epoch API required by the pg-react missing-receipt fixture. Its guard and MDM source remain unchanged.

The umbrella remains open while #1221 and #1198 remain incomplete. The mutation issues remain excluded.

Linked issue update — 2026-11-02

[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221: Documentation PR #1320 merged at 2dc63cd40278295ad50ece7b037c59c88228c6c4. Its exact-head S1 qualification, secret scan, upgrade completeness, checked-LSN evidence, and aggregate PR correctness checks all passed. The spec now records the installed-trigger domain case and finite nine-pair SQL image oracle.
[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 remains open for arbitrary history and complete protected-window correctness; the umbrella stays open.

Linked issue update — 2026-11-02

[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221: PR test(cdc): enumerate valid multirow image histories #1319 exact-head workflow 41443007940 completed successfully at a8782e1b446f94db3a531e1d0d18d492dbed4333, including integration, unit, Windows compile, shipping-image upgrade, sensitive E2E, light E2E, checked-LSN and aggregate PR correctness checks.
The post-merge main run after test(cdc): enumerate valid multirow image histories #1319 was canceled by the later docs(cdc): record recent #1221 conformance evidence #1320 main push. The latest main CI run 41452825973 targets docs(cdc): record recent #1221 conformance evidence #1320's merge commit and still has checked-LSN queued. [Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 and this umbrella remain open.

Linked issue update — main CI for #1320

[Quality][Verus] Verify CDC normalization and observation-safe change elision #1221: Main CI run 41452825973 completed successfully on docs(cdc): record recent #1221 conformance evidence #1320 merge commit 2dc63cd40278295ad50ece7b037c59c88228c6c4, including checked-LSN and upgrade completeness.
PR test(cdc): exhaust two-identity image endpoints #1321 remains under exact-head qualification/E2E checks, so [Quality][Verus] Verify CDC normalization and observation-safe change elision #1221 and this umbrella remain open.

Bounded slice merged: exhaustive two-identity SQL oracle

PR #1321 merged as ff563398877cc1dd0087cb972ee75a2a02902ac1 from exact head 037afa6e49bade1778bea3426fb4611b996f6733. It adds a PostgreSQL execution oracle for all 81 initial/final state pairs across two row identities sharing a visible key, comparing production keyed_weight_sql with an independent complete-image bag model. It also makes installation-attestation writes locked and atomic after exact-head CI exposed a concurrent append race.

Exact-head CI run 41462986844 and S1 qualification run 41462986991 passed. The post-merge main CI run 41471328036 is queued.

This remains a bounded test slice. Broader valid transaction histories, complete PostgreSQL capture/reduction equivalence, source-incarnation transitions, and proof/enforcement for every protected consumer window remain open. Keep #1221 and this umbrella issue open.

Next bounded slice: SQL NULL as a complete row image

PR #1322, exact head 071ca5d679c6de6d3809c07f3274e48407ceb526, adds a production keyed_weight_sql execution case for two identities sharing a visible key. One history transitions from a NULL payload to a non-NULL endpoint; the other ends with a NULL payload. Local just fmt, just lint, and the focused PostgreSQL 18 Testcontainers case passed. Exact-head CI has started and is queued/running.

This distinguishes a NULL-valued row image from an absent row. General transaction histories, complete capture/reduction equivalence, and all protected consumer-window obligations remain open; #1221 and #1225 stay open.

Progress update: PR #1322 was squash-merged as b9d7224 (2026-11-02). It adds a focused PostgreSQL oracle case for NULL-valued complete-image histories. On exact head 071ca5d, the selected unit, integration, light-E2E, sensitive-E2E, shipping-upgrade, release-runtime, and checked-LSN checks all passed (17 passed, 0 failed). GitHub had left only the PR correctness aggregation job queued when the authorized merge proceeded; it did not report a failure. Post-merge main CI run #41482843356 is queued on merge commit b9d7224. This remains one narrow #1221 boundary case; the wider #1225 acceptance work stays open.

Linked issue update — source-incarnation runtime history

PR #1323, exact head 73a6c6d6cf740b0f8b64b87df743838b6710ca70, adds an installed PostgreSQL 18 regression for pending old-source images across same-name source recreation, in both row and statement trigger modes. just fmt, just lint, git diff --check, and the focused light-E2E Testcontainers run passed (1 passed, 18 skipped); hosted checks are queued.

This is a bounded #1221 runtime case. The linked issue remains open for general SQL capture/reduction and protected consumer-window equivalence.

Main CI follow-up — #1322

Main CI run 41482843356 completed successfully on merge commit b9d7224bca6d29e66eed185c5963ec2a67f003e4. #1221 and this umbrella issue remain open for the broader acceptance criteria.

PostgreSQL qualification: interleaved complete-image histories

PR #1324, exact head a7f23ac775ebca8f6a5f2bd257c170368dd18d79, adds an installed PostgreSQL 18 test for two source identities whose histories interleave and share complete output images. It runs in row and statement trigger modes, uses three separately committed multi-row updates, omits the source key from the output, observes numeric scale, forces differential maintenance with compaction eligible, and compares the resulting bag to the defining query.

just fmt, just lint, and the focused Testcontainers case passed (1 passed, 26 skipped, PostgreSQL 18.6). Exact-head hosted checks are running. This is finite SQL/runtime evidence for one multi-identity history; arbitrary history reduction and all protected-window obligations remain open.

Post-merge main CI — PR #1323

Main CI run 41496272241 completed successfully on exact merge commit 938f404108dd08b2b981f12d399c18430d63230a. Lint, coverage and secret scanning also passed on that commit. This qualifies the bounded source-incarnation runtime test; #1221 remains open for broader CDC history and protected-window acceptance.

Merge status — PR #1324

PR #1324 merged on exact head 595448d90f7d655d0a43579d91093f985fb463f7 as 77305dae1f83b6160861c548dd6ce373140e47a8. All exact-head PR checks passed, including the packaged candidate-binding runtime case and all three light-E2E shards. Post-merge main CI run 41509109302 is queued. This adds finite PostgreSQL runtime evidence for multi-identity interleaved complete-image histories; arbitrary production normalization and all protected consumer-window obligations remain open.

Protected consumer cuts — PR #1325

PR #1325 adds an installed PostgreSQL 18 test for two source identities whose complete output images interleave across an intermediate slow-consumer cut. It checks both row and statement CDC modes, exact bags at the fast and slow cuts, retained images after the fast consumer advances, and differential slow-consumer catch-up.

Local just fmt, just lint, the focused Testcontainers case (1 passed, 27 skipped), and candidate-binding tests (10 passed) succeeded. Exact-head hosted checks are queued. This remains finite runtime evidence; arbitrary production history normalization and all protected-window schedules remain unproved.

Candidate runtime qualification — PR #1325

On exact head 78bb83100b9dd4b04ab5ff552928365af1df3323, the Run packaged CDC image policy E2E and bind installed library step passed in CI run 41511322193. This step runs the new interleaved protected-cuts case against the packaged PostgreSQL extension and binds its installed library. Other exact-head light-E2E, release-runtime, and sensitive gates are still running. This is finite runtime evidence, not proof of all protected-window schedules or arbitrary normalization histories.

Post-merge main CI — PR #1324

Main CI run 41509109302 completed successfully on exact merge commit 77305dae1f83b6160861c548dd6ce373140e47a8. PR #1324 remains bounded runtime evidence for multi-identity interleaved image histories; #1221 stays open for arbitrary production normalization and all protected-window obligations.

Merge status — PR #1325

PR #1325 merged from exact head 78bb83100b9dd4b04ab5ff552928365af1df3323 as c7288f557b03186e2afc4747d10e06acfc21b427. All exact-head checks passed: candidate CDC installed-library binding, all three light-E2E shards, both sensitive E2E gates, unit/integration, Windows, ASan, semantic mutants, release controls, and the final correctness gate. Post-merge main CI run 41519451349 is queued. #1221 remains open for arbitrary normalization proofs and broader protected-window coverage.

[Quality] Correctness prevention: SQL semantics, lifecycle testing and bounded Verus proofs #1225

Description

Work items and recommended order

First: strengthen executable tests

Next: deliver proofs in bounded production slices

Relationship to existing work

Acceptance criteria (proposed)

Verification — PROPOSED — NOT RUN

Evidence and limits

Current delivery status (2026-11-01)

Activity

grove commented on Oct 29, 2026

grove commented on Oct 29, 2026

grove commented on Oct 29, 2026

grove commented on Oct 29, 2026

grove commented on Oct 29, 2026

Current delivery status

grove commented on Oct 29, 2026

CI update for candidate PRs

grove commented on Oct 29, 2026

CI update for candidate PRs

grove commented on Oct 29, 2026

Candidate CI update

grove commented on Oct 29, 2026

Delivery update

grove commented on Oct 29, 2026

grove commented on Oct 29, 2026

grove commented on Oct 31, 2026

Updated linked-issue status — 2026-10-31

grove commented on Oct 31, 2026

Updated linked-issue status — 2026-10-31

12 remaining items

grove commented on Nov 2, 2026

Linked issue update — 2026-11-02

grove commented on Nov 2, 2026

Linked issue update — 2026-11-02

grove commented on Nov 2, 2026

Linked issue update — main CI for #1320

grove commented on Nov 2, 2026

Bounded slice merged: exhaustive two-identity SQL oracle

grove commented on Nov 2, 2026

Next bounded slice: SQL NULL as a complete row image

grove commented on Nov 2, 2026

grove commented on Nov 2, 2026

Linked issue update — source-incarnation runtime history

grove commented on Nov 2, 2026

Main CI follow-up — #1322

grove commented on Nov 2, 2026

PostgreSQL qualification: interleaved complete-image histories

grove commented on Nov 2, 2026

Post-merge main CI — PR #1323

grove commented on Nov 2, 2026

Merge status — PR #1324

grove commented on Nov 2, 2026

Protected consumer cuts — PR #1325

grove commented on Nov 2, 2026

Candidate runtime qualification — PR #1325

grove commented on Nov 2, 2026

Post-merge main CI — PR #1324

grove commented on Nov 2, 2026

Merge status — PR #1325

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions