Manual browser driver (same actions on both commits)

Environment: Linux web dev app, Chrome, 1280 x 800 CSS pixels, device scale 2, light theme. Each commit has its own fresh T3 home and synthetic git project. Enable Claude using the machine's existing proxy configuration privately; do not publish credentials. No Claude turn is sent.

1. Run seed-skills.py with administrator privileges and a private personal-config directory argument. This installs managed-only and deploy under /etc/claude-code/.claude/skills and a same-name personal deploy under the argument's skills directory.
2. Set CLAUDE_CONFIG_DIR to that personal config directory and T3CODE_DEV_SEED=0. Start each checkout with `vp run dev --home-dir .t3/manual -- --host 127.0.0.1`. Set T3CODE_AUTO_BOOTSTRAP_PROJECT_FROM_CWD=0 to avoid an extra default project.
3. Run seed-app.py with the checkout as its sole argument. It creates a project and one free replay turn using the app CLI.
4. Pair the shared preview browser using the server's startup link, then navigate directly to the seeded thread's environment/thread URL after sign-in completes.
5. Hide the thread details panel to keep machine labels out of captures. Choose Claude, then Claude Haiku 5.5, then press Escape to close the model/effort picker.
6. Start recording. Click the composer and type `$managed`. Read the menu. Base shows “No skills found. Try / to browse provider commands.”; head shows “managed-only — MANAGED-ONLY skill installed by administrator”. Capture two screenshots at least 500 ms apart and compare pixel equality before retaining a still.
7. Ctrl+A in the composer, then type `$dep`. Read the menu. Base shows “PERSONAL deploy skill (user copy)”; head shows “MANAGED deploy skill (org-enforced copy)”. Capture a stable still as above. Stop recording.
8. On head, clear the composer, type `$managed`, click managed-only, and capture the inserted skill chip. Base cannot perform this selection because no matching skill exists.
