3 Commits

Include renames

Author	SHA1	Message	Date
mesalogo	26b87d7ed5	test: use the installed OpenCode entrypoint ... The Linux routing test still referenced the obsolete bin/opencode name. With intentional path-only Runtime selection, that stale fixture was no longer masked by automatic discovery; use the locked opencode-ai 1.18.9 bin/opencode.exe entrypoint on every platform. Keep the approved 0.12.0 notes and bilingual feature matrices explicit that local OpenCode paths are not prevalidated and fail only at actual launch.	2026-09-03 05:37:52 +08:00
mesalogo	8ecd87381f	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
mesalogo	c4231c8f9c	chore: prepare GoodBuddy 0.12.0 release ... Update the desktop version, approved bilingual release notes, and synchronized English and Chinese feature matrices for the 0.12.0 candidate. Release preparation now runs local tests, type checks, and lint without a local production build, then requires the main-branch CI build before tagging. The package matrix uses a native Windows arm64 runner and validates managed Python on every target without adding extra license files to the desktop package.	2026-09-02 21:36:27 +08:00