mirror of
https://github.com/jjbrunton/Sauci.git
synced 2026-10-31 10:19:43 +00:00
jjbrunton
01bb8225ae
Add concise routed context, task-aware agent roles, focused skills, and structured learning promotion.\n\nUnify local development and workspace tooling, add layered test and E2E verification, harden MCP authentication, and gate deployment behind verification and explicit production promotion.
1.6 KiB
1.6 KiB
name, description
| name | description |
|---|---|
| verify | Prove a completed Sauci engineering task works before a PR. Use when asked to verify, prove behavior, or open a PR with runtime evidence. |
Verify Sauci work
Run locally on a non-default branch with the implementation committed.
- Start the stack once with
scripts/dev-local.sh up; reset fixtures first when the task changes durable state. Web ishttp://127.0.0.1:3000, admin ishttp://127.0.0.1:3001, and MCP health ishttp://127.0.0.1:3002/health. - Give a fresh read-only verifier the acceptance criteria. It drives browser
surfaces with the repository browser capability, native surfaces with Maestro
or the iOS simulator skill, and APIs with
curl. Authentication fixtures are described bye2e/.auth/fixtures.jsonafterdev-local.sh reset. - The verifier writes screenshots, traces, video, or response evidence under
evidence/and returns only expected, observed, evidence paths, andworks|broken. It never edits code. - If broken, fix and use a fresh verifier. Stop after three failed rounds and report the unresolved evidence.
- After the task works, run
npm run verify:fast, affected E2E, andnpm run verify:fullwhen local Supabase/Deno are available. Never weaken an assertion just to pass. - Open a PR only after both task verification and regression checks pass. Upload
evidence to the established CI artifact or
pr-evidenceprerelease and embed the screenshot plus a video/trace link in the PR body.
A green test suite without an independently observed task outcome is incomplete.