dhpk-feature-verifylisted

# Feature Verify — Runtime-First API Verification Verify deployed behavior with read-only runtime evidence: `Claude analysis → Codex independent confirmation → integrated verdict` Use this for post-deploy checks, smoke tests, and production diagnosis. For local tests use the repository verification route; for changes use `dhpk-adaptive-dev-workflow` in feature mode; for code review use `dhpk-change-review`. ## When NOT to Use - The requested action changes application data, configuration, or deployment state. - The task is to implement or modify a feature; use `dhpk-adaptive-dev-workflow` in feature mode. - The task is a code, security, or test review rather than runtime behavior verification. - There is no read-only endpoint, observation path, or approved test environment that can produce evidence for the requested claim. ## Required References Read these at the indicated phase: - P0/P3: [safety-rules.md](references/safety-rules.md) and [environments.md](references/environments.md) - P1/P2/P4/P5: [blackbox-testing.md](references/blackbox-testing.md) - P0/P2/P5: [verification-playbook.md](references/verification-playbook.md) - Report: [output-template.md](references/output-template.md) `Bash` is permitted only for read-only curl and observation queries reviewed against the safety rules. Missing endpoint allowlist means P3 is skipped. ## P0 — Scope and Safety 1. Select `--env`, defaulting to test, and load its configuration. 2. Run `scripts/health-probe.sh <he