c_ed5070da05a14321c4

Side B is a small, surgical commit: it adds a real bugfix (room garden pages no longer silently fall back to the public scope when a private room has no content, preventing content leakage), factors out a well-documented `thread_post_index_chronological` helper to eliminate duplicated fragile lookup logic across rpc.rs/garden.rs/ingest.rs, and backs the fix with new integration and browser regression tests. Side A is a sprawling 'reshuffle' commit that mostly moves large chunks of working code into a `legacy/` directory, checks in a huge generated Cargo.lock, and stands up a mostly-empty demo scaffold (health check, counter bump) — it's a project reset with high line count but little durable engineering value per line, and it discards more functionality than it adds.

Side B fixes real behavior bugs (empty private-room gardens no longer fall through to public content; thread_post_index is centralized as stable 0-based chrono indices with redact-safe rebuild semantics) and adds focused integration/browser regression tests. Side A is mostly reshuffle noise—renames, legacy moves, Cargo.lock, and scaffolding—with far less net correctness per line despite its size.

Side B introduces lasting abstractions by centralizing thread post index lookup into `ReducerState::{try_thread_post_index_chronological, thread_post_index_chronological}`, replacing duplicated indexing logic across RPC and HTML code, and adds regression tests ensuring redacted posts preserve stable chronological indices. Side A is dominated by a large project reshuffle (moving files into `legacy/`, renames, workspace/bootstrap, generated `Cargo.lock`, CI, and scaffolding) with relatively little new enduring behavior compared to the amount of churn.

Side A extracts duplicated, panic-prone thread-index logic into well-documented reducer helper methods, fixes a real bug (garden 404 fallback for empty private rooms), and adds substantial regression tests (integration test + browser test) proving correctness after redaction. Side B merely moves a single div element in markup with no functional or test impact, offering negligible lasting value.

A extracts shared thread-index helpers, fixes empty private-room gardens falling back to public content (with an integration test), documents tombstone stability in the reducer, and adds a full browser regression for PostRedact vs chronological indices—plus aligning FeedPost indexing to 0-based. B only relocates an errors div in new-thread HTML, a trivial presentation nit with no lasting design or correctness impact.

Side A introduces reusable reducer helpers for chronological thread indices, fixes multiple call sites to use them consistently, adds guards so empty private room gardens return 404 instead of falling back to public content, documents important reducer invariants, and adds regression/integration tests covering these behaviors. Side B only moves the error container element within the new-thread form markup, a minor UI/layout adjustment with far less lasting impact.