[CodeWithEugene]

Summary

Dispute wait enforced on the server

• services/legacy/dispute-window.ts: one rule (14 days after winners are announced, plan §10.5) used by both the winnings page button and openMilestoneDispute, which now refuses early requests with TOO_EARLY and the date disputes open. Previously only the UI hid the button.

Trust bonus removed

• Deleted the unused payoutExcellenceDelta helper and its test; the 48 Hour Media Standard post no longer claims fast payouts add a point.

New Prize Verified hackathon alert

• The existing "prize locked" email went only to registrants, but registration opens when the prize locks, so it never reached anyone.
• New hackathon.announce job (lib/events/announce.ts) emails verified builders (DEVELOPER role) with hackathon updates on, plus an in-app notification. Skips opted-out builders, the host organization's team, demo/test accounts, unverified emails and demo hackathons. The in-app row doubles as the "already told" marker, so a retried job never emails twice.
• services/escrow/deposits.ts only gains one best-effort enqueue after the money state commits, next to the existing attestation enqueue; the fan-out runs off the webhook path.

robots.txt content signals

• app/robots.ts replaced by app/robots.txt/route.ts + lib/seo/robots.ts so it can carry Content-Signal: search=yes, ai-input=yes, ai-train=yes (Cloudflare's managed robots.txt is now off). Same allow/disallow rules and sitemap line.

Test plan

• Unit: dispute window, robots.txt output; integration: early dispute refused, announcement recipients, no double send, demo hackathon never announced
• pnpm test 332 passing, lint, typecheck, production build
• After deploy: live robots.txt shows the Content-Signal line