Commit Graph

326 Commits

Author SHA1 Message Date
pulse-triage[bot] 2476a4e449 Keep historical upgrade recovery non-destructive
Route current upgrades to current guidance; preserve existing login and monitoring state when diagnosing missing PVE backups. Require endpoint-specific access evidence rather than blanket ACL changes or setup-token rotation.

Contract-Neutral: Documentation and regression checks only; no collector, permission, authentication or upgrade contract changes.
Change-source: pulse-maintainer
2026-10-07 02:25:19 +01:00
pulse-triage[bot] a249ac9d06 Integrate reviewed bounded API shard failure diagnostics
Change-source: pulse-maintainer
2026-10-07 02:08:25 +01:00
pulse-triage[bot] 87c13e4074 Retain bounded API shard failure identities beside timings
Publish failed and unfinished source-test names in the existing shard artifact without waiting for other workflow jobs. Keep logs, timings, test selection and failure exits unchanged; record unknown completion and omitted unsafe or excess identities explicitly. Pin privacy, bounds, pipefail and timing-refresh compatibility, and align the existing shard contract with current compile admission.

Change-source: pulse-maintainer
2026-10-07 01:47:42 +01:00
pulse-triage[bot] da747553d9 Keep connection liveness separate from backup freshness
Source inspection shows connection/agent status is not a dedicated PVE backup last-success control. Use existing collection timestamps where available without inventing a settings field or treating a live agent as fresh backup inventory.

Contract-Neutral: Documentation-only correction of existing PVE backup diagnostics; runtime collection and access contracts are unchanged.
Change-source: pulse-maintainer
2026-10-07 01:05:17 +01:00
pulse-triage[bot] 138901e422 Keep missing PVE backup diagnostics non-destructive
Replace node deletion, registration-state removal and blanket ACL instructions with source-aware checks of existing native evidence, ordinary API collection and the actual rejected request. Preserve credential and backup safety boundaries in the shipped guide, with regression checks against the collector and setup behaviour.

Contract-Neutral: Documentation-only correction of existing PVE backup diagnostics; runtime collection and access contracts are unchanged.
Change-source: pulse-maintainer
2026-10-07 01:03:57 +01:00
pulse-triage[bot] b17d23665f Assert required frontend steps before comparing their order
The omitted-unit-suite control raised ValueError instead of an assertion. Require each step exactly once before checking positions so the control reports the intended missing-check failure.

Contract-Neutral: Regression-test diagnostic only; the frontend workflow and all product contracts are unchanged.
Change-source: pulse-maintainer
2026-10-07 00:07:24 +01:00
pulse-triage[bot] a8271238e1 Check frontend build budgets before the full unit suite
PR2624 spent 8m45s on successful unit tests before its deterministic bundle-size rejection; PR2626 and PR2627 now fail at that same gate. Type-check, build the real embedded assets and apply the unchanged size budgets before spending that test time. Passing source still runs every existing check.

Contract-Neutral: Reorder existing frontend CI commands only; no product interface, dependency graph, bundle budget or required-check change.
Change-source: pulse-maintainer
2026-10-07 00:02:31 +01:00
pulse-triage[bot] 450a551cf5 Reject incompatible Go test fixtures before backend CI fan-out
Compile all race-test binaries without execution only when source, graph, backend embeds or this admission path can affect Go. Preserve required check failures, docs/frontend-only skips and all full runtime/vet and frontend audit checks. Exercise inert and broken fixtures, diff classification and prerequisite propagation.

Change-source: pulse-maintainer
2026-10-06 19:54:22 +01:00
pulse-triage[bot] d554399ae8 Integrate reviewed complete backup-pause restoration guidance
Preserve the exact Web candidate and rendered-help proof. Require independent thaw, every-covered-filesystem writes and liveness, and restore only prior-active service and timer states. No native recovery is claimed.

Change-source: pulse-maintainer
2026-10-06 14:56:27 +01:00
pulse-triage[bot] 837d193960 Explain read-only checks for uncertain workload updates
Give Docker operators the missing host, container and bounded inspection steps before another update, retaining image and receipt uncertainty without exposing configuration.

Contract-Neutral: Existing documentation and synthetic recipe checks only; no runtime, action, permission or update-contract change.
Change-source: pulse-maintainer
2026-10-06 14:40:16 +01:00
pulse-triage[bot] e35df4b777 Make backup-pause restoration conditional on complete workload checks
Put thaw, every-covered-filesystem writes and workload liveness in the opening precaution. Keep post-backup evidence independent of Pulse and QGA, spell out the four prior service/timer states and verify timer restoration without starting a previously inactive server. Cover the rendered decision table and preserve the documented command allowlist.

Contract-Neutral: Clarifies the existing manual backup precaution and prior-active restoration; no collector, service, scheduling, permission or frontend runtime contract changes.
Change-source: pulse-maintainer
2026-10-06 14:38:09 +01:00
pulse-triage[bot] c17d65074b Distinguish login failures by credential source and request path
Replace blanket cookie clearing and hash escaping with source-specific, non-destructive guidance. Keep local lockout, SSO, browser sessions, API scopes and CSRF distinct, and link the existing private recovery recipes. Add six documentation/source-consistency checks and keep the served guide identical.

Contract-Neutral: Documentation and text/source-consistency tests only; existing authentication, permissions, cookies, lockout and request behaviour are unchanged.
Change-source: pulse-maintainer
2026-10-06 13:26:49 +01:00
pulse-triage[bot] a568cbae62 Integrate reviewed source-driven non-API CI balancing
Retain both reviewed commit identities and the exhaustive measured-weight selector. Current-source enumeration, actual workflow failure controls and focused contract proof are adequate for this CI-only diff; failed ISO preparation remains unresolved, not a suite verdict.

Change-source: pulse-maintainer
2026-10-06 13:16:18 +01:00
pulse-triage[bot] 321b1d0c77 Merge commit '7be63facb9a9e14dc026c31fb10928ad1e5f861c' into maintainer-async/20261006T115547Z-delivery-trust/pulse
Change-source: pulse-maintainer
2026-10-06 12:58:01 +01:00
pulse-triage[bot] 34ddb5829d Make contribution reports safe before diagnostic collection
Bring the existing contribution guide and shipped copy in line with live diagnostic behaviour and safe intake: reuse displayed results, defer checks during backup or host incidents, review every public attachment and accept passive or unavailable performance evidence. Four discovered guidance tests protect these distinctions; no runtime or new surface changes.

Contract-Neutral: Existing reporting guidance and its tests only; diagnostic runtime, issue form fields, label automation and release contracts are unchanged.
Change-source: pulse-maintainer
2026-10-06 12:57:53 +01:00
pulse-triage[bot] ffff96767e Preserve upstream release guidance in the integrated disclosure
Reconcile the reviewed disclosure with batch-start upstream 478a03b9ed. Retain early cuts, no scheduled patch releases, promotion enforcement and the user-facing release guide without losing private-support, independent-review or containing-version claims. Extend the focused disclosure assertions to retain the merged guidance.

Change-source: pulse-maintainer
2026-10-06 12:49:16 +01:00
pulse-triage[bot] 74177173c2 Integrate reviewed triage disclosure with the release-train frontier
Preserve exact candidate e0ea064e8f and its privacy, independent-review and verified-availability corrections. Resolve the overlapping disclosure to the reviewed text; preserve upstream early-cut, no-patch and user-guidance details in an additive follow-up.

Change-source: pulse-maintainer
2026-10-06 12:49:01 +01:00
pulse-triage[bot] 7be63facb9 Balance the existing non-API race-test checks by measured package cost
Two completed PR runs put 24 minutes of overlapping package test time on rest-1 versus 14 on rest-0. Assign whole package binaries deterministically by recorded cost while deriving exhaustive coverage from the checked-out go list. Keep both required check names, every race test, failure propagation and the separate contiguous internal/api shards unchanged.

Contract-Neutral: Rebalance existing CI work only; no runtime, required-check, exhaustive coverage, race-test or dependency-admission contract changes.
Change-source: pulse-maintainer
2026-10-06 12:38:46 +01:00
pulse-triage[bot] e0ea064e8f Make triage disclosure match the release train and private support
Remove obsolete selective-backport, model scheduling and automated email claims. Explain all-main cuts, frozen candidates, checked release availability and independent source review on the existing disclosure page and its shipped mirror.

Change-source: pulse-maintainer
2026-10-06 12:08:29 +01:00
pulse-triage[bot] c6294f5654 Correct pre-push receipt fixtures to compare admitted content
Exercise a receipt-only follow-up over unverified outgoing source rather than an unchanged source range, explicitly retain the CI skip when only metadata changes, and compare receipt tree identities across a merge instead of Git display headings. The existing range guard and receipt admission policy are unchanged.

Contract-Neutral: Test-only corrections establish the existing local and CI browser admission semantics without changing production or contract behaviour.
Change-source: pulse-maintainer
2026-10-06 12:07:58 +01:00
pulse-triage[bot] bc89ac1b89 Exercise final browser proof in local delivery preflight
Reproduce the local pre-push gap with real disposable Git histories and the existing browser receipt guard: missing, stale, partial, wrongly parented and nonpassing proof must not receive a local green verdict. Valid own-parent receipts and merges must remain usable without rebinding; upstream-only changes are not outgoing work.

Contract-Neutral: Test-only local delivery admission controls; no runtime, browser receipt rules or protected delivery policy change.
Change-source: pulse-maintainer
2026-10-06 10:29:16 +01:00
pulse-triage[bot] 94abfb3511 Reject incomplete frontend local delivery preflight
Run the existing bounded strict audit before expensive local checks when frontend manifests or its audit runner change. Fail missing frontend dependencies rather than print a passing pre-push verdict after a skipped type-check. Preserve per-commit contract binding, CI gates and the inherited-advisory policy; execute real disposable Git and canned-provider orchestration controls without an external advisory query.

Contract-Neutral: Local developer preflight now reports incomplete checks honestly; no runtime, API, dependency graph or protected CI policy changes.
Change-source: pulse-maintainer
2026-10-06 06:30:11 +01:00
pulse-triage[bot] 056ada5282 Require successful npm audit completion before a clean verdict
Retain the audit child's exit status alongside its captured report. Failed or stopped zero-count reports stay unavailable; positive findings still stop re-query and the existing unchanged-graph warning policy is preserved. Exercise failure, signal and real watchdog controls, and model npm's clean terminal status in the smoke provider.

Change-source: pulse-maintainer
2026-10-06 05:44:41 +01:00
pulse-triage[bot] db966b47f6 Integrate reviewed unattended updater recovery
Accept Delivery candidate 20261006T015404Z-delivery-trust with its exact six commits. Retain verified binary and VERSION backups on incomplete recovery, restore original paths and metadata, and avoid activating partial restores. Reviewed signed offline transaction and installer evidence source-vz0ldvxn; native systemd and released acceptance remain separate.

Change-source: pulse-maintainer
2026-10-06 04:20:01 +01:00
pulse-triage[bot] 6b3ce854f0 Model the failed-installer smoke fixture stop boundary
The complete signed transaction, race controls, installer suite and vet passed, but the older shell smoke fake still refused stop and consequently could not reach its restore/start assertion. Allow only that successful stop boundary and retain the activation assertions. Production updater and its explicit stop-failure controls are unchanged.

Contract-Neutral: Existing failed-installer fixture correction only; production snapshot, rollback and activation contracts are unchanged.
Change-source: pulse-maintainer
2026-10-06 03:51:54 +01:00
pulse-triage[bot] cf92426ec1 Keep rollback replacement portable and model its stop boundary
Reject directory destinations before the same-directory file rename, use portable mode inspection in the connected transaction tests, and teach the existing service fakes that stopping and failed activation are separate operations. The recorded first candidate proof remains bound to its own source.

Contract-Neutral: Preserve the reviewed backup and rollback semantics; portable utility invocation and faithful test boundary only.
Change-source: pulse-maintainer
2026-10-06 03:07:35 +01:00
pulse-triage[bot] e70e2c6430 Make memory troubleshooting passive and process-scoped
Distinguish LXC/container memory charts from Pulse RSS, heap and virtual memory. Add a bounded five-counter sample with process identity readback, failure preservation and private-data cautions. Exercise the copied recipe with synthetic failures and an owned Linux child, preserving the existing CPU/write recipes.

Change-source: pulse-maintainer
Contract-Neutral: Documentation and executable recipe checks only; no runtime or public-contract delta.
2026-10-06 02:52:50 +01:00
pulse-triage[bot] aae30e2baa Explain safe recovery of retained notification failures
A destination edit and a passing Test do not update the settings stored in an old queued delivery. Make the existing recovery help distinguish those paths, explain the passive Telegram header check, and keep the shipped guides in sync. Connect a real rejected HTTP delivery through edit, Test, restart, retained retry and new alert, including current disable, removal and pause controls.

Contract-Neutral: Documents and verifies existing destination-snapshot and retry semantics; no runtime, API, schema or delivery-policy change.
Change-source: pulse-maintainer
2026-10-06 01:30:57 +01:00
pulse-triage[bot] 28c64e3808 Reconcile reviewed monitoring maintenance with published benchmark repair
Preserve the exact reviewed tip and incorporate current origin/main additively before combined-source validation.

Change-source: pulse-maintainer
2026-10-06 00:05:38 +01:00
pulse-triage[bot] 3fe60c8732 Integrate reviewed aligned Go patch graph
Retain exact Delivery commits and current main repairs. Reviewed source-1dqqprfr verifies offline codec and Kubernetes races, runtime checks, vet and real server/agent builds with unchanged manifests. No frontend content is resolved or changed by this integration.

Change-source: pulse-maintainer
2026-10-05 22:55:45 +01:00
rcourtman b027bb0e8e Keep paired PR benchmarks inside their time budget
Since 15:00 UTC on 5 October every paired benchmark run that was not
superseded has hit its 25-minute step timeout. Each step runs ten base
and ten candidate samples, so per-sample growth is multiplied by twenty.

BenchmarkRegistryProjectionSnapshot (#2518) rebuilt a registry behind
StopTimer on every cold iteration. Go sizes b.N from timed work only, so
the empty-registry cases ran hundreds of thousands of untimed ingests
and took 16 s of a 100 ms benchtime. With #2486's new owner-index and
metadata benchmarks, internal/unifiedresources went from 8 s to 38 s per
sample. Cold now invalidates the registry's derived state instead. The
refresh never reads its own output, so this repeats a fresh ingest's
first read with the same allocations, and the family drops from 22 s to
about 5 s per sample.

Paired runs also measured every package even when both trees compiled
identical code, as on frontend-only changes. They now sample only
packages whose in-module dependency closure the change reaches. Module
files, dirty or non-Git trees and an unreadable graph still select
everything.

A module or shared-model change still samples nearly every package,
about 24 minutes with warm-up. The step therefore gets a measured 30
minutes, and the script stops at a 28-minute projected budget with
per-package costs instead of meeting a bare timeout.
2026-10-05 22:39:51 +01:00
pulse-triage[bot] 94971167f2 Compose the acquired Go patch graph with current repairs
Retain the reviewed four-module patch candidate, current disk History, isolated partial-PVE and Patrol changes. Validate this exact composition against the prepared dependency graph before offering source integration.

Change-source: pulse-maintainer
2026-10-05 21:55:09 +01:00
pulse-triage[bot] e8fe8d4af1 Lead Patrol rule removal help with the existing UI
Explain exact rule scope, confirmation and uncertain-result readback in Patrol Activity. Keep the tested administrator-session workaround only for older builds without the controls; denied access is not a reason to use it. Bind help labels to the production controls and preserve the shipped mirror.

Contract-Neutral: Documentation and help regression coverage only; existing Patrol UI, API, suppression semantics, authentication, organisation scope and CSRF contracts are unchanged.
Change-source: pulse-maintainer
2026-10-05 21:51:17 +01:00
pulse-triage[bot] a6c40e693b Keep TrueNAS diagnostic reads bounded and truthful
Remove log filters that hide reader failures and unrelated startup errors. Use current export labels and separate cached downloads from live diagnostics, preserving private evidence and the backup safety boundary.

Change-source: pulse-maintainer
2026-10-05 20:57:01 +01:00
pulse-triage[bot] a0ccb9f3cc Continue managed Go graph repair on current main
Preserve the held four-patch dependency repair and all current main monitoring and UI changes. The two earlier acquisition attempts failed before execution at capacity; this current-source composition still requires exact graph acquisition, fresh launch selection and runtime/build proof before integration.

Change-source: pulse-maintainer
2026-10-05 20:42:53 +01:00
pulse-triage[bot] 310c7e6e51 Document safe removal of mistakenly created Patrol rules
Explain the missing v6.4.5 undo control and the existing scoped API. Verify exact selection, confirmation, browser session and CSRF, failure handling and readback without copying credentials or deleting unrelated rules.

Contract-Neutral: Documentation and regression-proof coverage of existing Patrol suppression APIs only; no runtime, route, authority or subsystem contract changes.
Change-source: pulse-maintainer
2026-10-05 17:14:39 +01:00
pulse-triage[bot] 6e30eb84a9 Keep the managed Go patch group aligned on current source
Update only compress and the Kubernetes trio from proposal 2317. Preserve other dependency and compiler pins and retained checksums. Require aligned patch floors, paired checksum records and exact-graph runtime proof before integration.

Contract-Neutral: Dependency patches and internal graph admission controls only; module names, public APIs, deployment interfaces, managed-runtime orchestration and acquisition security boundaries are unchanged.
Change-source: pulse-maintainer
2026-10-05 14:49:16 +01:00
pulse-triage[bot] 34a568ef65 Keep constrained NAS install guidance private and non-destructive
Match QNAP guidance to existing data-volume relocation, create private per-attempt staging and preserve diagnostic logs and identity. Exercise copied commands for preparation and installer failures without an appliance operation.

Contract-Neutral: Clarifies existing installer storage and private staging guidance; no runtime, permission or data-contract change.
Change-source: pulse-maintainer
2026-10-05 07:25:14 +01:00
pulse-triage[bot] 757ae22ece Integrate reviewed private Metrics History guidance
Preserve the exact reviewed documentation candidate and its retained privacy/query proof; no runtime or storage changes.

Change-source: pulse-maintainer
2026-10-05 07:14:39 +01:00
pulse-triage[bot] c420758068 Keep history diagnostics private and match current query types
Reuse the tested API helper, explain point/source and access distinctions, and preserve data before storage tuning. Copied examples now exercise private success/error responses, redirects, incomplete transport and encoded IDs.

Contract-Neutral: Documentation and recipe checks align with existing history API behaviour; no runtime, storage, entitlement or authentication contract changes.
Change-source: pulse-maintainer
2026-10-05 06:47:09 +01:00
pulse-triage[bot] cadb669610 Integrate reviewed private-help checks without replacing stronger fixtures
Preserve the reviewed candidate commits as the second parent and retain canonical one-shot, redirect, partial-response and disclosure controls in the overlapping API/PBS smoke fixtures. Keep the candidate's canonical PBS guard, scoped private temperature-file assertions and unchanged-verdict audit diagnostics.

Contract-Neutral: Integration of test-only private-help adapters; no runtime, guides, dependencies or frontend source changed.
Change-source: pulse-maintainer
2026-10-05 06:39:53 +01:00
pulse-triage[bot] 4bcca1a100 Scope private helper checks and retain audit retry diagnostics
Bind the new 0600 assertion only to the reviewed temperature cleanup helper rather than impose it on the unchanged public Unified Agent installer recipe. Include the captured canned audit output when its existing one-call assertion fails, preserving verdicts, call counts and timing controls. The complete second proof retains its fail-closed two-call observation without a cause or successful-retry claim.

Contract-Neutral: Test adapter scope and failure diagnostics only; existing guide, audit verdict and timing contracts are unchanged.
Change-source: pulse-maintainer
2026-10-05 05:33:35 +01:00
pulse-triage[bot] eb9cf740bf Preserve copied-recipe isolation across guide smoke tests
Keep the shared direct-curl recorder compatible with the other existing guides while binding API requests to its reviewed private helper. Update the temperature selector to the reviewed fail-closed temporary download and retain disable-first TLS and mode checks. The first broad proof caught both adapter faults before publication.

Contract-Neutral: Test-only adapters for existing reviewed guide contracts; no runtime, guide, dependency or frontend change.
Change-source: pulse-maintainer
2026-10-05 05:20:34 +01:00
pulse-triage[bot] 8ad902ed1f Bind guide checks to private PBS and API response recipes
Repair deterministic governance and script-smoke failures against the reviewed guides without restoring public response output, literal credential commands or clobbering downloads. Exercise the actual shared API helper and independently verify private, unique response files, methods, bodies and hostile curl defaults.

Contract-Neutral: Update test adapters for the existing reviewed credential-private guide contract; no runtime or guide change.
Change-source: pulse-maintainer
2026-10-05 04:59:34 +01:00
pulse-triage[bot] 5082c60d27 Restore documentation fixtures for private API and PBS recipes
Execute the actual API helper and PBS private-file/download handoffs, keeping their response-privacy assertions separate from shared credential-transport fixtures. Verify one-shot requests, exact methods and JSON, retained private responses and failure exits, TLS and preparation. Match the temperature cleanup test to its current non-clobbering download, without changing any guide.

Contract-Neutral: Repair connected documentation fixtures only; no guide, mirror, runtime, API, authentication, dependency or permission contract changes.
Change-source: pulse-maintainer
2026-10-05 04:35:48 +01:00
pulse-triage[bot] 3a0a7f6302 Fail closed on oversized or corrupt passive VM reads
Bound the existing passive preflight before Bash can discard NULs or accept unlimited configuration output. Preserve producer errors independently, isolate the byte reader from Python startup hooks, and keep the copied helper and mirrored help private and off the guest-agent channel.

Contract-Neutral: Operator diagnostics and existing help only; Proxmox polling, guest-agent coordination, APIs, storage and service behaviour are unchanged.
Change-source: pulse-maintainer
2026-10-05 02:44:26 +01:00
pulse-triage[bot] 1f0d12af85 Match safety fixtures to private responses and native platforms
PR2472 build run 37239183545 extracts no wrapped TrueNAS recipes; exercise all three current blocks and retain synthetic HTTP response bodies only in private files, including 201 save and error controls. Native run 37239183481 expects a Linux QGA capability on macOS and Windows; assert non-Linux agents do not advertise it and scope the connected PVE fixture to its actual Linux runtime. Production safety and documentation remain unchanged.

Contract-Neutral: Test-only reconciliation of already-reviewed private-response recipes and existing Linux-only guest-execution capability; no product contract change.
Change-source: pulse-maintainer
2026-10-05 00:08:47 +01:00
pulse-triage[bot] af73b0e6c6 Keep fenced shell comments inside the selected diagnostics section
The first publication correction retained the two original defects as history but its heading matcher treated the reviewed shell comment as a boundary. Parse headings only outside fenced blocks, and pin comment, duplicate-heading and missing-heading controls. All 17 passive diagnostics and safety-boundary fixtures now pass; no production or guidance bytes changed.

Change-source: pulse-maintainer
2026-10-04 18:43:10 +01:00
pulse-triage[bot] c4a72995c6 Keep passive VM diagnostics separate from planned server pause controls
The completed PR smoke job demonstrates two obsolete whole-guide assertions after the reviewed manual backup precaution added six server-control examples. Select the unique passive preflight section for helper execution, constrain planned pause examples exactly, and reject active probes or service operations outside that section. Production code and safe guidance remain unchanged.

Change-source: pulse-maintainer
2026-10-04 18:40:58 +01:00
pulse-triage[bot] c7bb48f0b4 Clarify the existing webhook correlation contract
Keep canonical guidance aligned with the actual unchanged header and copied member-aware templates. Pin the correction in the same safety guard so a later maintainer does not restore permanent header-only deduplication.

Contract-Neutral: Documentation clarification and its verification only; webhook wire format, retry stability and runtime behaviour are unchanged.
Change-source: pulse-maintainer
2026-10-04 08:44:50 +01:00