mirror of
https://github.com/jjbrunton/Sauci.git
synced 2026-10-31 18:19:43 +00:00
jjbrunton
bdfe8b7171
Keep Sol responsible for scope, steering, and final acceptance while assigning one continuous discovery, implementation, testing, and iteration unit to Terra. Route additional reviewers and runtime verification by risk and avoid redundant verification passes.
2.2 KiB
2.2 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. Use an independent verifier for user-facing, cross-boundary, or high-risk runtime changes. Documentation, mechanical configuration, isolated tests, and low-risk package-local changes may use focused deterministic checks without a verifier.
- Package-local deterministic checks do not need a running stack. For runtime
verification, reuse a compatible running local stack when available; otherwise
start the documented full stack 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. - When independent runtime verification is required, 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 independent verification is broken, fix and use a fresh verifier. Stop after three failed rounds and report the unresolved evidence.
- Run focused checks for the affected change. Run affected E2E when the runtime
path requires it. Run
npm run verify:fullwhen its prerequisites are available; it already runsnpm run verify:fast, so do not run both in sequence. 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 outcome is incomplete when independent runtime verification is required.