harness-issueslisted

# harness-issues Create one outcome-oriented issue with scope, acceptance criteria, non-goals, risks, and verification. - Prefer a small independently testable outcome over a vague epic. - Mark sensitive paths, dependencies, rollout, and explicit exclusions. - Never place secrets, raw tool output, or unverified security claims in an issue. - Use the repository template when present and preserve its required fields. Use `.codex/skills/harness-delivery/references/delivery-contract.md` for evidence and `.codex/skills/harness-rules/references/governance-contract.md` for risk wording.