Conversation
…he agent - README: CLI-created Vercel projects default the Framework Preset to Other, which builds green but 404s every Next.js route; document the framework=nextjs fix (closes Merit-Systems#48) - gitignore agent/skills/ and skills-lock.json so Neon marketplace installers cannot be committed into the agent definition (closes Merit-Systems#47) - source-layout test now fails if unexpected directories (or a skills-lock.json) land in the agent tree
This branch has not been deployed
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.
Summary
vercel project add/vercel link) defaults its Framework Preset to Other, which builds green but silently drops the Next.js output - every app route 404s while/eve/v1/healthstill answers. The README now documents settingframework=nextjsbefore the first Git deploy.vercel integration add neonwrites third-party agent skills underagent/skills/and a rootskills-lock.json, and eve loads every skill inagent/skills/. Both paths are now gitignored, and the README tells CLI users to delete them after provisioning.tests/source-layout.test.tsnow failspnpm checkif unexpected directories (or askills-lock.json) ever land in the agent tree, so a committed installer drop is caught in CI.Validation
pnpm exec vitest run tests/source-layout.test.ts tests/local-development.test.ts- 10 tests pass, including the new guardagent/skills/neon/+skills-lock.jsonpresent, passes on a clean treeoxfmt --checkclean on all touched files