Surfaced 2026-05-24 during PR #448 verification.
The CI workflow Test & Coverage runs backend + frontend test suites but does not invoke the CLI test suite at cli/__tests__/. Local-only.
Concrete evidence: PR #448 fixed a pre-existing stale test (runtimeType='local-cli' vs current 'stub') that had been failing on main for weeks. Nobody caught it because CI never ran it.
Fix
Add a cli step to .github/workflows/tests.yml (or wherever Test & Coverage lives):
- name: CLI tests
working-directory: cli
run: |
npm ci
NODE_OPTIONS="--experimental-vm-modules" npx jestOr fold into the existing backend job if Node + npm cache are already warm.
Why this matters
The CLI is the ADR-005 driver entry point — commonly agent attach is how every BYO-claude / BYO-codex agent joins the kernel. Regressions there silently degrade the entire wrapper-based runtime tier.
Estimate: ~15 LOC YAML + maybe a cli/package-lock.json if not present.
Surfaced 2026-05-24 during PR #448 verification.
The CI workflow
Test & Coverageruns backend + frontend test suites but does not invoke the CLI test suite atcli/__tests__/. Local-only.Concrete evidence: PR #448 fixed a pre-existing stale test (
runtimeType='local-cli'vs current'stub') that had been failing on main for weeks. Nobody caught it because CI never ran it.Fix
Add a
clistep to.github/workflows/tests.yml(or wherever Test & Coverage lives):Or fold into the existing backend job if Node + npm cache are already warm.
Why this matters
The CLI is the ADR-005 driver entry point —
commonly agent attachis how every BYO-claude / BYO-codex agent joins the kernel. Regressions there silently degrade the entire wrapper-based runtime tier.Estimate: ~15 LOC YAML + maybe a
cli/package-lock.jsonif not present.