# Reaction failure proof

Both commits ran unchanged in real clients against fresh isolated databases with synthetic demo/reactions GitHub data. The server fetch fixture replaces only GitHub responses; it does not change client state, rendering, RPC or reaction code.

Web: Chromium, 1280x800 CSS pixels, DPR 2, light theme. Open the synthetic PR in its workspace panel, use the comment reaction pill (the web description has no reaction bar). Click thumbs-up three times: add, remove, add. The server serializes mutations, so only the first reaches the fixture while newer mutations queue. After the pill shows selected 2, create the fixture's fail-oldest marker. The oldest request fails while newer requests stay unresolved. Base becomes unselected 1; head stays selected 2. The failure stills were checked against a second capture 500 ms apart: zero differing pixels. Detail images are crops of those full stills. Browser lacks a thumbs-up glyph; counts and selected border remain visible. Videos show the complete three-click sequence.

iOS: pooled iPhone simulator, 402x874 logical screenshot, light theme, native development client. The uploaded one-test scenario uses the PR-description pill and the same three taps, then fails the oldest request and dismisses its error alert. Both latest-choice screenshots show selected 2. After failure, base shows unselected 1 and head selected 2. scenarios:prove reports failsOnBase=true and passesOnHead=true. Recordings were trimmed to the PR interaction, excluding installation and connection setup. Automatic 003-failure.png is omitted as redundant evidence.

For replay, put the uploaded scenario under scripts/scenarios and run scenarios:prove from current main with the two stated commits. Set actionTimeout:120_000 in scripts/e2e.config.ts because cached iOS installation exceeded the default 30 seconds. Start with T3CODE_DEV_SEED=0, GH_TOKEN=synthetic-reaction-fixture, NODE_OPTIONS=--import=<absolute path to share-github-fixture.mjs>. The fixture/scenario default to /tmp/reaction-proof; create it first. Inherit GH_TOKEN,NODE_OPTIONS,T3CODE_DEV_SEED through T3_SCENARIO_INHERIT_ENV alongside the pool credentials required by the runner. For web, start each commit with scripts/scenarios/start-app.ts and run share-seed.mjs <isolated T3 home> <server port> from that checkout. Synthetic seed data only; no real accounts or databases.
