Skip to content

refactor(db): move user and DM store ownership - #6796

Closed
TheSentinel454 wants to merge 1 commit into
codex/issue-2-feed-storefrom
codex/issue-2-user-dm-store
Closed

refactor(db): move user and DM store ownership#6796
TheSentinel454 wants to merge 1 commit into
codex/issue-2-feed-storefrom
codex/issue-2-user-dm-store

Conversation

@TheSentinel454

@TheSentinel454 TheSentinel454 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Current reconstructed head

Exact base: codex/issue-2-feed-store at 31f52ef39eb42107a1d593f221ff9894a38ccb39
Exact head: codex/issue-2-user-dm-store at 4664593b6f5f90394bc0d2432b26822dbede9c44

This current head removes crates/buzz-db/tests/store_ownership.rs; no replacement path-sensitive ownership test is introduced. Apart from removing that complete test-file diff, the production patch is byte-for-byte identical to the previously reviewed slice. This remains part of tracker #2 and the #17/#19 acceptance work.

Independent exact-head review from a separate clean Blox workstation found no issues. Current-head evidence passed formatting, strict buzz-db clippy, 111 non-PostgreSQL library tests with 200 PostgreSQL tests ignored, the observability source test, relay consumer compilation, exact ownership/unique-span review checks, and 8 user PostgreSQL tests and 4 non-PostgreSQL DM tests on native PostgreSQL where applicable.

Why

Continue tracker #2 by completing user and direct-message persistence ownership. The user and DM SQL, records, helpers, and focused tests already lived in user.rs and dm.rs; this child moves the remaining Db APIs and datastore spans out of lib.rs so each domain has one implementation owner. This PR stacks on #6794.

What

  • Move all nine user-facing Db APIs and their datastore spans into user.rs
  • Move all seven direct-message Db APIs and their datastore spans into dm.rs
  • Preserve every public Db method signature and existing crate-root/module exports
  • Keep user SQL, profile/search records, row handling, and focused tests in user.rs
  • Keep DM SQL, participant/channel records, hashing helpers, and focused tests in dm.rs
  • Keep runtime read routing and its proofs/tests in lib.rs
  • Retain the existing fixed local-only PostgreSQL test URL with the repository-standard inline sadscan suppression required after its line moved

Stack

Non-goals

  • No SQL, schema, locking, transaction, retry, timeout, pagination, hashing, visibility, or client-visible behavior changes
  • No movement of runtime read routing, sessions, or proofs out of lib.rs
  • No store traits, domain-handle redesign, broad PgExecutor migration, raw pool accessor, new crate, or directory-wide reorganization
  • No changes to, retargeting of, or merge action on parent PRs or PR Add database pressure observability #6700

Risk Assessment

Low semantic risk. The sixteen wrappers and spans moved intact and still call the same domain SQL functions with the same pool, arguments, return types, and ordering. Existing user/DM records, parsers, helpers, SQL, and tests remain in their owning modules.

Blox Verification

Author workstation: buzz-tornquist-issue-2-store-stack (2046520), exact head 9e63d4ad728ed893a32e923d56d66e58d9ca7599.

  • cargo fmt --all --check and git diff --check — passed
  • cargo clippy -p buzz-db --all-targets -- -D warnings — passed
  • cargo clippy -p buzz-relay --all-targets -- -D warnings — passed
  • cargo test -p buzz-db --quiet — 108 passed, 200 ignored
  • Native PostgreSQL user::tests:: ignored suite — 8 passed
  • DM focused unit tests — 4 passed as part of the DB suite
  • cargo test -p buzz-relay --lib -- --test-threads=1 — 909 passed, 48 ignored
  • Commit-time formatting, sadscan, attribution, and sign-off hooks — passed
  • Review follow-up moved the misplaced Tests section header below the production DM wrapper block; exact-head fmt, diff, and ownership checks passed

Independent exact-head Blox review: buzz-tornquist-pr-6796-review (2051741) verified final head 9e63d4ad728ed893a32e923d56d66e58d9ca7599, 16/16 wrapper equivalence, 16/16 byte-identical SQL functions, unique spans, unchanged tests apart from the scoped scanner suppression, and the retained runtime routing boundary. The reviewer found the misplaced Tests header, confirmed the comment-only fix on the final head, and reported no remaining findings. Formatting, diff, DB/relay clippy, 108 DB tests, 8 user PostgreSQL tests, 4 DM tests, ownership checks, the sadscan staged probe, and final 909 relay tests passed. The review workstation was deleted after artifact verification.

Generated with Codex

Superseded pre-comment restack verification

PR #6700 merged before publication completed. This layer was restacked onto current main through the exact parent named above; the final cumulative tip is 2ddcc8a. Cumulative author gates passed: formatting and diff checks; buzz-db and buzz-relay all-target clippy with -D warnings; DB lib 111 passed / 200 ignored; ownership 22/22; observability 1/1; the full isolated PostgreSQL domain matrix; and relay lib 910 passed / 49 ignored.

Outcome

No actionable findings.

Reviewed exact base ecd17550f7e6e7b4f25399a546072177a0eb20a6 through exact head 48822f008819089618593edcee78bb468a21ec05 on fresh Blox workstation buzz-tornquist-pr-6796-final-review (ID 2057634). The range contains the ownership extraction commit plus its documentation-only follow-up. Nine user wrappers and seven DM wrappers retain their signatures, calls, SQL owners, types, and single datastore spans; route/session infrastructure remains in lib.rs.

Verification

  • Formatting, range/worktree diff checks, touched-crate clippy, and clean-tree checks passed.
  • Non-PostgreSQL tests: user 5 passed/8 ignored; DM 4 passed.
  • Relay consumer compile passed.
  • Native PostgreSQL 17: all 8 ignored user tests passed; the DM module has no ignored PostgreSQL tests.
  • Exact head and base merge-base were rechecked.

No code edits or external mutations were made. Buzz relay credentials/ownership reporting were unavailable under the documented fallback. The workstation was deleted after artifact transfer.

Artifacts

  • Diff SHA-256: 9a62ded16afce24a3ffb04f83c8c6f9838f413675f3877cc1cbae92bcec21915
  • Verification log SHA-256: e848ac25a588eaec7d2e983e659640dedf6efc8ed642bb8f79d694ea72cb19d2
  • Artifact archive SHA-256: a1047df1b60e4f3dedc43b116cce62dc6147c36603b73984b325200c0d2b3229

Comment-addressed restack

Review follow-up on #6777 removed only the low-value replaceable ownership source test. This PR was restacked onto its rewritten parent; its production patch is unchanged.

  • Exact base: 30621460f04c38467ea0df1731fce2763d696c04
  • Exact head: d6abdf916ea53ad59e9f1d909db5256a06c2a661
  • Final cumulative tip: 6fa2f104d42c6ba85bdf62e7ccb74ceaf4a84f67
  • Per-layer patch-ID and tree audits confirm this PR’s production diff is unchanged from its pre-comment head.
  • Cumulative Blox gate: formatting and diff checks; strict buzz-db/buzz-relay Clippy; DB lib 111 passed / 200 ignored; ownership 21/21; observability 1/1; every moved PostgreSQL test; relay lib 910 passed / 49 ignored.
  • Independent re-review at this exact head: no findings; fresh exact-parent/head Blox review passed fmt/diff, strict buzz-db Clippy, current ownership/observability guards, user/DM unit tests, all 8 user PostgreSQL tests, and relay compilation.

Signed-off-by: OpenAI Codex <codex@openai.com>
@TheSentinel454

Copy link
Copy Markdown
Contributor Author

🤖 Superseded by #6987, which consolidates the remaining issue #2 store-extraction stack onto merged #6782. #6987 is an open draft at the independently reviewed exact head, and all exact-head CI checks are green. This PR remains available for review history; please continue review on #6987.

TheSentinel454 added a commit that referenced this pull request Aug 28, 2026
## Summary

Finish the remaining database-store extraction tracked by
[TheSentinel454#2](TheSentinel454#2)
in one reviewable PR.

This consolidates the previously stacked domain slices after #6782
merged. It preserves the runtime/store boundary established by #6660,
#6668, #6700, and #6782 while separating database runtime infrastructure
from domain-owned persistence:

- `runtime/` owns pool construction and sizing, writer/reader routing,
read sessions and route proofs, transaction infrastructure,
observability primitives, replica fencing, health support, migrations,
and cross-cutting runtime tests.
- `store/` owns domain records, SQL, row parsing, locks and invariants,
`Db` domain methods, focused tests, and logical-operation datastore
spans.
- `lib.rs` remains a 57-line compatibility facade that preserves
existing crate-root paths and `Db` method signatures through re-exports.

Domain coverage includes API tokens, authentication allowlists,
reminders, event queries, threads, reactions, feeds, users and DMs,
push, workflows/runs/approvals, relay membership and invites, product
feedback, moderation/admin moderation, relay admin actions/operators,
git repositories, archived identities, usage, partition maintenance,
deletion, channel membership inherited from merged #6782, and the final
runtime/store layout.

The branch has been rebased onto current `main`. Database changes that
landed there were incorporated rather than overwritten:
`relay_admin_actions.rs` and `relay_operators.rs` now live under
`store/`, their 27 public `Db` wrappers and existing behavior remain
intact, and every wrapper has exactly one fixed-name datastore span.
Concurrent changes to migration, moderation, admin moderation, and error
handling are also retained.

### Exact base and head

- Base: `main` at `ed11c8d8bf0a17402be5cf243724f89471530d2f`
- Head: `codex/issue-2-store-extraction` at
`be24430472d1a87ac5c0d6026c620cd6caea3537`

### Related issue

- Structural tracker:
[TheSentinel454#2](TheSentinel454#2)
- Domain trackers:
[#6](TheSentinel454#6),
[#7](TheSentinel454#7),
[#12](TheSentinel454#12),
[#13](TheSentinel454#13)
- Acceptance trackers:
[#17](TheSentinel454#17),
[#19](TheSentinel454#19)

This supersedes #6783, #6784, #6787, #6788, #6789, #6792, #6820, #6794,
#6796, #6797, #6798, #6799, #6804, #6805, #6806, #6808, #6809, #6811,
#6812, #6813, #6814, #6815, and #6890. Their discussions remain
available for review history.

### #17 / #19 acceptance

- Preserves the metric names, fixed labels, transaction/lock timing
boundaries, and privacy/cardinality constraints introduced by #6700.
- Keeps exactly one datastore span per public logical operation,
including the 27 relay-admin wrappers added on `main`.
- Removes `store_ownership.rs`; physical ownership and focused source
guards now enforce the boundary directly.
- Leaves no `impl Db`, domain SQL, focused domain test group, or
datastore span in `lib.rs`.
- Preserves existing public paths such as `buzz_db::channel`,
`buzz_db::event`, and `buzz_db::workflow` through crate-root re-exports
while keeping internal `runtime` and `store` namespaces private.

### Non-goals

- No SQL, schema, locking, transaction, retry, timeout, or
client-visible behavior changes.
- No generic store traits, domain handles, broad `PgExecutor` migration,
new store crate, raw pool accessor, or broader directory reorganization.
- No tracker issues are closed by this PR.

### Risk

The cumulative diff is large but structural. Risk is primarily
module-path, ownership, or conflict-resolution drift. It is mitigated by
preserving public re-exports, comparing the newly moved `main`
implementations to their upstream source, source guards, touched-crate
compilation, PostgreSQL-backed test coverage, and an independent
exact-head review on a separate clean Blox workstation.

### Testing

Author workstation `buzz-tornquist-pr-6987-rebase`, rebased branch
ending at exact head `be24430472d1a87ac5c0d6026c620cd6caea3537`:

- `cargo fmt --all --check`
- `cargo clippy -p buzz-db -p buzz-relay --all-targets -- -D warnings`
- `cargo test -p buzz-db --lib` — 113 passed, 240 PostgreSQL tests
intentionally ignored
- `cargo test -p buzz-db --test observability_source` — 2 passed
- PostgreSQL-backed `buzz-db` coverage under native PostgreSQL — 235
passed in the shared serial run; the five shared-state/config-sensitive
cases passed as isolated reruns against fresh schemas, including the two
owner-limit tests with their fixture's
`BUZZ_MAX_COMMUNITIES_PER_OWNER=3`
- `cargo test -p buzz-relay --lib -- --test-threads=1` under native
PostgreSQL/Redis — 991 passed; the three current-month
partition-sensitive identity-archive cases passed after provisioning the
August 2026 test partition; 87 infrastructure-marked tests remained
ignored
- Source/diff guards — relay-admin implementation bodies match current
`main`; all 27 public wrapper signatures are retained; exactly one
datastore span wraps each wrapper; `lib.rs` has zero `impl Db` blocks
and zero datastore spans; no duplicate top-level relay-admin modules or
`store_ownership.rs`; `error.rs` matches current `main`

Independent clean review workstation `buzz-tornquist-pr-6987-review`,
detached at exact head `be24430472d1a87ac5c0d6026c620cd6caea3537`:

- `cargo fmt --all --check`
- `cargo clippy -p buzz-db -p buzz-relay --all-targets -- -D warnings`
- `cargo test -p buzz-db --lib` — 113 passed, 240 ignored
- `cargo test -p buzz-db --test observability_source` — 2 passed
- Exact-head ownership/re-export/instrumentation audit — no remaining
actionable findings

---------

Signed-off-by: OpenAI Codex <codex@openai.com>
Signed-off-by: tornquist <tornquist@squareup.com>
Co-authored-by: OpenAI Codex <codex@openai.com>
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