kami/correx
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs(sprint): record the #40 profile migration

Browse Source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
kami
2026-07-26 21:39:51 +04:00
parent fb8141d669
commit 9b59b7c1aa
1 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sprints/2026-07-23.md
+11 -2
View File
@@ -109,8 +109,17 @@ toolchain. But `setup` is operator-declared, and the repo profile didn't declare
`frontend/` cleared before each QA run, the now-firing terminal gate would run `npm run build` against
an absent `node_modules` and fail on deps instead of on the code. Added
`setup = "npm --prefix frontend install"` to `.correx/project.toml` (install, not `ci` — a fresh
scaffold has no lockfile). #267 needs nothing further. The general case — a workspace whose operator
declared no `setup` — is **#314** (toolchain-default fallback).
scaffold has no lockfile). The general case — a workspace whose operator declared no `setup` — is
**#314** (toolchain-default fallback).
**#40 follow-through** (commit `fb8141d6`). #40 (toolchain-aware command resolution — this repo hosts
Kotlin at root *and* a Node app in `frontend/`, and one flat alias can't serve both) closed on
2026-07-21 with `[commands.<toolchain>]` support in `6e844ef1`. The repo profile was never migrated:
every flat alias still pointed at npm, so a Kotlin run's auto-gate would have run
`npm --prefix frontend run build` — the latent misfire #40's own body predicted. Profile now carries
`[commands.jvm]` + `[commands.node]` with jvm as the flat default. Parsing verified against
`ProjectProfileLoader`; the gate prefers `<toolchain>.<alias>` and falls back to flat. #267's "re-scope
#40" is now just the live confirmation.
---