feat(pco): Psychic Consensus Oracle Frontend UI [Innovation Cycle 48]

[Eli5DeFi]

Summary

This PR ships the complete frontend implementation of the Psychic Consensus Oracle (PCO), the flagship feature from Innovation Cycle #48.

The smart contract, TypeScript client, and types were already built. This PR adds the missing UI layer — connecting everything into a production-ready betting experience.

---

The Two-Layer Prediction Market

Layer 1 — Story Bet (unchanged parimutuel):

• Pick which AI choice wins (A/B/C)
• 85% of pool to winners, standard parimutuel math

Layer 2 — Psychic Oracle (NEW):

• Crowd Believer → bet the majority is correct (standard payout)
• Contrarian Psychic → bet the crowd is WRONG (2× bonus payout)
• ELO-style scoring: SEER → ORACLE → PROPHET → VOID SEER
• Fee discounts at higher tiers (ORACLE: -0.5%, PROPHET: -1%, VOID SEER: -2%)
• Psychic Edge live signal (3× = Extreme Contrarian, 2× = Strong, etc.)

---

Files Changed

New Files

File	Description
hooks/usePsychicOracle.ts	wagmi hook — reads pool, odds, consensus, user positions, profile; handles all writes
components/psychic/PsychicConsensusPanel.tsx	Main 2-layer panel (tabs: Story Bet / Psychic Oracle)
components/psychic/PsychicLeaderboard.tsx	ELO leaderboard with badge tiers and rank medals
components/psychic/index.ts	Barrel export
api/psychic/leaderboard/route.ts	REST endpoint — on-chain batch reads + mock fallback for dev
api/psychic/pool/[poolId]/route.ts	REST endpoint — full pool state from chain
migrations/20260218_add_pco_fields/migration.sql	Adds pcoContractAddress + pcoPoolId to betting_pools

Modified Files

File	Change
story/[storyId]/page.tsx	Conditionally renders PsychicConsensusPanel (PCO) or BettingInterface (legacy) based on pool config
schema.prisma	Added pcoContractAddress and pcoPoolId fields to BettingPool
.env.example	Added NEXT_PUBLIC_PCO_ADDRESS, NEXT_PUBLIC_CHAIN_ID, NEXT_PUBLIC_RPC_URL

---

Design System

All components follow the Ruins of the Future aesthetic:

• Dark glass-morphism cards (glass-card className)
• Gold / drift-teal / void-gray palette
• Framer Motion animations (tab switches, choice selection, badge progress)
• Mobile-first responsive (stacks on mobile, sidebar on desktop)
• Real-time countdown with urgency states (green → yellow → orange → red pulsing)
• Skeleton loading states throughout

---

Testing Checklist

• TypeScript compiles (0 errors in new files)
• Layer 1 choice selection + amount input + bet button flow
• Layer 2 psychic side selection + amount input + bet button flow
• Countdown timer updates every second with urgency color changes
• Psychic Edge signal renders correctly for all edge values
• Badge progress bar animates from current → next tier
• Mock API fallback returns data when PCO contract not deployed (dev mode)
• Leaderboard API handles empty DB gracefully
• End-to-end with deployed PCO contract (needs testnet deployment)
• Mobile layout verified (needs browser testing)

---

Deployment Notes

1. Run the DB migration

# Apply the SQL manually or via prisma migrate deploy
cd packages/database
pnpm exec prisma migrate deploy
# If shadow DB issue persists, apply migration.sql directly:
psql $DATABASE_URL -f prisma/migrations/20260218_add_pco_fields/migration.sql

2. Add environment variables

# After deploying PsychicConsensusOracle.sol to Base Sepolia:
NEXT_PUBLIC_PCO_ADDRESS=0x<deployed-address>
NEXT_PUBLIC_CHAIN_ID=84532
NEXT_PUBLIC_RPC_URL=https://sepolia.base.org

3. Enable PCO for a betting pool

UPDATE betting_pools
SET "pcoContractAddress" = '0x<deployed-contract>',
    "pcoPoolId" = '1'  -- on-chain pool ID
WHERE id = '<pool-db-id>';

4. For new chapters, set both fields when creating the pool

The story page checks pool.pcoContractAddress — if set, it renders the PCO panel. Otherwise it falls back to the legacy BettingInterface. Zero breaking changes for existing pools.

---

Architecture Decision

Why conditional rendering instead of replacing BettingInterface?

Existing deployed pools use the old contract. PCO is a new contract deployment. The conditional approach lets us:

1. Ship PCO to new chapters immediately
2. Keep existing chapters working without data migration
3. Migrate pools gradually (or never — both coexist fine)

---

Related

• Innovation Cycle 48 proposal: INNOVATION_CYCLE_48_FEB_17_2026.md
• Smart contract: packages/psychic-oracle/src/PsychicConsensusOracle.sol (already merged)
• Client SDK: packages/psychic-oracle/src/client.ts (already merged)