Intent of agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence legacy migration persists the whole set in one write (never a subset, even across a re-restore)|occurrence=1

All 2 exact tests in this concept. Every test is marked by where it enters the hierarchy.

mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/ 2 tests
- platform/ 2 tests
  - agentHost/ 2 tests
    
    test/ 2 tests
    
    node/ 2 tests
    
    mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence a rejected migration write leaves the catalog absent (not a subset) so migration re-runs|occurrence=1 Inherited agentService.ts ×1
    
    mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence legacy migration persists the whole set in one write (never a subset, even across a re-restore)|occurrence=1 Introduced here