Native runtime builds could exceed the unrelated 20-second setup hook while each real build command allowed 120 seconds. Await initialization before runtime/sensor test timers, identify failed stages, and preserve existing command, response and test-body deadlines.
The cold-build qualifier derives its aggregate budget from the three real commands, bounds capture, and observes and settles parent/tool groups. Its reporting-fault campaign interrupts the actual parent during CMake and retains receipt refusal without bypassing cleanup. Controlled hook, aggregate-cutoff, inherited-pipe and reporting-write failures remain retained with their corrected campaigns.
Validation:
- Pickier, application/runtime types, fresh cold build, reporting-fault mode and 51 focused tests passed locally, with 347 assertions and one Linux-only skip. Both independent review axes are clean.
- Original-head CI 39838472116 passed the full check job, Linux cold/fault/FIFO campaigns and standalone commands. Its separate browser jobs failed; that terminal workflow and original artifacts remain retained.
- The combined source at
1ef2f6a86ed77ae9e7924d4fd3f76ebd19a8648eadds the browser-launch diagnostics from #70. Exact-head CI 39843840771 passed all five jobs, including both actual rendered browser campaigns, firmware, namespace and the complete check job. The full Buddy suite passed 1,519 tests, with 41 skipped, zero failed and 489,307 assertions, across 198 files. All later standalone CLI gates passed. The combined source was published toorigin/mainby normal fast-forward on October 22, 2026 as Chris Breuer without coauthors. - The original local full-suite failures in #68 and invalid-CLI timeout in #67 remain unexplained. A later passing workflow does not establish their causes. The original browser failures in #44 and #64 also remain open.
Related: #65. No physical runtime or hardware acceptance is claimed. No original failed workflow was rerun or replaced by this result.