docs(sprint): correct the #191 note, file the setup-command gap as #314

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-26 21:34:13 +04:00
parent 1b3b2f401a
commit a7f5b9902f
+9 -3
View File
@@ -100,9 +100,15 @@
- Left deliberately: the gate chain still short-circuits before the execution gate when the
contract gate fails. The stage fails either way — cheap gates first, no COMPLETE-lie.
**Goal 1 remaining: #267 only** — the acceptance live run. Needs the #191 `setup = "npm ci"` alias
first, or the now-firing gate fails on absent `node_modules` rather than on real code. Fold the
unverified #312/#313 trailing-mandate check into the same run.
**Goal 1 remaining: #267** — the acceptance live run. Fold the unverified #312/#313 trailing-mandate
check into the same run.
**Precondition, filed as #314.** #191 (dependency resolution before scaffold accept) closed on
2026-07-21: `runSetupCommand` runs the profile alias `setup` before every build gate and #40 resolves
it per toolchain. But `setup` is operator-declared in `.correx/project.toml`, and a freestyle run
scaffolding into an empty workspace has no profile — so `npm run build` runs with no `node_modules`.
Invisible until now; #263 making the terminal gate actually fire is what surfaces it. For #267,
hand-write a `project.toml` in the QA workspace; the general fix (toolchain-default `setup`) is #314.
---