Skip to content

Visual investigation index ​

Final adversarial review revisited all75 original PNGs through review-sheet-1.jpg…review-sheet-10.jpg plus DOM/source evidence. Contact sheets are review derivatives, not new runtime captures. Main desktop /book-call and /audit-unknown-route initial images are blank (DOM headings absent); use mobile404 captures/source for design evidence and require fresh implementation404 captures. Do not infer desktop404 visual fidelity from HTTP status alone.

Captured from isolated pinned main/dev runtimes. Default images: Chromium desktop 1440×1000, mobile 390×844, reduced motion, light color scheme; public browser network outside localhost blocked. This intentionally exposes external-widget fallbacks and is not provider availability testing. All 62 captures completed; route statuses and browser/DOM evidence are in capture-results.json.

No authenticated account, private report bearer token, real application, contact message or booking was used. Cookie banner remains visible in most initial shots; normal-motion supplement rejects the banner to expose the page. Initial dev shots may leave observer-driven sections unrevealed; use the revealed images below for full-page comparison. Under reduced motion main's phone can be blank because source omits a poster.

Normal-motion and interaction references ​

Route and state screenshots ​

BranchViewportRouteHTTPScreenshot / additional state
maindesktop/200page
maindesktop/?audience=creators200page
maindesktop/campaigns200page
maindesktop/campaigns/forgegui200page
maindesktop/campaigns/kill-streak200page
maindesktop/services200page
maindesktop/contact200page
maindesktop/careers200page; role dialog
maindesktop/clipping200page
maindesktop/creators200page
maindesktop/creators/apply200page
maindesktop/creators/start200page
maindesktop/creator-guides200page
maindesktop/creator-guides/roblox-clipping200page
maindesktop/privacy200page
maindesktop/terms200page
maindesktop/login200page
maindesktop/book-call404page
maindesktop/audit-unknown-route404page
mainmobile/200page; menu open
mainmobile/?audience=creators200page
mainmobile/campaigns200page
mainmobile/campaigns/forgegui200page
mainmobile/campaigns/kill-streak200page
mainmobile/services200page
mainmobile/contact200page
mainmobile/careers200page; role dialog
mainmobile/clipping200page
mainmobile/creators200page
mainmobile/creators/apply200page
mainmobile/creators/start200page
mainmobile/creator-guides200page
mainmobile/creator-guides/roblox-clipping200page
mainmobile/privacy200page
mainmobile/terms200page
mainmobile/login200page
mainmobile/book-call404page
mainmobile/audit-unknown-route404page
devdesktop/200page
devdesktop/campaigns200page
devdesktop/campaigns/forgegui200page
devdesktop/services200page
devdesktop/contact200page
devdesktop/book-call200page
devdesktop/creator-guides200page
devdesktop/privacy200page
devdesktop/terms200page
devdesktop/login200page
devdesktop/creators404page
devdesktop/careers404page
devmobile/200page; menu open
devmobile/campaigns200page
devmobile/campaigns/forgegui200page
devmobile/services200page
devmobile/contact200page
devmobile/book-call200page
devmobile/creator-guides200page
devmobile/privacy200page
devmobile/terms200page
devmobile/login200page
devmobile/creators404page
devmobile/careers404page

Visual findings ​

Main uses sharply separated blue/orange/ink/cream bands, chunky outlined title stickers and hard shadows; dev baseline has softer cream/blurred lighting, blue action accents and a different section hierarchy. Main brand homepage is substantially longer and proof-led. The phone appears only from 1024px; desktop nav appears from 768px. Services uses local video posters successfully even with external resources blocked. Main /contact uses the calendar fallback while its browser script is blocked. Main /book-call renders branded 404, while dev still renders its old scheduler.

There were no captured horizontal overflows or page exceptions, which does not prove all interactions accessible. Focus trapping, account flows, provider error contracts and production behavior remain in the implementation acceptance plan. Screenshots do not authorize copying main's stale root, finance or legal implementation.