docs: add the generated Vite+ block, and correct the bare-vp claim - #145
Merged
Conversation
Adds Vite+'s generated toolchain block to CLAUDE.md between its own HTML comment markers, so the tool can resync it, with a short repo-specific override note OUTSIDE the markers. Two things worth knowing about how it landed. The block's checklist says to run `vp install` / `vp check` / `vp test` directly. This repo's own guidance says to run everything through pnpm, so the note points at `pnpm vp <cmd>` - the form package.json and CI use, and therefore the only one that stays verified - and steers `vp install` to `pnpm install`, because the install discipline here is specific: `pnpm add -w` for root deps, always followed by a bare `pnpm install`, and a 24-hour release-age guard that must not be bypassed. And adding it surfaced a stale claim that would have contradicted it. CLAUDE.md said a bare `vp` OR `npx vp` at the project root fails with EBADDEVENGINES. Half of that is wrong, measured rather than assumed: npx vp check -> EBADDEVENGINES, Invalid name "pnpm" does not match "npm" vp check -> exits 0, "All 367 files are correctly formatted" The global `vp` binary is v0.2.7 and is not npm, so devEngines' packageManager pin does not gate it. The line now says which form fails and which does not, and says not to "fix" a working command on the strength of the note. The override paragraph deliberately does NOT reproduce the marker strings literally - a resync matching on marker text would otherwise find the prose first and rewrite the wrong region. It points at a grep instead. Verification: pnpm run verify green - 1554 app + 13 worker + 3 container tests, 0 warnings, exit 0. Documentation only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012VRsPwmSwjnFKVSS6jx9Mo
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Vite+'s generated toolchain block to
CLAUDE.mdbetween its own HTML comment markers so the tool can resync it, with a repo-specific override note outside the markers.There is no
AGENTS.mdin this repo;CLAUDE.mdis the project instruction file, so it goes there.Where this repo overrides the block
The generated checklist says to run
vp install/vp check/vp testdirectly. This repo runs everything through pnpm, so the note points atpnpm vp <cmd>— the formpackage.jsonand CI use, and therefore the only one that stays verified — and steersvp installtopnpm install, because the install discipline here is specific:pnpm add -wfor root deps, always followed by a barepnpm install, and a 24-hour release-age guard that must not be bypassed.Adding it surfaced a stale claim that would have contradicted it
CLAUDE.md said a bare
vpornpx vpat the project root fails withEBADDEVENGINES. Half of that is wrong — measured, not assumed:npx vp checkEBADDEVENGINES … Invalid name "pnpm" does not match "npm"vp checkThe global
vpbinary is v0.2.7 and is not npm, so thedevEngines.packageManagerpin does not gate it. Left as-is, an agent reading the new block ("runvp check") against the old line ("a barevpfails") would have had no way to resolve the conflict. The line now says which form fails, which doesn't, and not to "fix" a working command on the strength of the note.One deliberate detail
The override paragraph does not reproduce the marker strings literally. A resync that matches on marker text would otherwise find the prose before the real block and rewrite the wrong region — it points at a
grepinstead. Confirmed: exactly two literal markers in the file.Verification
pnpm run verifygreen — 1554 app + 13 worker + 3 container tests, 0 warnings, exit 0. Documentation only.🤖 Generated with Claude Code
https://claude.ai/code/session_012VRsPwmSwjnFKVSS6jx9Mo