feat: collection offer books, royalty enforcement, signal edit history, emoji reactions

[KingFRANKHOOD]

Summary

Implements four flag-gated features, each an isolated module in an existing *-store.ts wired additively into its API routes. All four flags default off — zero behavioural change on main until explicitly enabled.

• [Feature] Add collection-level offer books aggregated from token offers (Module #71) #88 (phase-139): collection-level offer books aggregated from per-token offers, plus bulk-bid across a collection's listings. New: GET/POST /api/market/collections/[collection_id]/offer-book.
• [Architecture] Implement royalty enforcement on secondary sales via contract split (Module #72) #89 (phase-140): royalty enforcement on secondary sales — a creator/seller split computed and ledgered at offer-accept time. Listing create gains optional creator_wallet/royalty_bps; accepting an offer on a secondary sale now records and reports a royalty split.
• [Spike] Implement signal edit history with version diffing (Module #82) #100 (phase-82): signal edit history with word-level version diffing. New PATCH /api/signals/[id] (author-only, snapshots the pre-edit state) and GET /api/signals/[id]/history.
• [Feature] Add emoji-reaction aggregation with rate limits (Module #83) #101 (phase-83): emoji-reaction aggregation on signals (curated 6-emoji set, toggle per wallet) with a 20/60s per-wallet rate limit. New GET/POST /api/signals/[id]/reactions.

Each issue's "Impacted Subsystems" pointed at files that didn't line up with where the feature actually belongs in this codebase (e.g. offers/listings live in lib/market-store.ts behind app/api/market/*, not the signals/replies files listed). Implemented against the domain each feature actually fits, per the title + acceptance criteria — see IMPLEMENTATION_SUMMARY_88_89_100_101.md for the reasoning and full per-issue breakdown.

Also fixes a pre-existing bug blocking all of the above

lib/sqlite-db.ts:getDb() calls serverDataJsonPath("sqliteDb"), but "sqliteDb" was never registered in lib/server-data-paths.ts's FILES map when signals/market were migrated onto SQLite (issue #36) — every getDb() call threw at runtime, i.e. every signal/market read or write. This was masked because a pre-existing, unrelated syntax error in app/api/forge-agent/route.ts aborts tsc's whole-program check before semantic diagnostics run, so npm run typecheck silently reported nothing wrong, and lib/__tests__/signals-social.test.ts / market-profile-views.test.ts were quietly failing on main too. One-line, additive fix (sqliteDb: "phase.sqlite3") — no schema change, no migration.

Test plan

• npx tsc --noEmit (scoped to exclude the pre-existing forge-agent parse failure): 0 errors in every changed/new file.
• eslint on every changed/new file: clean.
• Full suite on Node 22 (node --test --import ./node_modules/tsx/dist/loader.mjs ...): 253 → 269 passing, 0 regressions. Remaining 26 failures are pre-existing/unrelated (see summary doc).
• New suites, 20 cases across the 4 features:

  node --test --import ./node_modules/tsx/dist/loader.mjs \
    lib/__tests__/collection-offer-book.test.ts \
    lib/__tests__/royalty-split.test.ts \
    lib/__tests__/signal-edit-history.test.ts \
    lib/__tests__/signal-reactions.test.ts
  

• PROJECT_ARCHITECTURE.md §10 and docs/TECHNICAL.md §5.3/§9.1 updated with the four new flags per CLAUDE.md's change-management rule.

Closes #88
Closes #89
Closes #100
Closes #101

🤖 Generated with Claude Code

[drips-wave]

@KingFRANKHOOD Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits