From 968e7c5a278732dbec680dec5159917ff3102bdf Mon Sep 17 00:00:00 2001
From: "pulse-triage[bot]"
 <249995291+pulse-triage[bot]@users.noreply.github.com>
Date: Tue, 29 Sep 2026 14:21:28 +0100
Subject: [PATCH] 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 | 13 +++++++------
 docs/ISSUE_TRIAGE.md                  |  7 +++++++
 2 files changed, 14 insertions(+), 6 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 66ac87d22f..15df537f39 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.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
diff --git a/docs/ISSUE_TRIAGE.md b/docs/ISSUE_TRIAGE.md
index 0923612244..4b22611670 100644
--- a/docs/ISSUE_TRIAGE.md
+++ b/docs/ISSUE_TRIAGE.md
@@ -15,6 +15,13 @@ Reporters may still write free-form issues, edit form output, or discover a
 second topic during discussion. Triage owns decomposition in those cases; it
 must not require the reporter to refile information they already supplied.
 
+The bug form asks for the version on the failing running instance, not merely
+the version before an upgrade. A running image reference applies only to
+container installs; bare-metal and LXC reporters must not have to attest to
+one. Ask for evidence relevant to the symptom: logs or sanitized diagnostics
+for connection and data failures, and screenshots or exact error text for
+visual failures. Do not make a reporter invent logs where none apply.
+
 ## Required disposition
 
 Before removing `needs-decomposition` or declaring a mixed report triaged: