# Permission message comparison

Both apps run from separate checkouts with fresh T3 homes, T3CODE_DEV_SEED=0 and T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0. Start each with `vp run dev --no-seed`. Add one empty synthetic workspace using `node apps/server/src/bin.ts project add <workspace> --title demo --base-dir .t3`. Pair the browser using `node apps/server/src/bin.ts pair --base-dir .t3`, wait for sign-in, then open `/settings/access`. No model turn is needed for Settings.

Browser: Chromium, Linux, 1280x800 CSS pixels, device scale factor 2, light theme, English. The environment heading is masked with CSS for privacy; the permission messages are untouched. Base and head have one client and no unused pairing links.

Evaluate permission-driver.js only after Settings is fully loaded. It uses the app's own setEnabled command for connection changes. It holds or modifies only GET /api/auth/session responses to make the pending, failed and rejected displays inspectable; these are controlled response fixtures, not evidence of an actual server rejecting authentication. All other HTTP and WebSocket traffic reaches the real server.

Start recording after the driver completes. Capture each state below with two screenshots 500ms apart, retain only once their bytes match:

1. The driver disconnects and opens Permissions: Connect to this environment to view this session’s permissions.
2. `await permissionProof.connect(true)`; wait with `permissionProof.wait('Checking permissions…')`; capture pending.
3. `permissionProof.setMode('failed')`; wait for Could not verify your permissions. Retrying automatically.; capture.
4. `permissionProof.setMode('rejected')`; wait for This environment did not accept your session. Reconnect to try again.; capture.
5. `await permissionProof.connect(false)`; wait for Connect to this environment to view this session’s permissions.; capture. This follows a rejection and demonstrates the disconnected display replacing it.
6. `permissionProof.setMode('real'); await permissionProof.connect(true)`; wait for These permissions apply to this client’s current connection.; capture the real granted-permissions list.

Stop recording. Repeat the same driver and sequence on the other commit. The attached base and head recordings show this sequence. The permission messages and grants are identical. Local development ports differ.

The UI computes rejected only when failed is false. Therefore the unit test's simultaneous failed=true/rejected=true input, and disconnected with both flags true, cannot be demonstrated through this screen. Automated test coverage itself is not visible in the app. No unit test result is used as visual evidence.
