# Azure DevOps group labels: real web client proof

Environment for both Settings captures: Linux, Chromium web client, `vp run dev`, dark theme, 1440 x 1000 CSS pixels (device pixel ratio 2). Separate base/head worktrees and fresh databases, started with `T3CODE_DEV_SEED=0`. No tests used as evidence.

1. Run seed.py with a synthetic-fixture directory and the head checkout as arguments. It creates two local clones each for HTTPS and SSH, sets Azure DevOps remotes, and adds all four with the real project CLI and default titles.
2. Add the same four fixture paths to the base with `node apps/server/src/bin.ts project add --base-dir .t3 <path>` for each checkout.
3. Remove the automatically bootstrapped `apps/server` project on both sides with `project remove --base-dir .t3 --force <path>`.
4. In Settings > General, enable Project grouping on both sides. Open the sidebar project filter, then Settings > Projects.
5. Wait for two identical screenshots at least 500 ms apart before each still. Compare images byte-for-byte.

Observed base: Settings renders `example-org/My%20Project/_git/my-repo` and `MyRepo`. The sidebar renders the same HTTPS value truncated and SSH `MyRepo`.
Observed head: Settings and sidebar render `My Project/my-repo` and `MiXeDProject/MyRepo`.

Published Settings images are identically resized and cropped from stable screenshots. Synthetic local checkout path subtitles are visibly redacted; labels are untouched. The original screenshots were visually inspected before processing, and the processed images were inspected before upload.

The local clones avoid needing a real Azure DevOps account; no network clone or Azure DevOps credentials were used.