ACP background working-directory evidence

Environment: Linux x86_64, Node v26.12.1. Real bundled T3 server (t3 serve),
not an imported service or test harness. Each commit is built in its own checkout
with vp i and vp run --filter t3 build:bundle. Both use fresh isolated databases,
T3CODE_DEV_SEED=0, and identical generated data. No developer data is copied.

Base: 871b00907d0bcf2705224de6c6e90de925c7cbb9
Head: fcd048712d1dc00b2b0f4c47dbc0746bafc55565

Put the scripts in a scratch directory. Run:
  headless-desktop ./record.sh <base-checkout> before <scratch-directory>
  headless-desktop ./record.sh <head-checkout> after <scratch-directory>

record.sh records the real terminal while drive.mjs runs. Uploaded recordings
are cropped identically to the terminal rectangle (1408x810 from 1920x1080),
using ffmpeg -vf crop=1408:810:0:0. Terminal theme is light on both sides.
Private paths are replaced at output time with the documented role aliases.
Recordings were inspected across the sequence before upload.

The driver starts the actual built CLI in a synthetic home with 64 directories,
creates Local ACP configuration using Settings' server.updateSettings RPC,
refreshes the provider, requests sign-in, then adds a project and starts a thread
using the actual project/thread CLI. This exercises real RPC, provider registry,
ACP subprocesses, persistence and orchestration. It does not simulate T3 internals.

indexing-agent.py is a DISCLOSED SYNTHETIC ACP agent, not Empryo. It implements
minimal successful ACP initialize/authenticate/session/new/session/prompt replies.
On startup it recursively opens actual Linux inotify watches under process.cwd.
It reads its own /proc/<pid>/cwd and /proc/<pid>/fdinfo/<fd> and writes these
observations on ACP requests. Proc observations include those real fdinfo entries.
The path aliases do not change the directory classification or watch counts.
The per-run source logs remain private; uploaded JSON is sanitized synthetic data.

Observed on base: background status and sign-in cwd=SYNTHETIC_HOME, 65 watches.
Observed on head: background status and sign-in cwd=BACKGROUND, 1 watch.
Observed on both: thread process cwd=PROJECT, session cwd=PROJECT, 1 watch;
thread session/prompt received. Project and thread CLI commands exited 0.

Limits: no actual Empryo, inotify exhaustion/ENOSPC, or systemd unit was exercised.
This demonstrates the erroneous cwd and excess directory watches, and their fix,
without exhausting a shared kernel resource. Relative executable anchoring,
Windows paths, registry npx/uvx distributions and real third-party OAuth were
not exercised. No tests are offered as evidence.

AI-assisted; verified with the tests and tools listed above.