# Composer footer reproduction

For each checkout, install dependencies with `vp i`. Run `python3 seed.py "$PWD"`
from the checkout before starting its server. This creates synthetic state only
and replaces the free replay showcase transcript with a 61-item file list.

Start `T3CODE_DEV_SEED=0 T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0 vp run dev --home-dir "$PWD/.t3/evidence"`.
Wait for the server to listen. Then populate through the real CLI:

```sh
node apps/server/src/bin.ts project add "$PWD/.t3/evidence/workspaces/workspace-review" --title workspace-review --base-dir .t3/evidence
node apps/server/src/bin.ts thread start "$PWD/.t3/evidence/workspaces/workspace-review" 'Review the workspace and finish with file paths.' --title 'File review' --provider devReplay --model showcase --wait --json --base-dir .t3/evidence
```

Open the startup pairing link in the Browser panel and wait until the signed-in
app renders before navigating. Use a 1280x800 CSS-pixel viewport, light theme,
and the same browser on both sides. In Appearance > Advanced enable
“Keep composer context visible in active threads”. Return to the app, open
“File review”, and close the thread details panel.

Start recording and execute the scroll portion of browser-driver.js. Capture
footer overlap only after two PNG captures at least 500ms apart are identical.
Click the real Scroll to end control and capture again with the same stability
check, then stop recording. No application rendering code or CSS is changed.

Observed on base: review-file-56.ts overlaps Local checkout, and
review-file-57.ts shows in the bottom gap. On head both are covered by the fade.
At scroll end on both commits the final bullet ends at 563.695 CSS pixels and
the composer begins at 636.5 CSS pixels, leaving 72.805 pixels of clearance.

The workspace is local; a remote connection and the desktop shell were not tested.
AI-assisted; verified with the tests and tools listed above.