Make bug evidence intake truthful for non-container installs

Ask for the failing running version and a container image only where one exists. Accept symptom-appropriate screenshots or logs without forcing irrelevant log text, and state the matching triage rule.

Change-source: pulse-maintainer

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -7,11 +7,13 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thanks for reporting this. I need exact version metadata so I can triage quickly across rapid patch releases.
+        Report the version on the running instance where the bug occurs, not just the version you upgraded from. For container installs, include the running image tag or digest; for other installs, leave the image field blank.
 
         If your issue is connection- or data-related, include diagnostics from:
         `Settings -> Diagnostics -> Export for GitHub (sanitized)`.
 
+        Do not post secrets, tokens, private keys, or unsanitized configuration files.
+
   - type: textarea
     id: bug_description
     attributes:
@@ -94,18 +96,17 @@ body:
   - type: textarea
     id: logs
     attributes:
-      label: Relevant logs or diagnostics
-      description: Paste relevant logs, errors, or sanitized diagnostics export details.
-      render: shell
+      label: Logs, screenshots, or diagnostics
+      description: Add relevant logs or sanitized diagnostics for connection and data failures; for visual failures, attach a screenshot or quote the exact error. Redact secrets.
     validations:
-      required: true
+      required: false
 
   - type: checkboxes
     id: confirmation
     attributes:
       label: Confirmations
       options:
-        - label: I verified the exact Pulse version and image reference from the running instance.
+        - label: I checked the Pulse version on the running instance and, for a container install, its running image tag or digest.
           required: true
         - label: I searched existing issues for duplicates.
           required: true