Testing strategy and quality gate

This entry point is retained for existing callers. The canonical policy is testing-standard; read and apply that skill before planning tests or verifying a change. Use the harness's skill loader when available, or read the sibling file directly. If neither is accessible, report the missing policy instead of claiming that its gate was verified.

Do not keep a separate checklist or infer commands here. Repository-specific instructions supply the actual checks, dependencies, and approved exceptions. Report which checks passed, failed, or did not run, and never imply that a partial test run proves the full change is complete.