Explain how to find CORE graph responses without exposing a capture

The CORE reporter could find requests but not the matching replies. Clarify Firefox message filtering, per-request IDs, CPU versus temperature and bounded response sharing in the canonical and shipped guide; keep secrets and full captures out of diagnostics. Add guidance regression coverage while preserving the existing authenticated connection recipes.

Change-source: pulse-maintainer

docs/TRUENAS.md

@@ -175,9 +175,31 @@ Check whether the corresponding graphs work in the TrueNAS web UI. If Pulse
 still shows missing readings, report the affected panels, running Pulse and
 TrueNAS versions, and the relevant sanitized evidence above. Do not replace
 an otherwise working key or clear stored History merely because a graph is
-empty. When sharing a requested native graph response, include only its graph
-name, `legend`, timing fields and one `data` row or error; omit authentication
-messages and identifying details. Do not upload a full browser network capture.
+empty.
+
+If a maintainer requests a **CORE 13 native graph response**, use your existing
+signed-in **TrueNAS** browser session, not the Pulse page:
+
+1. In Firefox on macOS, open Network with **⌘⌥E**, then reload with Network
+   recording. Select **WS**, select the WebSocket connection and open its
+   **Response** pane.
+2. Show **All** messages and clear any message search for `reporting.get_data`.
+   The incoming reply does not need to repeat the method name, so that search
+   can hide the evidence. Open the CPU or Memory graph on TrueNAS's Reporting
+   page while recording.
+3. Find the outgoing `"msg":"method"` request with `"name":"cpu"` or
+   `"name":"memory"`; `cputemp` is temperature, not CPU usage. Each request has
+   a different `id`, which is normal. Find the incoming `"msg":"result"` reply
+   with the **same `id` as that request**, and expand its `result` (or `error`).
+   The `legend`, timing fields and `data` belong to the response, not the
+   outgoing request's `params`.
+4. Share only the requested graph name, `legend`, timing fields and one `data`
+   row, or the matching sanitized error. If no matching incoming reply is
+   visible after the graph loads, report that instead of sending more requests.
+
+Omit authentication messages, keys, cookies, private hostnames and addresses.
+Do not upload a full browser network capture or paste code into the browser
+console to collect this evidence.
 
 ### Stale TrueNAS data
 - If TrueNAS data stops updating, the source status transitions to `stale` after ~120 seconds.

frontend-modern/public/docs/TRUENAS.md

@@ -175,9 +175,31 @@ Check whether the corresponding graphs work in the TrueNAS web UI. If Pulse
 still shows missing readings, report the affected panels, running Pulse and
 TrueNAS versions, and the relevant sanitized evidence above. Do not replace
 an otherwise working key or clear stored History merely because a graph is
-empty. When sharing a requested native graph response, include only its graph
-name, `legend`, timing fields and one `data` row or error; omit authentication
-messages and identifying details. Do not upload a full browser network capture.
+empty.
+
+If a maintainer requests a **CORE 13 native graph response**, use your existing
+signed-in **TrueNAS** browser session, not the Pulse page:
+
+1. In Firefox on macOS, open Network with **⌘⌥E**, then reload with Network
+   recording. Select **WS**, select the WebSocket connection and open its
+   **Response** pane.
+2. Show **All** messages and clear any message search for `reporting.get_data`.
+   The incoming reply does not need to repeat the method name, so that search
+   can hide the evidence. Open the CPU or Memory graph on TrueNAS's Reporting
+   page while recording.
+3. Find the outgoing `"msg":"method"` request with `"name":"cpu"` or
+   `"name":"memory"`; `cputemp` is temperature, not CPU usage. Each request has
+   a different `id`, which is normal. Find the incoming `"msg":"result"` reply
+   with the **same `id` as that request**, and expand its `result` (or `error`).
+   The `legend`, timing fields and `data` belong to the response, not the
+   outgoing request's `params`.
+4. Share only the requested graph name, `legend`, timing fields and one `data`
+   row, or the matching sanitized error. If no matching incoming reply is
+   visible after the graph loads, report that instead of sending more requests.
+
+Omit authentication messages, keys, cookies, private hostnames and addresses.
+Do not upload a full browser network capture or paste code into the browser
+console to collect this evidence.
 
 ### Stale TrueNAS data
 - If TrueNAS data stops updating, the source status transitions to `stale` after ~120 seconds.

scripts/tests/test_truenas_docs.py

@@ -70,6 +70,25 @@ class TrueNASDocsTest(unittest.TestCase):
         self.assertIn("does not establish a live reading", text)
         self.assertIn("Do not upload a full browser network capture", text)
 
+    def test_core_graph_guidance_distinguishes_request_from_reply(self):
+        text = DOC.read_text().split("### Inventory works but CPU, memory or History is missing", 1)[1]
+        text = text.split("### Stale TrueNAS data", 1)[0]
+        for required in (
+            "signed-in **TrueNAS** browser session, not the Pulse page",
+            "In Firefox on macOS", "**WS**", "**Response** pane",
+            "Show **All** messages", "clear any message search for `reporting.get_data`",
+            'outgoing `"msg":"method"`', 'incoming `"msg":"result"`',
+            "**same `id` as that request**", "expand its `result` (or `error`)",
+            "`cputemp` is temperature, not CPU usage",
+            "response, not the\n   outgoing request's `params`",
+            "one `data`\n   row", "no matching incoming reply",
+            "Omit authentication messages, keys, cookies, private hostnames and addresses",
+            "Do not upload a full browser network capture or paste code into the browser",
+        ):
+            with self.subTest(required=required):
+                self.assertIn(required, text)
+        self.assertNotIn("```", text)
+
     def test_preparation_protects_new_and_existing_payload(self):
         preparation, _ = commands()
         with tempfile.TemporaryDirectory() as temporary: