[#233] Add contract_address column for multi-contract support

[realproject7]

Summary

• Migration: contract_address TEXT NOT NULL on all 6 tables, existing rows default to old contract
• Types: Added contract_address to all Row/Insert/Update types
• Indexer inserts: All 6 routes stamp contract_address: STORY_FACTORY.toLowerCase()
• Frontend queries: All reads filter by .eq("contract_address", STORY_FACTORY.toLowerCase())
• 17 files changed across migration, types, indexers, pages, components, and ranking

Test plan

• Run migration on Supabase
• Existing data tagged with old contract address
• New storyline → contract_address matches current STORY_FACTORY
• Home page only shows current contract's data
• Story pages filter correctly
• Writer/reader dashboards filter correctly
• Ratings, comments, views all scoped to contract
• npx tsc --noEmit passes (verified)

Fixes #233

🤖 Generated with Claude Code

[project7-interns]

Verdict: REQUEST CHANGES

Summary

Most read/write paths were updated for contract_address, but the cron backfill path still writes storylines, plots, and donations without stamping the new column. That leaves a correctness gap in the indexing pipeline and breaks the multi-contract isolation this PR is supposed to establish.

Findings

• [high] Backfill route still inserts rows without contract_address
  • File: src/app/api/cron/backfill/route.ts:210
  • File: src/app/api/cron/backfill/route.ts:234
  • File: src/app/api/cron/backfill/route.ts:271
  • File: src/app/api/cron/backfill/route.ts:302
  • Suggestion: stamp contract_address: STORY_FACTORY.toLowerCase() on every backfill upsert, just like the live indexer routes. Right now these inserts rely on the DB default, which this migration intentionally changes to ``, so any reindexed/backfilled rows will be written unscoped and then disappear from the newly filtered frontend queries.\n\n### Decision\nRequesting changes because #233 is an infra isolation fix, and leaving the backfill pipeline untagged would keep producing rows that violate the new contract-scoping model.

[project7-interns]

Verdict: APPROVE

Summary

The follow-up change fixes the remaining correctness gap by stamping contract_address on all cron backfill inserts, bringing the backfill path in line with the live indexers and the new frontend filtering model. The multi-contract isolation work now looks internally consistent across migration, types, reads, live writes, and backfill writes.

Findings

• None.

Decision

Approving because the previously blocking backfill hole is resolved and GitHub lint-and-typecheck passes on the updated head.