1. browse_code — docs/internals/testing.md

2. browse_code — apps/desktop/src/backend/DesktopBackendManager.test.ts

3. browse_code — packages/provider-core/src/server/managedProvider.test.ts

4. browse_code — apps/desktop/src/app/DesktopApp.test.ts

5. modify_pr — Submitted review with 1 inline comment

6. browse_code — In apps/desktop/src/backend/DesktopBackendManager.test.ts does the existing readiness waiters test provide a suitable case into which the newly added server-ready control line test could be folded while retaining HTTP fallback testing? Identify meaningful differences and whether it is the same behavior.

7. browse_code — Analyze if the new test 'holds the first provider check until server startup finishes' duplicates and can be folded into the immediately preceding 'runs the initial provider check in the background and streams the refreshed snapshot' without losing unique behavior, referencing code. Provide concise answer.

8. browse_code — What does layerAlwaysRunTest set for runBackgroundWork and awaitServerReady in packages/provider-core/src/server/managedProvider.test.ts and what behavior of test is affected?

9. browse_code — Find existing managed provider tests verifying initial checks without background work enabled, and default awaitServerReady omitted.

10. modify_pr — Submitted review with 1 inline comment — not performed: the agent's request was refused before it ran

11. browse_code — Assess whether tests 'becomes ready from the server ready line while HTTP probes stall' and 'notifies readiness waiters on HTTP readiness and stop without clock advancement' can be folded into a smaller parameterized case, or whether the setups are materially different.

12. browse_code — Compare existing provider initial check test and new readiness gate test for whether cases can be combined reducing code and still cover behavior. Discuss practicality and unique behavior.

13. modify_pr — Test signal review: the new provider-readiness case can be folded into the existing initial-check test.

14. modify_pr — Minimized comment (duplicate)

15. browse_code — Review the readiness provider test and explain whether an existing test can be extended instead without losing coverage; concise.

16. browse_code — For the provider core managedProvider.test.ts initial readiness tests, is runBackgroundWork false existing separately tested with no readiness gate?

17. browse_code — Does the no readiness gate and runBackgroundWork true get tested elsewhere in managedProvider.test.ts?

18. browse_code — Does periodic recovery test verify no readiness gate starts initial check?

19. browse_code — In packages/provider-core/src/server/managedProvider.test.ts lines 378-413 what does it assert about initial check?

20. browse_code — No further query; state no additional result.

21. browse_code — In packages/provider-core/src/server/managedProvider.test.ts locate test regarding periodic recovery.

22. browse_code — No more research needed.