feat: rebrand IdeaScape as ControlProof

[Bots]

Summary

• rebrands the public product from IdeaScape to ControlProof, a name centered on explicit control boundaries and reproducible security proof
• updates the browser title, favicon, global header, homepage, authentication, profile, bounty editor, pilot, admin, README, plan, and project-status surfaces
• replaces remaining map-pin brand marks with the ControlProof shield while retaining the established black, bone, neutral, and #ff5a1f visual system
• adds focused regression assertions for the ControlProof name and rejects stale IdeaScape branding on major rendered surfaces

Compatibility boundaries

• keeps the Bots/ideascape repository, current deployment URL, routes, package name, Supabase project reference, migrations, RPC/function names, storage keys, and historical documentation paths unchanged
• makes no database or persisted-data changes
• preserves private/reversible reviewer signals, aggregate-only evidence, authorization requirements, no-payment language, and all existing RLS boundaries

Verification

• npm run check — 202/202 frontend tests
• npm run format:check
• npm run build
• npm run test:e2e — 4/4 Playwright flows
• git diff --check
• static scan: no added secrets, dangerous execution patterns, or debug statements
• desktop and 390px mobile visual QA
• no horizontal overflow, broken images, browser errors, or stale IdeaScape branding on the verified homepage
• independent fail-closed staged-artifact review

Rollout note

This PR intentionally changes the public brand only. Repository, deployment, database, auth, and compatibility identifiers can be renamed later through separate reviewed migrations if desired.

[vercel]

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

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