Skip to content

First run: warn on older Node instead of refusing, and show what failed - #17

Merged
YusefSyed merged 3 commits into
mainfrom
fix/first-run-node-and-summary
Nov 4, 2026
Merged

YusefSyed merged 3 commits into
mainfrom
fix/first-run-node-and-summary

Conversation

@YusefSyed

@YusefSyed YusefSyed commented Nov 4, 2026 •

Copy link
Copy Markdown
Owner

What changes

  • Node: the launcher and runtime guard accept Node 22 from 22.16.0 and Node 24 from 24.0.0, each line's first release whose node:sqlite needs no flag and honours the open timeout the observers use. Below the October 2026 security release (22.23.4 or 24.22.1) the launcher warns and runs, and doctor shows [warn]. Before this, those versions got exit 2 and nothing ran.
  • assess output: a summary on stderr lists each check that did not pass, anything else keeping the run from being clean, and an export command that works as printed. stdout JSON is unchanged. Observed values appear only for the owned synthetic fixture, so a real app's values stay out of CI logs. Control characters are stripped.
  • Action name: ScopeHaven - check what an AI agent did, for Marketplace search.

The failing case

A fresh clone on Node 24.18.0: ./scopehaven assess --target demo-vulnerable exited 2 and ran nothing.

Checked

On macOS arm64, official builds with verified checksums: 22.16.0, 24.0.0, 24.18.0 and 24.22.2 each gave doctor ready, demo-vulnerable exit 1 with 26 failures, demo-repaired exit 0. 22.13.0 is refused with exit 2: its node:sqlite reads busy_timeout as 0 where 22.16.0 and 24.0.0 read 2000.

Limits

The suite itself runs on the pinned 24.22.2. Older versions were checked with doctor and both demo targets, not the full suite, and CI does not run them. A below-floor run goes ahead with only a warning.

🤖 Generated with Claude Code

Anyone on a Node 22 or 24 below the October 2026 security release got exit 2
and nothing else. The floors are now each line's first release with node:sqlite
and no flag (22.13.0, 24.0.0); below the security release the launcher warns and
doctor shows [warn]. The demo was run on 22.13.0, 24.0.0, 24.18.0 and 24.22.2
with the same counts.

assess now writes a summary to stderr: each check that did not pass and how to
see the findings. stdout is unchanged. Observed values appear only for the owned
synthetic fixture, so a real app's values stay out of CI logs, and control
characters are stripped.

Rename the root action so it reads clearly in Marketplace search.

Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
- Raise the 22 floor to 22.16.0: on 22.13.0 node:sqlite ignores the open timeout
  (PRAGMA busy_timeout reads 0), so the observers' lock fallback would not wait.
- A run that exits 1 with every check passed now says why, and not-applicable
  rows are counted.
- The export hint now works as printed: it writes into the evidence directory.
- core-practice's why() prefers row reasons, since assess now always writes stderr.
- DEPENDENCIES no longer says 24.18.0 is refused.

Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
The escaped form was written as a literal line separator, which broke the regex literal.

Signed-off-by: YusefSyed <211442445+YusefSyed@users.noreply.github.com>
@YusefSyed
YusefSyed merged commit 2e2dd77 into main Nov 4, 2026
7 checks passed
@YusefSyed
YusefSyed deleted the fix/first-run-node-and-summary branch November 4, 2026 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant