๐Ÿงฑ Agent Version-Anchor ยท #2600 (P3 ยท approach A)

Agents have no pin mechanism โ€” so they must not snapshot upstream Labs versions at all. The skill is the single source of truth; agents reference it. A guard makes that stick.

โœ‚๏ธ What changed โ€” thin the snapshot, keep the feature

before โ€” agents pinned versions

### Network Control (v0.13)
### Semantic Locators (v0.16+)
### Auth Vault & Domain Control (v0.15-v0.29)
# emulate-engineer.md
via Vercel emulate 0.7+
## Service Ports (v0.7.0 โ€” 13 providers)

after โ€” feature stays, version defers

### Network Control
### Semantic Locators
### Auth Vault & Domain Control
> commands & flags live in the
> browser-tools skill (source of truth)
## Service Ports (13 providers) โ† list intact
6 agents thinned (29 version tags removed), all keep their features + commands:

๐Ÿ›ก๏ธ The closed loop โ€” 3 layers, click to see what each catches

โš™๏ธ The new guard

$ node tests/skills/structure/test-agent-no-version-snapshot.mjs
  Passed: 37 agents  Offenses: 0
  SUCCESS: no agent hardcodes a Labs-package version snapshot
Flags any (v0.XX) tag or agent-browser/emulate/portless next to a version in src/agents/*.md (skips the generated README.md). Wired into npm run test:skills. A future agent that re-snapshots a version fails CI.