# Pi notification severity reproduction

Run each revision in its own checkout with dependencies installed and a fresh .t3 directory. Use the same notify-test.ts extension on both sides.

Enable only the Pi provider instance in .t3/userdata/settings.json. Its config has binaryPath "pi" and launchArgs "--no-extensions -e <absolute path to notify-test.ts>". Disable Codex, Claude, Cursor, Grok, Muse, OpenCode and Antigravity. No live database was copied.

Start the real application:

```sh
T3CODE_DEV_SEED=0 vp run dev
```

Seed and execute through the running server's public CLI:

```sh
node apps/server/src/bin.ts project add . --title 'Pi notification proof' --base-dir .t3
node apps/server/src/bin.ts thread start . /notify-test --title 'Pi notification severities' --provider pi --model anthropic/claude-haiku-5-5 --json --base-dir .t3
```

Pair the browser with the startup pairing link, obtain the environmentId from /.well-known/t3/environment, then open /<environmentId>/<threadId>. Hide the thread details panel. Reload that thread on both revisions. The screenshots show the persisted rows after reload.

Environment: Linux web client, Chromium preview browser, 1280x800 CSS viewport (2560x1600 screenshot pixels), light theme, Pi / Claude Haiku 5.5. No model generation is needed: the real Pi extension command directly emits info, warning and error notify RPC events.

Base: 82479522cb667e09616a04705648ac4fab68b997. All three rows have orange text and circle-alert icons.
Head: cba786e8c4c7c26bb932cb74ab3bcd0d458596db. Info has neutral text and a muted zap icon; warning and error retain orange warning styling.

Each final screenshot was visually inspected and matched a second screenshot taken more than 500 ms apart pixel-for-pixel after blurring the empty composer to stop its caret blinking.

persisted-notices.json contains only synthetic type/message/level fields extracted with read-only SQLite connections. Base has no level fields; head retains info/warning/error. pi-rpc-notify.jsonl independently captures the extension's real Pi RPC notifications.

The scenario runner was not used because its replay provider speaks generic ACP and cannot exercise the Pi notifyType boundary.
