fix

Fix the requested defect. Use the twin to answer questions that affect the change and exercise the application. Reuse evidence from normal development: once the required behavior is covered and passes, finish. Investigate further when a failure or a specific unanswered requirement warrants it.

For a change with no meaningful vendor interaction, skip Veris setup and twin work; use the repository's validation and state that scope in the result. A local queue or cache defect that changes vendor-facing behavior still needs the affected application flow tested against the twin.

Use the working setup

Read relevant findings in .veris/NOTES.md and reuse those whose conditions still apply. Follow How to run for preparation, the application command, evidence collection and cleanup. Setup owns connection selection and configuration. Run setup only when a needed handoff step is missing, the connection is broken, or the change invalidates its wiring, such as adding a vendor service or hostname. An application assertion failure alone is not a reason to redo setup.