Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Integrate reviewed parsed report-intake safety proof

pulse-triage[bot]5060e1b6b8bc
diff --cc docs/release-control/v6/internal/subsystems/deployment-installability.md
index 83873fd1bc,290dcf6319..703c05d3d1
--- a/docs/release-control/v6/internal/subsystems/deployment-installability.md
+++ b/docs/release-control/v6/internal/subsystems/deployment-installability.md
@@@ -15,25 -15,27 +15,34 @@@
## Purpose
- ### Self-contained release feedback precautions (4 October 2026)
-
- Bug and RC feedback forms carry their collection and attachment precautions
- inline. A reporter must not need an unpublished branch-tip or candidate-commit
- documentation link to learn that Run Diagnostics makes live API/guest-agent
- requests, that an already displayed result can be exported without another
- run, or that attachments require local privacy review. Collection during
- backups, freeze/thaw or an unresponsive-host incident is not an intake
- requirement. Removing a documentation link must retain these precautions and
- all existing report fields; it does not change release readiness or installed
- recovery acceptance.
-
- Verification: the report-form regression in
- `frontend-modern/src/utils/__tests__/docsLinks.test.ts` checks both forms for
- self-contained safety/privacy text and rejects candidate or branch-tip docs
- links. The issue-triage tests and repository documentation drift guard retain
- their independent intake and runtime-link checks.
-
+ ### Report intake remains safe without unreleased documentation
+
+ The bug and prerelease report forms carry their collection and attachment
+ precautions in the form itself. A branch-tip troubleshooting link must not be
+ needed to understand the advice for an installed release. Keep live API and
+ guest-agent checks distinct from downloading an already displayed result;
+ never request another run during backup freeze/thaw or an unresponsive-host
+ incident merely to file a report. Existing observations and the original
+ sequence remain valid evidence.
+
+ Both forms require local privacy review even for exports labelled sanitized,
+ and warn against attaching credentials, session cookies, secret URLs, private
+ host/network or personal details, configuration files and raw request exports.
+ Removing or pinning a documentation link must not remove those precautions or
+ turn evidence fields into mandatory live checks. The existing optional
+ attachment fields are `logs` in the bug form and `evidence` in the prerelease
-form; their common label is "Logs, screenshots, or diagnostics". The form parsing controls in
++form; their common label is "Logs, screenshots, or diagnostics". The form
++parsing controls in
+ `scripts/release_control/release_promotion_policy_test.py` and the existing
+ community intake tests preserve this installed-version-safe behaviour; they
+ are source checks, not native diagnostic, guest-thaw or release acceptance.
+
++The connected report-form regression in
++`frontend-modern/src/utils/__tests__/docsLinks.test.ts` also checks both forms
++for self-contained safety/privacy text and rejects candidate or branch-tip
++documentation links. Repository documentation drift and issue-triage controls
++retain their independent intake and runtime-link checks.
+
### Update History consent does not infer the backup's restore scope
The confirmation names the observed running server separately from the selected