mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 13:39:47 +00:00
pulse-triage[bot]
247d39af39
## What changed and why Keep Proxmox guest readings, alerts and History owned by the live connection that collected them. A completed obsolete poll must not republish after connection replacement, retirement or runtime shutdown. Both enumeration routes now stage the complete guest generation and its effects before publication. Caller detail-budget expiry still preserves already collected inventory, without granting another read or fallback. Make FreeBSD rc.d and SysV agent removal retain recovery material until shutdown, process absence and disabled boot activation are confirmed. Refused, incomplete or ambiguous observations stop removal; a partially stopped installation is not automatically restarted. Existing systemd/OpenRC protections remain. Keep the guest memory explanation's agent-setup advice safe: defer setup, restarts and live guest-agent probes during backups or an incident. The underlying percentage, source and reading age are unchanged. These are bounded maintenance steps for reported workload safety, restart recovery and safe removal, not whole-report completion. Related to #1099, #2439, #2619, #2762 and #2822. Native recovery, independent thaw, Windows removal and installed acceptance remain separate. ## Included source Complete unpublished range: `dba4b722af3f1e9a648b09ace9484a1cfc26f785..d4e89c1a1bd7892b3fc16441365a90a15139efd4`. - Guest publication candidate: `1ccc3651fdd611a1d5da47c5d44659fbcd4c2773` through `08a7eaf70d8452c223e05b19ce2bd7866bbb237d`, integrated at `ac00b9ec782b1a5964c3a9b00cdd19775293d6fc`. - Recovery-preserving removal candidate: `bad484550830d19569e0332c96c495e71c1694d6` through `65f813c49758c663380ad0179e5cce3245615baf`, integrated at `7bda196005275cd25da63776db8eadc500c0066d`. - Memory setup precaution: `c776990b817b6a96d02abc38692960c2be578419` and compatibility-fixture correction `9327bc02409ffe3f07d14b8f560d6fb75d492f46`, integrated at starting reviewed tip `020a7be6bf2a2923c291395a8409ed79ddcde336`. - Additive upstream composition `b523c0b6f33b6cc0ddcb36b967b05fffa7f63b4a` contains the published backup guide unchanged. It has the same source tree as the starting reviewed tip. Every accepted commit identity and ancestry is preserved. - Additive correction `6281d6e0008aec029b5cc7f79820ed46159aa17a` reconciles the canonical Docker-ingest source guard with both routes through the ownership gate, retaining the canonical state-update assertion and all behavioral withdrawal controls. It changes no runtime source. - Additive upstream composition `a61f14c823be5ee99f20b2aa2eb3808eff83645d` incorporates the published second-beta metadata-test repair at `171f003a04950b53e577019398961758eb32d91c`. Its exact object was already present; no transport or history rewrite was needed. - Final additive composition `d4e89c1a1bd7892b3fc16441365a90a15139efd4` incorporates published beta.2 metadata at `dba4b722af3f1e9a648b09ace9484a1cfc26f785`. The bounded upstream refresh completed at the requested identity with source unchanged before this merge. It adds no new maintenance scope or release action. ## Validation and limits Publication provenance, whitespace and all fifteen per-commit completion guards pass. The complete-range browser guard validates the unchanged source-bound memory precaution receipt. Recorded candidate evidence includes 33 guest scenarios and both original 500-guest budget controls, 60 removal methods and ten targeted installer fixtures, and 40 grouped browser checks with twelve captures recorded as inspected. Unchanged sufficient browser evidence was not replayed merely for batching. Earlier Go 1.26.8 results remain diagnostic rather than matching the declared compiler. - `source-ji6j004_` on the first composition observed Go 1.26.9 and failed the stale direct-publication assertion. The complete failure remains retained; later vet/installer steps were not reached. - Corrected `source-krkur1bl` on `6281d6e0008aec029b5cc7f79820ed46159aa17a` passes the targeted Proxmox/guest-ownership race suite, monitoring vet, shell syntax and twelve targeted installer/consumer tests, including fifty Python removal controls executed through their production-function wrappers. It uses Go 1.26.9, exits zero, collects complete output and confirms guest stop. These monitoring and agent-removal bytes are unchanged in the final composition. - `source-9u5ig0nx` passes 62 frontend tests, full types, changed-source formatting/ESLint, the production/embed build and every bundle budget. Exit zero, complete output and guest stop are recorded. The final frontend delta from that proof is only the already-published upgrade-guide mirror; JavaScript, styles, manifests and browser-verified inputs are unchanged. - `source-p3ht5oy2` verifies the reconciled canonical ingest guard and the newly published prerelease-predecessor helper/current prerelease metadata on `a61f14c823be5ee99f20b2aa2eb3808eff83645d`. Two stable-packet checks correctly skip on prerelease source. Go 1.26.9, zero exit, complete output and guest stop are recorded. The later beta.2 metadata is validated separately on the final tip. - Exact final `source-sl4t8d7o` on `d4e89c1a1bd7892b3fc16441365a90a15139efd4` passes shell syntax and the prerelease-predecessor/current beta.2 install-metadata checks on Go 1.26.9. The two stable-packet checks remain explicitly skipped. Exit zero, complete 1,485-byte output and completed guest stop are recorded. Earlier receipts retain their reporting-line-bound flags without loss of their complete raw output. These checks do not establish installed restoration, native guest safety, Docker qualification, release readiness or publication of this maintenance. Administrative review and all required exact-head hosted checks still govern landing; any advisory failures need an evidence-based disposition. [How Pulse handles triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)