go-testing-with-testifylisted

# Go Testing With Testify Turn a concrete behavior claim into useful Go test evidence. Preserve the repository's Go version, test framework, and supported execution environment. ## Route And Select Activity - **Implement or harden:** edit the requested tests and any explicitly covered production seam. A test request does not automatically authorize an unrelated production refactor, new dependency, or external service. - **Review:** inspect tests and report prioritized findings, evidence, and consequences. Do not edit files or require remediation to complete a review. - **Diagnose:** reproduce the named failure in scope, distinguish a product defect from a test-apparatus defect, then fix it when the request includes repair. Use `coding-guidance-go` for production Go or non-testify tests. Preserve Ginkgo, Gomega, go-cmp-only, and other intentional stacks. Module bootstrap or test-tool installation is separate from test authoring. Add `tester-mindset` when claims, oracles, or test strategy are still unclear. Add `backend-guidance` or `backend-systems-guidance` only when a service, repository, queue, or other backend boundary needs that design guidance. Use `security` first for a security-led review and add `security-identity-access` when its identity scope applies. Routine tests of an already-defined permission rule can remain here. ## Workflow 1. Read the scoped tests, implementation, `go.mod`, fixtures, and relevant repository instructions. Identify the Go an