refactor(db): move moderation store ownership - #6808
Closed
TheSentinel454 wants to merge 1 commit into
Closed
Conversation
TheSentinel454
force-pushed
the
codex/issue-2-moderation-store
branch
from
August 25, 2026 20:07
5fd23b4 to
da6d86c
Compare
TheSentinel454
force-pushed
the
codex/issue-2-moderation-store
branch
from
August 25, 2026 20:59
da6d86c to
f87152c
Compare
TheSentinel454
force-pushed
the
codex/issue-2-moderation-store
branch
2 times, most recently
from
August 26, 2026 15:53
4e89d99 to
a0a4afc
Compare
TheSentinel454
force-pushed
the
codex/issue-2-moderation-store
branch
from
August 27, 2026 20:07
a0a4afc to
2146ba5
Compare
Signed-off-by: OpenAI Codex <codex@openai.com>
TheSentinel454
force-pushed
the
codex/issue-2-moderation-store
branch
from
August 28, 2026 14:56
2146ba5 to
95755df
Compare
Contributor
Author
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current reconstructed head
Exact base:
codex/issue-2-product-feedback-storeat011301f32318163a2291a537f3d4184f4f39e9ddExact head:
codex/issue-2-moderation-storeata0a4afc5317bb15e02f77a169ca359e8af289e28This 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-dbclippy, 111 non-PostgreSQL library tests with 200 PostgreSQL tests ignored, the observability source test, relay consumer compilation, exact ownership/unique-span review checks, and 7 moderation PostgreSQL tests on native PostgreSQL where applicable.Summary
Continue tracker #2 by making
moderation.rsown the moderation-report, restriction, and audit-action persistence boundary. Records, SQL, parsers, and focused PostgreSQL tests already lived there; this child moves the remaining fourteenDbmethods and datastore spans out oflib.rswithout changing public signatures or behavior.Stack
Domain moved
crates/buzz-db/src/lib.rsfalls from 4,192 to 4,033 lines.Non-goals
admin_moderation.rsRisk
Moderate review surface and low semantic risk. The fourteen facades and spans moved intact and call the same module-owned functions with the same pool, arguments, and return types. Existing SQL, parsers, records, and focused tests are unchanged. The only extra line is a secret-scanner suppression on the long-standing fake local test URL after moving that fixture to a newly scanned file; the signed commit hook accepted it normally.
Blox verification
Author workstation:
buzz-tornquist-issue-2-store-stack(2046520), exact head5fd23b4bd81d9db24c2ac4ad29a7ff74590de700.cargo fmt --all --checkgit diff --check c007b0fdf7e213c8a1120c65a37dbf999d2e320d..HEADcargo clippy -p buzz-db --all-targets -- -D warningscargo clippy -p buzz-relay --all-targets -- -D warningscargo test -p buzz-db --lib: 108 passed, 200 ignoredcargo test -p buzz-db --test observability_source: 1 passedcargo test -p buzz-relay --lib: initial run had one unrelated mesh-demo HTTP 504; that exact test passed alone and the complete rerun passed 909 tests with 48 ignoredIndependent exact-head Blox review: no findings. The unrelated mesh-demo 504 was reproduced transiently, passed alone, and passed in the final complete run. Review artifacts were preserved before teardown.
Remaining tracker work
Next: git repository registry and archived identities, then usage/admin/maintenance, deletion ownership, and the final runtime-boundary/test audit.
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.
Result
No findings.
Exact revision and isolation
6ae5893c36429f778105285ce77fc890ad5e3c67da6d86cb4f46504edd3d860571e670d07b2f2023buzz-tornquist-pr-6808-final-review(2057663)The fresh shallow workstation was clean and unclaimed, had no competing commands, and had no Buzz production relay credentials or ownership-report file.
Review conclusions
Dbfacades move tomoderation.rswith identical signatures, tenant inputs, calls, return types, and fixed-label span names.lib.rs.Verification
-D warnings: passed.Artifacts:
pr-6808-final-review-artifacts.tgz, SHA-2561a6534c33be6538ebd33d6fc7c535dff23cfabff9adc9700d9b77d18f2f4ef1a. Archive and internal checksums were verified locally.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.
64fa6de401a9a14f2aa5da3dd13beac19942a944f87152c1c0d3f9ab460e5b54711af41b43da0e286fa2f104d42c6ba85bdf62e7ccb74ceaf4a84f67buzz-db/buzz-relayClippy; DB lib 111 passed / 200 ignored; ownership 21/21; observability 1/1; every moved PostgreSQL test; relay lib 910 passed / 49 ignored.buzz-db/buzz-relayClippy, DB lib and current ownership/observability/unique-span guards, 7 moderation PostgreSQL tests, and relay compilation.