FunFirst Loco — Pair Test Plans

Protocol Brand matrix The five plans X · Cross-brand isolation

How a session works

Pick a plan below and open its doc — every step, expected result, brand data value, and results log lives there.
Agent executes a step in a real browser against the live app, posts screenshots to the Discord thread, and states pass/fail.
Mike repeats the same step with his own shows/performances, posting his screenshots to the thread.
Compare. Same result → check the box in that plan's log. Different result → both re-run once, then file an issue.
File a GitHub issue for every wanted change: [pair-test FLOW<STEP>][brand] short summary in microspaces/linkall, label pair-test, one behavior per issue. Body: environment (prod domain + route), expected vs actual, screenshot links, tester.

Evidence conventions

Agent screenshots: posted in the Discord thread via MEDIA: and committed under test-screenshots/pair-test/ on the session branch.
Every step in each plan has an Agent row and a Mike row. Both = same action, own data.
Test data marker across all brands: only create PairTest <who> …-titled shows/performances; never rename or re-cue seeded shows. Every plan ends with a cleanup checklist.

Brand matrix

	Battle Loco	Wrestle Loco	Comedy Loco	Bar Loco	Wedding Loco
Plan	battle-loco	wrestle-loco	comedy-loco	bar-loco	wedding-loco
Mode	competition	competition	competition	setlist	setlist ×2 (ceremony + reception)
Teams	Heat / Ice	Faces / Heels	Banana Peels / Comedy Clubtrotters	Naughty / Nice (nominal)	Bride / Groom (nominal)
Rounds	18	33	12	12	12 + 14
Console host	funfirst.fun	funfirst.fun	funfirst.fun	surroundshow engine	app.weddingloco.com
Convex deployment	funfirst	funfirst	funfirst	surroundshow	⚠ pin it live (D1)
Seeder	battleLocoLuxor	wrestleLocoLuxor	comedyLocoLuxor	barlocoHolidays	weddingShows
Seeded show(s)	Luxor Oct 17 (22 scenes)	Luxor Night 1 (28)	Luxor Night 1 (28)	Halloween / Jingle / Big L♥ve	Chapel (22) / DJ (26)
Marketing site	battleloco.com	wrestleloco.com	comedyloco.com	bar-loco.vercel.app (barloco.com parked)	weddingloco.com

Suggested order: Battle → Wrestle → Comedy (same engine, one deployment, competition mode) → Bar (setlist + surroundshow deployment) → Wedding (two locos + the deployment-pin check).

The five plans

🥊 Battle Loco

Heat vs Ice on funfirst. 18-round card, Punishment overlay, Luxor Oct 17 seeded show, scoring + winner-cue contract.

🤼 Wrestle Loco

Faces vs Heels on funfirst. 33-round card (five 3-round matches), Ring overlay, crowd refs, Luxor Night 1.

🍌 Comedy Loco

Banana Peels vs Comedy Clubtrotters on funfirst. 12 scored games, the winner-name/nickname regression case.

🍸 Bar Loco

Setlist mode on surroundshow. Jingle-Bar-style night loop (sets → games → prize time), month-long performances, swap-in bits, launch-site copy checks.

💍 Wedding Loco

Ceremony chapel + Reception DJ on app.weddingloco.com. Theme packs, the ceremony→reception handoff, couple isolation, deployment pin.

Flow X · Cross-brand isolation (run after any two plans)

One codebase — and, for Battle/Wrestle/Comedy, one Convex deployment — serves all brands. Leakage here is a critical finding: the loco equivalent of Around Town's cross-town check.

X1BothOpen two brands' console + wall side by side (e.g. Battle vs Comedy; Mike: Wrestle vs Battle). Cue a scene in one brand only.

Expected: the other brand's wall/performance does not react. Any cross-brand cue, scene, or performance leak is a stop-and-file.

X2AgentHit the brand marketing domains fresh: correct hero/brand accent/nav everywhere; <domain>/performances lists only that brand's performances; legacy <domain>/<slug>/performances 308s to the clean URL with the query string preserved.

Expected: zero brand mixing; redirects preserve method + query string.

X3AgentOn funfirst.fun, walk the locos listing and each brand's nav (Shows, Designer, Player, Preview, Locos).

Expected: every loco listed with the right blurb; all links resolve; no cross-brand copy ("Heat vs Ice" must never appear on wrestleloco.com).

X4BothSign out. As visitors, open each brand's performance/designer routes.

Expected: marketing pages render; engine surfaces gate to sign-in (Convex auth); no console actions reachable unsigned.