Found by the merge test gate on its first real cadence run (2026-07-31). Pre-existing at integration 674b72c8; deterministic on every attempt of retries = 2.
Tests:
wcore-cli::harness_regression r011_channels_auto_register_logs (harness_regression.rs:1053, guards F-014 channel bootstrap)wcore-cli::harness_regression r012_honcho_fallback_on_no_key (harness_regression.rs:1129, guards F-093 user-model fallback)
Both assert on stderr content:
R-011 expects one of ["start_all() complete", "channel_manager", "inbound polling active"]
R-012 expects one of ["local backend", "HONCHO_API_KEY", "user-model: using local", "honcho"]
Observed stderr now contains only the config-permission warning. The stderr-noise reduction (#147, 41 lines -> 2) removed the lines these two tests read.
The product behaviour they guard was not shown to be broken. What broke is the tests' ability to see it — which is the more dangerous failure, because a detector that cannot observe fails silently and keeps reporting green once someone "fixes" the assertion.
Do not repair these by loosening the assertion to something that always matches. Either point them at wherever the bootstrap and fallback events actually go now (there is a new log file — see #155), or restore the events at a level the test can observe. Whichever is chosen, the repair must be proven both directions: the assertion has to still fail when the underlying event does not happen.
Recorded in .planning/merge-test-baseline.txt as accepted debt so the gate keeps a reachable pass state. Remove those two lines when fixed.
Found by the merge test gate on its first real cadence run (2026-07-31). Pre-existing at integration
674b72c8; deterministic on every attempt ofretries = 2.Tests:
wcore-cli::harness_regression r011_channels_auto_register_logs(harness_regression.rs:1053, guards F-014 channel bootstrap)wcore-cli::harness_regression r012_honcho_fallback_on_no_key(harness_regression.rs:1129, guards F-093 user-model fallback)Both assert on stderr content:
Observed stderr now contains only the config-permission warning. The stderr-noise reduction (#147, 41 lines -> 2) removed the lines these two tests read.
The product behaviour they guard was not shown to be broken. What broke is the tests' ability to see it — which is the more dangerous failure, because a detector that cannot observe fails silently and keeps reporting green once someone "fixes" the assertion.
Do not repair these by loosening the assertion to something that always matches. Either point them at wherever the bootstrap and fallback events actually go now (there is a new log file — see #155), or restore the events at a level the test can observe. Whichever is chosen, the repair must be proven both directions: the assertion has to still fail when the underlying event does not happen.
Recorded in
.planning/merge-test-baseline.txtas accepted debt so the gate keeps a reachable pass state. Remove those two lines when fixed.