Skip to content

feat(instrument): persist PostgreSQL locale-specific releases - #50

Merged
seonghobae merged 2 commits into
mainfrom
feat/instrument-release-persistence-20260813
Aug 13, 2026
Merged

feat(instrument): persist PostgreSQL locale-specific releases#50
seonghobae merged 2 commits into
mainfrom
feat/instrument-release-persistence-20260813

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

Persist one immutable locale-specific instrument-release identity and its publication state on PostgreSQL 18. Exact replay is idempotent. Rebinding release_ref to a different digest, locale, item set, or other immutable field fails closed. The same manifest may advance to a reachable later state; rewind fails closed.

Psychometric evidence remains referenced, not recomputed. HTTP publication transport and session-creation integration stay outside this slice.

Physical schema

  • migrations/0006_instrument_release.sql — one-row instrument_release aggregate
  • two-or-more-word snake_case constraints
  • CHECK-constrained publication_state and SHA-256 content_digest

Verification

  • cargo test --offline --test postgres_instrument_release_persistence --test postgres_instrument_release_error_contract --test postgres_instrument_release_schema_constraints
  • cargo clippy --offline --all-targets -- -D warnings
  • cargo doc --offline --no-deps
  • cargo llvm-cov + scripts/check_coverage.py --kind lines: PASS 3693/3693; postgres_instrument_release.rs 157/157

Docs

TRACEABILITY, ERD, as-built schema, and CHANGELOG name this as Active PR work, not protected-main truth.

Store one immutable instrument-release identity plus publication-state
advance under READ COMMITTED, with exact replay and fail-closed digest
rebinding. Psychometric evidence stays referenced, not recomputed.
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 26f385ed-5ca0-4a65-b4e2-b5e92e7e8ce8

📥 Commits

Reviewing files that changed from the base of the PR and between 66ed162 and 08c16a4.

📒 Files selected for processing (10)
  • CHANGELOG.md
  • docs/TRACEABILITY.md
  • docs/architecture/AS_BUILT_SCHEMA.md
  • docs/architecture/ERD.md
  • migrations/0006_instrument_release.sql
  • src/lib.rs
  • src/postgres_instrument_release.rs
  • tests/postgres_instrument_release_error_contract.rs
  • tests/postgres_instrument_release_persistence.rs
  • tests/postgres_instrument_release_schema_constraints.rs

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.

@seonghobae
seonghobae merged commit daab993 into main Aug 13, 2026
30 checks passed
seonghobae added a commit that referenced this pull request Aug 13, 2026
Name exact protected main daab993 as the evaluated baseline. Mark
instrument-release persistence and response payload-digest validation as
protected-main truth. Keep engine-artifact digest validation as Active PR #43.
seonghobae added a commit that referenced this pull request Aug 13, 2026
Reconcile TRACEABILITY to protected-main daab993, keep this slice
explicitly not protected-main truth, and record the local propagation
entity on the logical ERD.
seonghobae added a commit that referenced this pull request Aug 13, 2026
The link-end foreign key now blocks dropping the link-event table
alone. Also keep the exact Active PR marker after the #50 rebase.
seonghobae added a commit that referenced this pull request Aug 13, 2026
Name **Active PR** #53 as not protected-main truth on the current
instrument-release baseline.
seonghobae added a commit that referenced this pull request Aug 13, 2026
…lity (#43)

* test(scoring): require canonical engine artifact digest

* fix(scoring): fail closed on noncanonical engine digest

* test(scoring): use canonical engine artifact fixtures

* test(result): use canonical engine digest fixture

* test(result): pin canonical engine provenance

* test(scoring): keep digest provenance canonical

* test(scoring): use canonical digest in provenance collision cases

* test(scoring): exercise hexadecimal digest branch

* test(scoring): cover invalid engine digest diagnostics

* test(scoring): satisfy clippy error expectation

* test: keep scoring fixture compatible with response digest contract

* docs: reconcile traceability after #44 and #50

Name exact protected main daab993 as the evaluated baseline. Mark
instrument-release persistence and response payload-digest validation as
protected-main truth. Keep engine-artifact digest validation as Active PR #43.
seonghobae added a commit that referenced this pull request Aug 13, 2026
Reconcile TRACEABILITY to protected-main daab993, keep this slice
explicitly not protected-main truth, and record the local propagation
entity on the logical ERD.
seonghobae added a commit that referenced this pull request Aug 13, 2026
The link-end foreign key now blocks dropping the link-event table
alone. Also keep the exact Active PR marker after the #50 rebase.
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.

1 participant