test: stabilize 0.12.0 candidate validation

Full-suite resource contention could make asynchronous renderer assertions and short runtime timing tests fail even though focused runs passed. Limit Vitest to two workers and give the affected UI operations the existing three-second async window. Also include the approved Linux ARM OpenCode startup note in both feature matrices and release-note languages, and record the successful isolated Linux x64 Host validation of the current-source Runtime activation path.
2026-09-02 22:57:31 +08:00
parent dc36e7a967
commit 8ecd87381f
6 changed files with 35 additions and 8 deletions
@@ -82,7 +82,10 @@ otherwise.
  parallel. Interactive questions are answered only by foreground
  conversations; scheduled tasks, remote channels, delegated work, and other
  background runs fail immediately with guidance to rerun in the foreground
-  instead of waiting indefinitely.
+  instead of waiting indefinitely. On managed Linux ARM Hosts, project
+  switching and cold startup reuse the Runtime path, registry, and manifest
+  verified during setup instead of repeating an OpenCode version probe or
+  binary check.
 - [x] **Managed SSH OpenCode loop (technical preview)**: Controlled by the
  separate Remote Projects (Technical Preview) tab under Settings / Platform
  Features and disabled by default. Disabling it does not affect local