AGENTS.md: the dependency lockstep bullet and the npm test annotation are stale

[cliffhall]

Found while writing the knowledge skills (#4872, PR #4921). Two statements in AGENTS.md no longer match the repository, and AGENTS.md says of itself that every rule in it is true of the repository as it stands.

1. Dependencies: the shared-devDependency bullet contradicts the guard

AGENTS.md → Dependencies says:

When you bump a devDependency that several TypeScript workspaces declare (typescript, vitest, @vitest/coverage-v8, @types/node, …), bump it in every workspace that declares it. Their ranges already differ; do not widen the skew.

Since #4864, npm run verify:dep-lockstep (in validate:guards, so in CI) fails when two declarations of a package in SHARED_DEV_DEPENDENCIES (typescript, vitest, @vitest/coverage-v8, prettier, @types/node) carry different ranges. The ranges no longer differ, and "do not widen the skew" understates a rule that is now "one range everywhere it is declared". The local-dev skill describes the guard, so an agent gets a different instruction depending on whether the skill loaded. Copilot raised this on PR #4921 (round 3).

Expected: the bullet states the lockstep rule the guard enforces and names the guard.

2. Development setup: npm test is annotated "with coverage"

The command block says:

npm test -w src/<server>                # one workspace (vitest, with coverage)

Each workspace's test script is vitest run. Coverage is the separate coverage script (vitest run --coverage).

Expected: the annotation drops "with coverage", or the block lists npm run coverage -w src/<server> on its own line.

Not included

The Before pushing paragraph saying CI does not run ruff check is also stale (python.yml runs scripts/validate-py.mjs, which does), but #4871's PR rewrites that section, so it is left to that change.

Branch

Targets v2/main. If #4871's PR is still open when this is picked up, check whether it already touched either line.

[workspaceabheet]

Found and verified both stale statements still present on current origin/v2/main (confirmed clean of today's PR #4920, which rewrote the adjacent "Before pushing" section but left these two untouched).

1. Development setup, line 103 — the npm test -w src/<server> annotation says "(vitest, with coverage)". Confirmed: test runs plain vitest run in all 4 TS workspaces; coverage is a separate vitest run --coverage script. Proposed fix — drop "with coverage":

npm test -w src/<server>                # one workspace (vitest)

2. Dependencies bullet, lines 178-181 — says shared devDependency ranges "already differ; do not widen the skew". Confirmed: the verify:dep-lockstep guard (scripts/verify-dep-lockstep.mjs, in validate:guards/CI since #4864) now requires one identical range everywhere, and all 5 tracked packages (typescript, vitest, @vitest/coverage-v8, prettier, @types/node) are in fact identical across root + all 4 TS workspaces today. The local-dev skill already describes this correctly; only this bullet is stale. Proposed replacement — keep the opening clause, replace only the stale sentence:

When you bump a devDependency that several TypeScript workspaces declare (typescript, vitest, @vitest/coverage-v8, @types/node, …), bump it in every workspace that declares it. Declare it with one identical range everywhere — the verify:dep-lockstep guard enforces this.

No other file needs touching — checked README.md, CONTRIBUTING.md, and grepped the tree for other references to either stale sentence; none found.