sandcastle: fix implement-prompt feedback loop (npm -> just check) #13
Labels
No labels
in-review
ready-for-agent
ready-for-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
weiwen/evie#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blocked by: #9, #10, #11
Why
.sandcastle/implement-prompt.mdtells the implementer, before committing, to run:But evie is a Rust project with no npm scripts (
package.jsonhas only deps, noscripts). So the implementer's pre-commit feedback loop is a no-op — it never actually type-checks or tests the Rust code.What
npm run typecheck && npm run testinstruction withnix develop .#ci -c just check(fmt + clippy + test).Acceptance criteria
implement-prompt.mdinstructs runningnix develop .#ci -c just checkbefore committing.npm run ...build/test references in the prompt.Note
Depends on #10 (
just checkrecipe), #9 (ci devShell), and #11 (image can run it). Purely a prompt edit; safe to land once the toolchain is real.