c_fc17a4aa31e6a2aa58

Side B is a real functional/UI fix that reworks post_header_meta to consolidate delete button placement, adjusts CSS flex layout in two themes, and refactors call sites—concrete, testable product code. Side A is a small CI workflow tweak (npm OIDC publishing config) which is useful infra maintenance but lower in lasting code value and scope compared to B's cross-cutting UI/logic change.

A modernizes the npm release path for OIDC trusted publishing (Node 22, npm upgrade, drop NODE_AUTH_TOKEN secrets), a lasting security/ops improvement to how packages ship. B only relocates the delete control into post header meta and adjusts flex CSS—useful UI polish, but a small layout refactor with less project-wide impact.

Side A updates the release workflow toward npm OIDC trusted publishing by moving to Node 22, upgrading npm to a version that supports trusted publishing, and removing reliance on injected NPM auth tokens in the publish steps. Side B is a clean UI refactor that relocates the delete button into the post metadata and adjusts CSS layout, but it primarily changes presentation rather than project infrastructure or release behavior.

Side B is a substantial architectural refactor that removes cached edge/index state (GroupState) in favor of a minimal source-of-truth (ScopeVotes) with edges/components derived on demand, touching ranking, reducer, storage, pair-suggestion logic, and tests consistently—reducing state-sync bugs and simplifying persistence. Side A is a small, purely cosmetic UI tweak (moving the delete button into the meta row with CSS flex adjustments) with no behavioral or architectural impact.

A only relocates the delete control in forum HTML/CSS (post_header_meta + flex layout tweaks) with no behavioral or data-model change. B simplifies the core ranking store by replacing GroupState’s cached indices/edges/voted_pairs with ScopeVotes (uuid_votes + recent_votes) and deriving edges/components at rank time across reducer, ranking, pair, storage, and tests—reducing maintained state and inconsistency risk.

Side B performs a substantial architectural refactor by replacing the cached `GroupState` with `ScopeVotes`, deriving graph edges, connected components, and rankings on demand from persisted votes. It updates ranking, storage, reducer, UI, and tests consistently, simplifying persisted state while preserving behavior; Side A is primarily a UI layout change that moves the delete button into the post metadata and adjusts CSS for flexbox positioning.

Side A eliminates substantial duplicated HTTP/OAuth/test-harness code across four test files by consolidating it into shared common.bb/oauth.bb helpers, reducing maintenance burden and duplication risk with no behavior loss. Side B is a small, localized UI tweak (moving a delete button) with modest CSS/markup changes that fixes a cosmetic layout issue but has narrower lasting impact on the codebase.

Commit A consolidates duplicated test harness, HTTP/OAuth mocks, registration helpers, cargo build, and server env into shared modules (common.bb/oauth.bb), shrinking auth/grants/integration and improving maintainability. Commit B only relocates the delete control into post_header_meta with flex CSS tweaks—presentational churn with little lasting design impact.

Side A consolidates duplicated test infrastructure into shared utilities by introducing reusable helpers in `test.common` and `test.oauth` (shared assertions, server environment creation, cargo build wrapper, OAuth registration flow, configurable mock Google server, and common HTTP behavior with timeouts), then updates multiple test suites to use them. This reduces duplication and centralizes maintenance across the integration tests, whereas Side B is primarily a UI layout refactor that moves the delete button into the metadata component and adjusts CSS flexbox styling without changing core functionality.

Side B is a targeted, integrated fix that moves the delete button into the existing ingest header, refactors the shared post_header_meta helper, and updates CSS in two real theme files, all clearly wired into the running app. Side A drops a large standalone reddit.rs file at the repo root with no Cargo.toml/mod wiring shown, reading like a generic boilerplate API client dump rather than an integrated, exercised part of the codebase.

A adds a full Reddit API client (rate limiting, typed listing/post/comment models, response helpers)—foundational capability. B only relocates an existing delete control in the forum header and tweaks related CSS, a small UI polish with far less lasting scope.

Side A adds an entirely new Reddit API client with rate limiting, request handling, structured response types, custom serde deserializers, and helper methods for working with posts and comments, introducing substantial reusable functionality. Side B mainly refactors the post header to relocate the delete button and updates CSS flex layout to support the new placement, which is a useful UI improvement but much narrower in long-term impact.

Commit A performs a meaningful structural refactor, splitting a monolithic forum.rs into cohesive modules (nav, ingest, new_thread, room_members, access), reducing duplication (e.g. removing separate rpc-value helper functions) and adding a genuinely useful sample-fixture dev tool. Commit B is a small, focused CSS/markup tweak moving the delete button's position, which is a real but narrow UI fix with much less lasting architectural value.

A’s lasting value is the forum split into focused modules (nav, access, ingest, new_thread, room_members) that structure real domain boundaries; B only relocates the delete control into the meta row with flex CSS. Minor noise in A (sample-fixture script, RPC helper inlining) does not outweigh that architectural win over B’s small UI polish.

Side A performs a substantial architectural refactor by extracting forum functionality into focused modules (such as access, ingest, navigation, room members, and new thread handling) and centralizing reusable logic like URL helpers and permission checks, improving maintainability without changing behavior. It also adds a useful developer profiling script (`sample-fixture`) and removes redundant helper wrappers by inlining simple RPC generation, whereas Side B mainly repositions the delete button within the post metadata and adjusts CSS layout for that UI change.