Skip to content

Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS

Merge current main into Vitest cache isolation fix

[._.]/ Adam Eivy7314cff8a98e
diff --cc docs/GITHUB_ACTIONS.md
index 4aafbee0b4,38fa111e79..0ce1703fdc
--- a/docs/GITHUB_ACTIONS.md
+++ b/docs/GITHUB_ACTIONS.md
@@@ -754,11 -754,7 +754,11 @@@ The three test-runner jobs are therefor
`server_shards`, `client_shards`, and `windows_shards` — `[1]` for exact-file
plans and `[1..n]` for full plans. Windows also uses its full matrix for
related-test plans: a single shared source can select most of the server graph
-and exceed the 15-minute test-step budget on one Windows runner. Matrices are
+and exceed the bounded test-step budget on one Windows runner. Full Windows
+shards reached 19,911 passing tests in 877.6 seconds before post-test timeout,
+and another reached 1,091/1,100 modules at the 15-minute deadline (2026-10-24,
- #13402). The test step now has 20 minutes within its unchanged 40-minute job;
++#13402). The test step now has 25 minutes within its unchanged 40-minute job (#13301);
+the two-worker cap, matrix size and all tests remain unchanged. Matrices are
sized by `FULL_SUITE_SHARDS` in
`scripts/ci-test-plan.js` (client 3, Windows 3, server 2) — and each job builds
its matrix from that output. The decision has to be made in the planner: a