Kaoru0822 7346397106 fix(ghidra): keep earlier LaunchSupport warnings when a later helper fails ... d4bd65c53 moved a failed LaunchSupport helper's output into the nested `command_outcome`, but the cause projection also returned early for those failures and dropped `launch_support`. A `-vmargs` failure therefore lost the warning that the successful `-envvars` helper had already reported. Keep the retained helper outputs and skip only the launcher outcome that the nested cause now owns. Update the Ghidra launch and Hopper startup boundary expectations to current main: failed helpers report through `cause.command_outcome`, and bridge startup results carry the launched `processId` (599a8ee11), asserted against the exact retried process. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-14 02:40:48 +00:00
..
acceptance	fix(javascript): admit candidate endpoint interpretation in worker output	2026-10-14 02:36:45 +00:00
boundary	fix(ghidra): keep earlier LaunchSupport warnings when a later helper fails	2026-10-14 02:40:48 +00:00
composition	fix(providers)!: preserve readiness, coverage, and diagnostic ownership	2026-10-14 08:28:14 +08:00
conformance	test: harden verification fixtures and runtime coverage	2026-10-14 08:59:27 +08:00
evaluation	chore: merge upstream main while preserving bug fixes	2026-10-14 09:50:13 +08:00
fixtures	chore: merge upstream main while preserving bug fixes	2026-10-14 09:50:13 +08:00
process-global	test: harden verification fixtures and runtime coverage	2026-10-14 08:59:27 +08:00
support	test: harden verification fixtures and runtime coverage	2026-10-14 08:59:27 +08:00
ciTestSequencer.ts	ci: finish main validation and balance complete test costs	2026-10-13 18:54:05 +08:00
processOwnershipRunner.ts	test(process): retire native caches at worker teardown	2026-10-09 04:12:49 +08:00