Repository navigation
Run the full wire-harness suite on a development Realm and record every result #105
Description
Expected. The wire-harness suite's "N passed" summary only counts scenarios that actually ran. A scenario file that fails to even start must show up as a startup failure, never as a silent absence from the count.
Actual (at 87109e3c, harness pin v0.1.0-alpha.13). Fixed. The harness resolves file-based scenarios through $ADAPTER_DIR instead of the core checkout's working directory, accepts a named subset, and a script that fails to start is counted separately as a startup failure (SPAWN_N) in the suite summary. Any startup failure makes the run exit 2 with "RESULT: ERROR, scenarios could not run" instead of a misleadingly green pass count. The fix landed in wire-harness PR #6 and core PR #446, both merged; 55 upstream Rust tests and all seven core pin checks passed, and a fresh anonymous tag checkout matched the pin.
How it shows. Nothing today under normal CI, since the broken dispatch this issue found is fixed. The one thing nobody has done since is run the complete suite once against a live development Realm and record every scenario's result, which is the acceptance this issue was tracking in the first place.
How to check. On a local ./lyracore dev up Realm, run the full wire-harness suite (bash adapters/lyracore/wire-suite.sh, no subset argument) and record the pass/fail/skip count and the RESULT line.
Done when. That run's result is recorded here, with the harness pin and the core commit.
Activity
Mathih13 commentedon Sep 7, 2026
The source fix and release pin are merged. Wire-harness PR #6 resolves scenario paths from the adapter directory, accepts named subsets, and reports startup failures with exit status 2. Core PR #446 pins alpha.4 at
fcaabf9486a774611c1ee3d1a69710471c79c60a.A fresh anonymous tag checkout matched the pin. Offline tests cover dispatch from separate roots, startup failures, subset selection, and early refusal. Upstream CI passed on Linux and macOS, including 55 Rust tests; all seven core pin checks passed.
The remaining acceptance is a full suite run on an approved development Realm, retaining every scenario result. No existing Realm was accessed for this work. This issue stays open until that run proves the scenarios execute on their merits.
LyraCoreProject/wire-harness#6
#446
[-]wire-harness pin resolves file-based scenarios against the wrong root — the loop's 'suite green' never ran them[/-][+]Run the full wire-harness suite on a development Realm and record every result[/+]