Skip to content

Qualify actual retention through Catalog field computation offline - #130

Merged
sswiftdrtv merged 1 commit into
mainfrom
codex/retained-field-integration-2207
Oct 27, 2026
Merged

sswiftdrtv merged 1 commit into
mainfrom
codex/retained-field-integration-2207

Conversation

@sswiftdrtv

@sswiftdrtv sswiftdrtv commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

The Catalog evaluator tests supply qualified/unavailable boundary fixtures without executing retention and the authority read. This adds a disposable integration harness that calls the actual writer, obtains the exact read_binding envelope from its receipt, and invokes the pinned API #1190 evaluator while the read transaction remains open.

Eight integration tests cover all four fields and complete binding/provenance, missing versus observed zero, retry versus current document revision, supported correction with new retention/recomputation, withdrawal and membership revocation, competing mutation locks, UTF-8 refusal and source-history budget denial. CI keeps the existing 45 reader/writer tests and adds the integration suite on PostgreSQL 15/17 with API head 6ba799dbb67be284adcd6f8bcd8fcde2faa6c2b8, verified evaluator/recipe/helper hashes and frozen dependencies.

Validation at ed9e805369f1a9ca52174928b5b3b9c24d9508be: CI matrix passed all 45 existing tests plus all eight integration tests on both PostgreSQL 15 and 17, including cleanup. All other Actions checks passed; zero review threads. Local eight-test runs passed on PostgreSQL 15/17. Independent source review passed, including an independent PostgreSQL 15 run and final assertion-only delta review.

Offline qualification only: no migration, grant, runtime adapter, provider ingestion, UI descriptor projection or production activation. Currentness is protected only during the held transaction; later publication/caching needs its own protocol. Root owns merge and activation gates. See the protocol for reproducible commands and bounded claims.

Summary by CodeRabbit

  • Tests

    • Added integration coverage for retained-field reads, evaluation, binding, retries, corrections, revocations, storage limits, and concurrent updates.
    • The checks run for changes to the proposal and across PostgreSQL versions 15 and 17.
  • Documentation

    • Added guidance for running the integration suite, including its scope, limits, and remaining production gates. These checks do not indicate that the behavior is deployed.

@supabase

supabase Bot commented Oct 27, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project godremdqwajrwazhbrue because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-27T18:10:31.231693Z ed9e805 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 39e05998-be0e-4ca2-989b-66d59b6b102d
Commits

Reviewing files that changed from the base of the PR and between a118b02 and ed9e805.

Files selected for processing: 4
  • .github/workflows/stream-binding-proposal.yml
  • proposals/retained-field-integration-2207/PROTOCOL.md
  • proposals/retained-field-integration-2207/build.mjs
  • proposals/retained-field-integration-2207/test_integration.py

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

Adds a pinned-source integration suite that exercises retained-field reads and evaluation against disposable PostgreSQL. The suite checks bindings, field results, revisions, source mutations, size limits, and transaction locks. A workflow runs it for PostgreSQL 15 and 17, and a protocol document records setup and scope.

Changes: Retained-field integration suite

Layer / File(s) Summary
Pin and run the integration harness
.github/workflows/stream-binding-proposal.yml, proposals/retained-field-integration-2207/test_integration.py, proposals/retained-field-integration-2207/build.mjs
The test setup verifies a pinned API checkout and builds the evaluator. Helpers exercise locked reads and evaluation. The workflow installs dependencies and runs the suite for PostgreSQL 15 and 17.
Check field results and currentness
proposals/retained-field-integration-2207/test_integration.py
Tests check complete and unknown field results, retries and revisions, refusals after source changes, and recomputation after a supported correction.
Check budgets and transaction locks
proposals/retained-field-integration-2207/test_integration.py, proposals/retained-field-integration-2207/PROTOCOL.md
Tests check UTF-8 and storage budgets, plus lock contention during evaluation. The protocol documents the test flow, limits, and stated production and UI handoff gates.

Priority: Low

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Other

Possibly related issues

  • recoupable/app#2305 — The PR adds end-to-end conformance tests for retained writes, Catalog evaluation, source changes, and currentness.
  • recoupable/app#2277 — The tests cover source-bound field computation, provenance, revisions, and corrections.
  • recoupable/app#2278 — The tests check binding, query, provenance, and refusal states in Catalog field results.
  • recoupable/app#2116 — The suite exercises versioned evidence reads and behavior after correction, withdrawal, and revocation.

Possibly related PRs

  • recoupable/database#127 — This PR tests the read_binding behavior defined by PR #127 as part of an end-to-end flow through the Catalog evaluator.

Suggested reviewers: sweetmantech

Merge Risk: Minimal · up to ed9e8

The qualification suite is ready to merge after normal CI checks; it does not activate production behavior.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi… Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed Passed checks: 4 passed
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title "Qualify actual retention through Catalog field computation offline" matches the main change. The PR adds an offline integration test suite. The suite runs the actual retention writer and th…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title "Qualify actual retention through Catalog field computation offline" matches the main change. The PR adds an offline integration test suite. The suite runs the actual retention writer and the pinned Catalog evaluator against a disposable PostgreSQL database. The title states the offline scope. It does not mention the workflow change or the documentation, which is acceptable because those support the main change. The title is specific, concise, and uses no vague terms.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 14 functions across 2 files. (2 skipped: 2 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

Finishing Touches: 💡 1
📝 Generate docstrings: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sswiftdrtv
sswiftdrtv merged commit 5e41ab1 into main Oct 27, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants