fix: separate pilot readiness generations

[Bots]

Summary

• fixes pilot readiness so one reviewer cannot be counted multiple times across historical and active validation-question generations
• counts distinct current reviewers only when they select ready-for-authorized-test
• keeps suitable-project evidence pinned to the original contribution question and counts distinct respondents
• updates owner-facing threshold copy from generic participant responses to ready reviewers
• ships the correction as a new forward-only migration because PR feat: recast IdeaScape as an authorized bounty network #13 has already merged

Regression

• a fixture gives one profile both a historical project response and an active readiness response
• the owner summary must report one ready reviewer and one suitable-project response
• the upgrade probe replays the merged recast twice and the forward fix twice before asserting the separated counts

Verification

• npm run check — 202 tests passed across 32 files; typecheck and Biome lint passed
• npm run format:check — passed
• npm run build — passed
• npm run test:e2e — 4 Playwright tests passed
• npx supabase db reset — passed and applied 20260813203034_fix_pilot_readiness_generation_counts.sql
• npx supabase test db — 244 pgTAP assertions passed
• focused pilot pgTAP — 56/56 passed
• npx supabase db lint --level warning — no schema errors
• transactional upgrade/replay probe — passed with both migrations replayed twice
• fail-closed independent review — no blocking errors

Security and privacy

• creator/operator authorization remains unchanged
• function remains SECURITY DEFINER with an empty search_path
• output remains aggregate-only and exposes no respondent identities
• the merged migration is not rewritten; correction is forward-only

Deployment note

• production serves the merged authorized-bounty frontend, but the public pilot plan still returns the pre-recast database title Project Time Capsule pilot
• this indicates frontend/database migration drift; deploy the pending Supabase migrations through the reviewed database path rather than inferring migration success from Vercel

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ideascape	Ready	Preview	Aug 13, 2026 8:39pm