[justanotherariel]

Proposed change

Adds the issue context for integration: tuya from home-assistant/service-hub#423. It asks reporters for diagnostics and sends them to the Tuya quirks library or to a feature request, depending on what the diagnostics show.

Type of change

• Dependency upgrade
• Bugfix
• New rule or command
• New repository manifest (enable the bot on another repo)
• New feature (which adds functionality to an existing engine)
• Code quality improvement or refactor (incl. tests)

Additional information

• This PR is related to issue: Add Tuya issue context home-assistant/service-hub#423

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass (mise run test). Your PR cannot be merged unless tests pass.
• Lint and type checks pass (mise run check).
• The code has been formatted (mise run format).
• Tests have been added to verify that the new code works.
• There is no commented out or debug code in this PR.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If behaviour, configuration, or environment variables changed:

• README.md and .env.example have been updated accordingly.

[RaHehl]

Not blocking: could integrations keep this text in core, e.g. homeassistant/components/<domain>/issue_context.md? The few existing entries could move over once. I'd guess most code owners don't know this map exists, and hardly anyone reads the troubleshooting docs before opening an issue. Could be made known through the quality scale.

[justanotherariel]

I like that idea! cc @/ent:ohf-team-ha-core what do you think?

[RaHehl]

@justanotherariel I opened a draft as a proposal: #154