fix: recover from-scratch live builds + point data persona at Prisma (#181, #182)#183
Merged
Merged
Conversation
…risma The first full-scope live run only produced Vike's default "Welcome" page. Two coupled from-scratch gaps: #181: the flagship data persona told the agent to build on `universal-orm`, which isn't installable (`@universal-orm/core` 404s on npm), so builds stalled sanity-checking the stack. It now defaults to Prisma with concrete install/init steps; the architect default no longer names an unpublished package. Persona renamed `universalOrmModeler` -> `dataModeler`. #182: the loop assumed an app already existed and only needed polishing. The build step now verifies it produced files and hard re-prompts to scaffold from scratch if the workspace is still empty; the improve step switches to a "create the whole app" directive on an empty workspace; the default max-passes is raised 3 -> 5. Also clarifies the end status ("finished", not "done"). Closes #181 Closes #182
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
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.
Fixes the two coupled from-scratch gaps that made the first full-scope live run end at Vike’s default "Welcome" page instead of the requested app.
#181 — data persona pointed at unpublished
universal-ormThe flagship data persona told the agent to build the data layer on
universal-orm, but@universal-orm/core404s on npm, so a careful agent stalled sanity-checking the stack and produced nothing.universalOrmModeler→dataModeler(persona namedata-modeler): now defaults to Prisma with concrete install/init steps (npm i -D prisma,npx prisma init,prisma migrate dev,prisma generate), keeps the same schema-first / derived-migrations / typed-query conventions, and allows the architect to pick another published SQL ORM.universal-ormreferences out of shipped source + the--fakedemo + the example apps (they keyed workers by the old persona name, so the rename would have broken them — updated + tests re-run green).#182 — loop could not recover an empty/unbuilt workspace
The full-fledged loop assumed an app already existed and only needed polishing;
improvePrompt("smallest changes / no unrelated features") actively blocked scaffolding when the real blocker was "no app exists yet".scaffoldPrompt).--max-passesraised 3 → 5 so a from-scratch build has room to bootstrap an empty dir before polishing.node_modules/ lockfiles / dotfiles; gated to real drivers so the--fakeflow stays deterministic.Also
Verification
@gemstack/ai-autopilot259 tests green,@gemstack/framework55 (+5 new), both example suites green, full-repotest20/20 andtypecheck20/20.--fakeend-to-end still runs deterministically to production-grade in 2 passes (now "Vike + Prisma").claudesession + a fresh dir).Changesets:
@gemstack/ai-autopilotminor,@gemstack/frameworkminor.Closes #181
Closes #182