netcracker/ai-for-dummies
3
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

fix: say the lockfile is committed, not untouchable

Browse Source 
AGENTS.md listed package-lock.json under 'Never touch', meaning never
hand-edit. Task 01's agent read it as never create, and shipped the scaffold
with no lockfile and installs pinned to --package-lock=false. That breaks the
parallel worktree setup outright: worktree.sh and launch.sh both spin up with
npm ci, which requires a lockfile.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Marcos Paulo
2026-09-05 02:08:08 +00:00
parent 88eecb1c71
commit f5631acb2c
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+4 -1
View File
@@ -49,7 +49,10 @@ Adding a build step changes this contract. Read
- `submitted-skills/` — other people's submitted work, reproduced verbatim - `submitted-skills/` — other people's submitted work, reproduced verbatim
- `skill-reviews/improved/` — generated; edit `skills-review/catalog.js` instead - `skill-reviews/improved/` — generated; edit `skills-review/catalog.js` instead
- `vote-service/` — separate deploy lifecycle; do not fold into the site build - `vote-service/` — separate deploy lifecycle; do not fold into the site build
- `package-lock.json`, `dist/`, `node_modules/` - `dist/`, `node_modules/` — build output, never committed
- `package-lock.json` — **committed, but never hand-edited.** Change it only
as a side effect of `npm install`. Every worktree spins up with `npm ci`,
which fails outright without it.
## Rules ## Rules