fix(ci): the sweep threw away a full report to die at exit 143

[LMPrado-DZ23]

Both sweeps on 2026-09-20 ran every static and drift gate green, merged seven green suites, reached Package artifact (npm pack policy), went silent for six minutes, and were killed:

10:25:13  ▶ Package artifact (npm pack policy) [serial]…
10:30:53  ##[error]Process completed with exit code 143

Not a timeout — the job budget is 55 minutes and the runner ceiling is ~60.

The repository already knew

check:pack-artifact falls back to a full next build, and the hosted runner cannot fit this tree. build.yml has been manual-only since diegosouzapw#11946 because 19 of its last 30 runs died with "the runner has received a shutdown signal" (VM out of memory) ~8 min into that build. Its own header says the bundle is validated "where a build actually fits" — the self-hosted pool.

So the gate was never going to pass there. Its failure mode was to discard thirteen green gates and seven green suites on the way out.

What it does now

On a hosted runner the gate is not attempted. It is recorded as unmeasured, with the reason and the remedy:

❌ pack-artifact (not measured here): a full next build does not fit the hosted
   runner (build.yml is manual-only since #11946); set USE_VPS_RUNNER=true for
   a release-window verdict

HARD, deliberately. A sweep missing a required gate is not release-green — and the point of every other guard in this release has been that a check which did not run must never read like one that passed. With USE_VPS_RUNNER selecting a runner the build fits, the gate runs exactly as before; a test asserts that branch, so the hosted path cannot quietly become the only path.

--unmeasured=<id>:<reason> is the general form. A malformed value throws rather than recording nothing — recording nothing is precisely the silent omission it exists to prevent. Reasons may contain colons, because the remedy is the useful half of the message.

Check	Result
tests/unit/validate-release-green.test.ts	53/53
smoke: a stated unmeasured gate	❌ NOT release-green, naming it
smoke: --unmeasured=pack-artifact (no reason)	refuses to start
YAML parses, prettier --check	clean

What this does not do

It does not make the artifact gate pass on a hosted runner — nothing can. A fully green sweep for this line needs USE_VPS_RUNNER=true with that runner online, and that is the owner's call. What changes is that everything else the sweep measured now survives to be read.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 50880035-4403-4942-a53b-645194dfd66a

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}