docs(devices): document fleet.ignored in the agents-yaml schema; repair the profiles.test state mock (RUSH-3062) - #2956
Conversation
…ir the profiles.test state mock (RUSH-3062)
Two leftovers from the fleet.ignored move:
- schema/agents-yaml.schema.json now documents the fleet.ignored entries
({ name, ignoredAt, ignoredOn }) so editors and the yaml-language-server
integration know the key.
- browser/profiles.test.ts's state.js mock exports getDevicesIgnoredPath;
since the move, config-migration imports it and the missing mock export
made every test in that file log a spurious 'device config migration
failed' (caught, non-fatal — but noise, and it meant the migration never
actually ran in that file's processes).
|
VERDICT: APPROVE Non-author review (automated reviewer paused per #1767). Docs + test-only diff, 2 files, +14/-0. All claims verified against origin/main. Schema entry matches
|
docs + test-only: two leftovers from the RUSH-3062
fleet.ignoredmove (42e1ff3). No behavior change.What changed
apps/cli/schema/agents-yaml.schema.json— documents thefleet.ignoredentries ({ name, ignoredAt, ignoredOn }, all three required) so the yaml-language-server integration and editors know the key the CLI now writes.apps/cli/src/lib/browser/profiles.test.ts— the../state.jsmock now exportsgetDevicesIgnoredPath. Since the move,config-migration.tsimports it (config-migration.ts:47), and the missing mock export made every test in this file throw inside the mock — caught byensureDeviceConfigMigratedand logged asdevice config migration failednoise (observed on the main CI run for feat(devices): move the discovery ignore-list into tracked central agents.yaml (RUSH-3062) #2947), with the migration never actually running in those processes.No changelog fragment: docs-only + test-only, and the
fleet.ignoredkey itself shipped with its own entry (.changelog/next/RUSH-3062-ignore.md).Verification
Ticket: RUSH-3062