Intent of agentHostStateManager.ts ×1
All 6 exact tests in this concept. Every test is marked by where it enters the hierarchy.
-
mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/6 tests-
platform/6 tests-
agentHost/6 tests-
test/6 tests-
node/6 tests-
mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentHostStateManager.test|title=AgentHostStateManager providerData (G-B1) restoreChat records providerData verbatim alongside turns|occurrence=1 -
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 -
mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence a valid new-format peerChats catalog restores without consulting legacy chats|occurrence=1 -
mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence createChat persists providerData; restore re-materializes from the orchestrator catalog before reading history|occurrence=1 -
mocha:v1|namespace=vscode@05c208e9e28d8c1c723fa08f85e2b7a96092e8e5|file=vs/platform/agentHost/test/node/agentService.test|title=AgentService (node dispatcher) peer chat catalog persistence legacy *.chats with no peerChats catalog migrates once into the orchestrator catalog|occurrence=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
-
-
-
-
-