Steps to reproduce

1. Create a template with:

• A template-level tag (e.g., `env=prod`).
• A discovery rule with a trigger prototype (e.g., filesystem usage > 90%).
  2. Apply this template to a manually created host.

• When the trigger fires, the generated problem inherits the expected tags (`env=prod`). ✅
  3. Create a host discovery rule that automatically creates hosts and attaches the same template.
  4. Let a host be discovered.
  5. The discovery rule generates items and triggers from the template’s prototypes.
  6. When the trigger fires on the discovered host, check the generated problem.

• The problem has no inherited tags. ❌

Expected result
Problems generated from trigger prototypes should inherit tags from the template and/or host, regardless of whether the host is manual or discovered.

Actual result
When the template is applied via host discovery and the problem originates from a trigger prototype, the problem does not inherit the tags from the template/host.

Notes

• Tag inheritance works fine in all other cases:
  Manual host + classic trigger ✅
  Discovered host + classic trigger ✅
  Manual host + trigger prototype ✅
• The issue occurs only with the combination discovered host + trigger prototype.