🧪 SurroundShow — Pair Test Plan

Draft pair-test plan for SurroundShow. Flows were auto-drafted from the project page — review and edit the steps before running the session. Two testers: the agent and Mike execute the same steps, compare results, and file GitHub issues for every mismatch.

Protocol Environments Flows Results
Draft plan. The flows below were generated from the project page — treat them as a starting checklist, edit freely before the session.

How this session works

  1. Agent executes a step in a real browser, posts screenshots to the Discord thread, and states pass/fail.
  2. Mike repeats the same step with his own accounts and data.
  3. Compare. Same result → check the box in the log. Different → both re-run once, then file an issue.
  4. File a GitHub issue for every wanted change (conventions below) and link it in the step’s issue box.

Issue conventions

Environments & test data

Repomicrospaces/linkall
SessionsAgent uses fresh browser profile + generated test data; Mike uses his real accounts with plus-tagged emails so records stay filterable.

Flows (draft)

A1Agent Stages landing — brand hero + stage cards (HomeShow, Halloween, Christmas, New Year, Wedding Ceremony, Wedding Reception, Bar Loco), each a themed show space.
Expect: same result for both testers — screenshot the end state.
A2Mike Repeat A1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.
B1Agent Venue module — /venue settings plus places (booths/tables) with guest place claim.
Expect: same result for both testers — screenshot the end state.
B2Mike Repeat B1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.
C1Agent Mobile order tab — guest key (UUID in localStorage), /order binds the guest to a claimed place; /bar serves Bar Loco tickets.
Expect: same result for both testers — screenshot the end state.
C2Mike Repeat C1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.
D1Agent Community — groups (state/county kinds from the legacy §-prefixed groups), feed with posts/replies/upvotes, people, events, marketplace.
Expect: same result for both testers — screenshot the end state.
D2Mike Repeat D1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.
E1Agent Brand registry — @linkall/brands is the single source of truth for identity, nav, theming, and feature flags; per-route layouts keep show pages chrome-free.
Expect: same result for both testers — screenshot the end state.
E2Mike Repeat E1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.
F1Agent Legacy SiteId column + domain→site middleware → each brand is its own Convex deployment; no tenant filtering anywhere.
Expect: same result for both testers — screenshot the end state.
F2Mike Repeat F1 with your own account/data — compare against the agent’s result.
Expect: identical behavior; file an issue on any mismatch.

Results log

Empty — fill in during the session: step id, pass/fail per tester, issue links.

StepAgentMikeIssue
————