verify

# verify - visual verification as Definition of Done Visual verification is the credo Definition-of-Done gate for anything with a runtime surface. If a change renders something, updates something on screen, or reacts to a user action, it is not done until that behavior has been observed - either by the user in a real browser, or by a reliable automated Playwright check that drives the real build. This skill is the DoD gate that `ui: true` items require. > **Task backend.** If the task backend is `gsd` (`.credo/config: task_backend`, or the `CREDO_TASK_BACKEND` env override), the credo item lifecycle is inactive, so > there is no credo item to move to done - GSD owns task tracking. The verification method > here still applies as a general "prove it renders" tool; just do not gate a credo item > with it in that mode. ## What does NOT count as verification None of these are a substitute for visual proof: - pytest / unit tests / integration tests passing - `node --check`, a type-check, a lint pass, or a successful build - "the file is served" / "the server returned 200" - a subagent code-review or a static read of the source They can all be green while the surface renders broken, never updates, or ignores the user. Verification means the rendered surface was exercised and observed. ## Two accepted forms of proof 1. Browser verification by the user - the user opens the real surface and confirms it. 2. A reliable Playwright check - drives the actual build in a real browser,...