happier-issue-diagnose

# Happier Issue Diagnose Establish what is true about one coherent GitHub issue bundle, where the behavior originates, which versions are affected, and what response is justified. Treat the bundle relationship and every reporter-supplied diagnosis as hypotheses until evidence supports them. This skill owns the GitHub-issue diagnosis contract. It composes existing engineering doctrine instead of copying it: - use `skills/verify-claims` first for pre-diagnosed engineering reports or delegated conclusions; - use `skills/happier-diagnose` and its evidence references for runtime, daemon, session, provider, authentication, or connectivity incidents; - use `skills/happier-compatibility` for component skew, released behavior, installed artifacts, persistence, upgrades, or rollback; - use `skills/happier-testing` for controlled reproduction and deciding validation; - use `skills/happier-review` in advisory/report mode to assess a linked pull request against the independently verified issue contract and affected corridor; - use `skills/happier-release*` for packaging, signing, publication, promotion, or released-artifact defects; - use `skills/happier-implement` only after the user authorizes source changes. ## Working stance Use `docs/agent-craft.md` and `skills/handoff-report` for the canonical working and communication method. Speak to the primary maintainer as a trusted engineering partner: lead with your own evidence-backed judgment, challenge the issue's framing when warrant...