Skip to content

ci(release): declare registry.npmjs.org for the release-gate planner's npm:effect import - #28

Merged
kiro-systemf[bot] merged 1 commit into
mainfrom
xs/release-gate-hosts
Oct 7, 2026
Merged

kiro-systemf[bot] merged 1 commit into
mainfrom
xs/release-gate-hosts

Conversation

@systemfsoftware-maker

@systemfsoftware-maker systemfsoftware-maker commented Oct 7, 2026 •

Copy link
Copy Markdown
Collaborator

Fixes the red Release gate on main at 27107a0 (#13's squash).

Root cause

Run 37581046981, job "plan · mutation shards" (112660538757). The first planner step, "Discover mutation projects", runs scripts/stryker-plan-gate.ts in the sandbox with jsr.io as its only declared host. The planner imports npm:effect (through scripts/deno.json), so Deno's fetch of registry.npmjs.org/effect was refused:

Download https://registry.npmjs.org/effect
sandbox: egress to registry.npmjs.org:443 refused (not declared)
error: Failed caching npm package 'effect@4.0.1'

The step exited 1, so has-shards was never published and every mutation shard was skipped. Main has no mutation result.

Change

  • .github/workflows/release-gate.yml: both Deno planner steps ("Discover mutation projects" and "Gate the plan") now declare jsr.io and registry.npmjs.org, the same pair gate:tasks declares. This is consumption only, allowed by the no-npm scope ruling.
    • The gate step passed on cache before: it reused the Deno cache the discover step left in the project's .cache. Its own imports resolve the same npm package, so it declares the host as well.
    • Nothing else is widened. The stryker plan step already had both hosts; the shard step is unchanged.
  • sandbox-proofs/release-gate-planner.test.ts runs in test:sandbox, which check:ci and the CI test leg run. No new job.
    • It parses release-gate.yml and takes, from the workflow itself rather than a copy, each plan-job sandbox step that runs scripts/stryker-plan-gate.ts: its hosts and command.
    • It runs each command through sandbox --allow-host … on exactly those hosts. The fixture is a workspace with one mutating package and a one-shard plan, and each step's Deno cache is cleared first.
    • Both steps must exit 0, discover must list packages/core, and the gate must emit has-shards=true.

Sabotage (local, throwaway copy)

release-gate.yml Test result
this PR passes
main's (jsr.io only) fails: "Discover mutation projects" exited 1, with the same egress to registry.npmjs.org:443 refused lines as the CI log
this PR with registry.npmjs.org dropped from "Gate the plan" only fails: "Gate the plan" exited 1, Failed caching npm package 'effect@4.0.1'

Verified locally on d880005

pnpm bootstrap 0 · pnpm format:check 0 · pnpm gate:tasks 9/9 · pnpm gate:dist 2/2 · pnpm test:sandbox 4 passed (13 steps), including the new test · commitlint 0. No stryker ran locally.

The Release gate dispatched on this branch is the proof that the planner succeeds and the shards run real mutants. Its run id and per-shard mutant counts are posted below.

CONST-W3: release-gate.yml is an evaluator surface (AGENTS.md Boundaries, CONST-E9), and the test is a new check. Both are added on the explicit ruling of their owner (Kiro).

…s npm:effect import

The Release gate failed on main at 27107a0 (run 37581046981, job "plan · mutation shards"). Its first step runs scripts/stryker-plan-gate.ts in the sandbox with jsr.io as the only declared host. The planner imports npm:effect through scripts/deno.json, so Deno's fetch of registry.npmjs.org/effect was refused, the step exited 1 and every mutation shard was skipped.
Both planner steps, "Discover mutation projects" and "Gate the plan", now declare jsr.io and registry.npmjs.org, the same pair gate:tasks declares. The gate step happened to reuse the Deno cache the discover step left in the project's .cache, but its own imports resolve the same npm package, so it declares the host too. Nothing else is widened.

sandbox-proofs/release-gate-planner.test.ts runs in test:sandbox, which check:ci and the CI test leg run. It reads every sandbox step in release-gate.yml's plan job that runs scripts/stryker-plan-gate.ts and takes each step's hosts and command from the workflow, not from a copy. It then runs each command through sandbox --allow-host on those hosts, against a fixture workspace and plan, with the step's Deno cache cleared first. Both steps must exit 0, discover must list the fixture's mutating package, and the gate must emit has-shards=true.
As a sabotage proof, with main's release-gate.yml the test fails on "Discover mutation projects" with the same "egress to registry.npmjs.org:443 refused" lines as the CI log. With registry.npmjs.org dropped from the gate step only, it fails on "Gate the plan" with "Failed caching npm package 'effect@4.0.1'"

CONST-W3: release-gate.yml is an evaluator surface (AGENTS.md Boundaries, CONST-E9), and the test is a new check. Both are added on the explicit ruling of their owner (Kiro), not on the maker's own judgment
@systemfsoftware-maker systemfsoftware-maker changed the title xs/release gate hosts ci(release): declare registry.npmjs.org for the release-gate planner's npm:effect import Oct 7, 2026
@kiro-systemf
kiro-systemf Bot merged commit 928d17c into main Oct 7, 2026
7 checks passed
systemfsoftware-maker added a commit that referenced this pull request Oct 7, 2026
…ages

Brings main's #28 (squash 928d17c): both Deno planner steps in release-gate.yml declare jsr.io and registry.npmjs.org, and sandbox-proofs/release-gate-planner.test.ts runs those steps on exactly the hosts the workflow declares
systemfsoftware-maker added a commit that referenced this pull request Oct 7, 2026
… into the upstream subtree layer

Brings main's #28 through #14: the release-gate planner steps declare jsr.io and registry.npmjs.org, and test:sandbox runs them on exactly those hosts
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