diff --git a/SKILL.md b/SKILL.md index 0c2d0a3..f87834d 100644 --- a/SKILL.md +++ b/SKILL.md @@ -426,7 +426,10 @@ and reconciles the target doc with the Body. is Idunn's verify transaction (a campaign in progress, ruled 2026-09-22). Until it lands, use the stopgap `tools/stopgap/ygg-verify.sh`. It pushes an exact revision to a mirror on Yggdrasil and runs one command in a container - capped at 4 CPUs and 12 GiB, niced, with at most 2 jobs at a time. Every + capped at 4 CPUs and 12 GiB, niced, with at most 3 jobs at a time (raised + from 2 by the operator on 2026-09-22: "the other cores are mostly sitting + idle"). **The script owns these numbers; where this text and `ygg-verify.sh` + disagree, the script is right** — this line was already stale once. Every Hands and Soul brief says so. Starfire runs only what has to run on Windows, such as the QUIC win32 scenarios: one job at a time, never burners. **The stopgap's container runs as root, so a test that expects a permission diff --git a/references/changelog.md b/references/changelog.md index 241adea..363da51 100644 --- a/references/changelog.md +++ b/references/changelog.md @@ -105,6 +105,15 @@ compiler jobs." The fleet inventory already said the same. runs the command in a container capped at 6 CPUs and 16 GiB, niced, with at most two jobs at once. The target directory stays inside the scratch work tree. Its header names its deletion line. +- **Correction, same day, found by a Mind Steward pass:** the caps above are + not what shipped. `ygg-verify.sh` defaults to **4 CPUs, 12 GiB and 3 slots** + — the slot raise was the operator's ("the other cores are mostly sitting + idle") and is recorded in the script's header; the 6/16 figure is not, and I + cannot say from here whether it was ever live or was written from a plan I + then retuned without a line. SKILL.md carried the stale "2 jobs" until this + pass caught it. **The script is the owner of these numbers.** Prose that + restates a running tool's configuration goes stale silently, which is how + three surfaces came to disagree inside one day. - The smoke test found two bugs in the stopgap before any real job ran: - `bash -lc` reset the image's `PATH`. - `ssh` re-split the command, so `a && b` ran `b` on the host.