# Active terminal prevents automatic settlement

Place `active-terminal-prevents-auto-settle.e2e.ts` in `scripts/scenarios/` of a current main checkout with dependencies installed. Save `clock.cjs` beside this guide.

```bash
export SCENARIO_CLOCK_FILE="$PWD/offset"
printf 0 > "$SCENARIO_CLOCK_FILE"
export NODE_OPTIONS="--require=$PWD/clock.cjs"
export T3CODE_DEV_SEED=0
export T3_SCENARIO_INHERIT_ENV='NODE_OPTIONS,T3CODE_DEV_SEED,SHELL,SCENARIO_CLOCK_FILE'
vp run scenarios:prove scripts/scenarios/active-terminal-prevents-auto-settle.e2e.ts \
  --base 068332c603ce5ca40ad5a96a09cffa34ebd05dff \
  --head 4a81dc549b88eb06caf70b450ffe954f4966d4a8
```

Both sides run the real web client and server on fresh isolated data, with a completed Replay agent turn and a real Node HTTP server running in the integrated terminal. The helper advances only server/CLI wall-clock reads by four days; the browser and scenario runner keep real time. Enabling a one-day auto-settle period invokes the normal settings-change settlement sweep. No database rows or application source files are changed. The assertion checks that the Settled shelf remains empty.

Environment: Linux, headless Chromium, 1280×800, light theme. This demonstrates the common server settlement behavior; Windows-specific subprocess inspection was not exercised. Automatic settlement after stopping the application was not exercised.
