Retain recent filesystem-only evidence across safe deferrals without renewing its ten-minute age from VM polls or cached identity. Carry internal source provenance through canonical replacement, preserve independent linked-agent precedence and keep expired values unavailable until a new ordinary read succeeds.
Change-source: pulse-maintainer
Accept the exact Core candidate with retained parent discrimination and containing source proof; preserve existing fallback windows and guest-command admission.
Change-source: pulse-maintainer
Keep the existing reconnect and healthy-guest windows from being renewed by ordinary diagnostic polls. Preserve recent and legacy direct readings, current independent sources and guest-command admission; reject expired, future or unaged retained evidence. Cover boundary, repeated-poll and real-client deferral/recovery behaviour with canonical projection and in-memory History controls.
Change-source: pulse-maintainer
Explain existing current, prior and unavailable disk labels, source precedence and a passive unfiltered inventory review without widening access or bypassing guest-read pauses. Reconcile Primary IP help with the integrated interface-associated collector while preserving unknown associations and virtual-only addresses.
Contract-Neutral: Documentation and source-bound help regressions only; collection, access, UI and safety contracts are unchanged.
Change-source: pulse-maintainer
Replace the obsolete Storage scope warning while preserving saved-rule, current-reading, SMART and passive private-reporting boundaries. Record the fresh inspected desktop and phone browser result for actual composed runtime bytes, including the page-model merge with current main.
Contract-Neutral: Documentation, document controls and fresh browser evidence only; no further subsystem contract or runtime delta.
Change-source: pulse-maintainer
Preserve the original frontend implementation and history alongside the already-qualified Core policy. Combine both subsystem contracts without reviving the retired Recovery fields. Containing source and changed-merge-byte browser proof remain required before candidate acceptance.
Change-source: pulse-maintainer
Preserve the exact reviewed documentation candidate and its source checks. Explain saved alert policy separately from current display limits and native SMART risk.
Change-source: pulse-maintainer
Preserve the exact reviewed Core commits and their qualified source. Address ordering changes no guest query, network configuration or machine identity.
Change-source: pulse-maintainer
Retain exact Delivery 22e9408574 history, effective-mask safeguards, fixture collection repairs and own-parent final-content browser receipts. Installer and frontend VM evidence reviewed; no installed or published acceptance claimed.
Change-source: pulse-maintainer
Distinguish current and last-known heat, saved alert tiers, Off and native SMART risk. Name the Storage display scope limit and keep mismatch reporting passive and private.
Change-source: pulse-maintainer
Contract-Neutral: Documents existing disk policy and a current display limitation; no alert, collection or subsystem contract delta.
Preserve the exact PI candidate and the reviewed main frontier; documentation clarifies existing confidentiality and delivery-evidence limits.
Change-source: pulse-maintainer
Retain the legacy MAC ordering while applying the Podman hint only to displayed IPs, with a discriminating identity control. Use the LXC interface API's actual address wire type in the DHCP fallback fixture.
Change-source: pulse-maintainer
Prefer named guest interfaces over local container networks instead of globally sorting flattened IP text. Preserve all secondary and unknown addresses, management interfaces, warm metadata caches, explicit agent report IPs and machine identity. Cover LXC status/config/runtime fallback, QEMU metadata and canonical list/broadcast projection for issue #2757.
Change-source: pulse-maintainer
Preserve exact Core candidate 31c8422162 and its retained ancestors. The disk policy follows TrueNAS per-disk and platform tiers rather than the synthetic host override; regression controls preserve independent Docker inventory and operator link decisions.
Retained final-source backend normal/race/vet and runtime/embed/API/Patrol/server receipts completed with exit zero and guest stop. Keep the initial failed proof and unlocalised timeout as adverse history. This is source integration, not native recovery or release availability.
Change-source: pulse-maintainer
Keep operators and triage from treating intentional response privacy as missing evidence. Explain HTTP verdicts, uncertain receipt after read failures, bounded Test response counts and the safe use of existing receiver records without Debug capture or a duplicate send. Preserve historical-log and export privacy limits in both shipped guides and intake guidance.
Change-source: pulse-maintainer
Contract-Neutral: Clarifies existing diagnostic confidentiality and receipt limits; no delivery, access or subsystem contract change.
Reconcile the returned timer-discovery repair: both exact units must have a successful bounded unmasked inventory before shared asset staging. Keep configured, runtime and off-destination persistent masks and all assets unchanged across every installer consumer, explicit setup and sandbox repair. Unknown or failed inventory stops replacement; enabled and disabled refresh remains consent-preserving.
Change-source: pulse-maintainer
Preserve the exact reviewed documentation candidate and its privacy-safe existing-view workaround. Retained focused checks cover unchanged guide and UI inputs; this does not establish collector recovery or released availability.
Change-source: pulse-maintainer
Review the VM monitoring intent before suggesting effective read-permission checks. Preserve deliberately restricted tokens, separate a denied reading from guest health, and defer access changes and live checks during backup or guest incidents. Carry the same advice through shipped filesystem help and check current, retained and refreshed production views.
Contract-Neutral: Error-copy and mirrored-help clarification with regression and browser evidence only; collection, API, authorisation, identity, freshness and subsystem contracts are unchanged.
Change-source: pulse-maintainer
Preserve exact retained Core ancestry while retaining the accepted Assistant target, webhook confidentiality, log-viewer and installer repairs. Qualify the composed source against the original seven-package, inventory-control and real embed/API/Patrol recipe; source acceptance remains separate from native recovery.
Change-source: pulse-maintainer
Match complete systemctl inventory rows by exact unit field with bounded reads, so updates and reinstalls reach the existing helper refresh. Preserve deliberate timer and updater masks instead of replacing their symlinks. Exercise all five installer consumers, unchanged settings and enablement, failure/timeout controls and actual fixture-root systemctl inventory.
Change-source: pulse-maintainer
The connected response audit found one remaining receiver-text sink: malformed Retry-After values were copied verbatim into Debug logs. Keep the fixed fallback diagnostic and bounded parsed durations, without retaining invalid header prose. Two regression cases reproduce the leak on the preceding candidate and preserve retry and terminal status behaviour.
Change-source: pulse-maintainer
Receivers can echo tokens, alert content or private provider data in a response or body-read error. Ordinary, enhanced and ntfy recovery senders now retain structured HTTP verdicts and bounded byte counts without retaining or formatting that text. Test keeps its existing response shape with an explicit withheld-body summary.
Preserve authoritative failure classes, retry hints, wrapped read causes, occurrence/payload identity, request credentials and the existing 1 MiB read cap. Regression controls reproduce disclosure on the parent and cover the real senders, retry history, interrupted replies, cleanup and bounded summaries. No historical diagnostic rewrite or native provider acceptance is claimed.
Change-source: pulse-maintainer
Separate selected guest addresses from default-route and reachability evidence. Point API-only LXC users to existing interface/address context, without asking them to alter bridges, install agents or expose network identities.
Contract-Neutral: Documentation and static assertions only; no guest collection, identity, routing, API or frontend runtime contract changes.
Change-source: pulse-maintainer
Bind session-derived targets only when current inventory has one canonical match. Preserve explicit canonical IDs over stale session aliases and return conflicting candidates before planning. Keep unique lookup, session registration, capability policy, approval and execution boundaries intact. Listener-free control tests and exact-parent regressions verify this repair; it does not establish native recovery.
Change-source: pulse-maintainer
The departmental-token report in Pulse #2756 distinguishes intended access denials from missing monitoring rights. Explain the existing per-connection selection limit, why display and alert filters do not stop reads, and why those denials do not justify broader grants or unhealthy-node conclusions. Preserve the same boundary in shipped help and a focused documentation assertion.
Contract-Neutral: Documentation-only clarification and its regression assertion; no runtime, API or subsystem contract delta.
Change-source: pulse-maintainer
Keep archive and sidecar downloads in owner-only staging, clean only owned leaves after handled failures and bootstrap exit, and preserve caller-provided inputs. Require the piped LXC installer signature before copying or execution instead of trusting PID-named files in shared tmp.
Exercise the actual download, prefetch and complete container bootstrap through confined offline doubles and real fixture SSH signatures. Preserve version, archive re-verification, staging-before-stop, service recovery, timer consent and removal boundaries; native acceptance remains separate.
Change-source: pulse-maintainer
Merge the exact reviewed PI candidate 10678304d0. Retained 39 passing component checks and six failing exact-parent regressions cover delayed metadata classification; no frontend runtime or public-state mutation is introduced.
Change-source: pulse-maintainer
Accept reviewed Delivery b155982e30 with retained confined menu, selector, signed-update and removal controls. Preserve current documentation frontier and exact candidate ancestry; no frontend source or infrastructure change.
Change-source: pulse-maintainer
Use the reviewed server-only selector in the existing-installation menu and bind automatic selection to available channel rows. A current selected release is a no-op; unavailable metadata or an automatic downgrade stops before mutations. Preview selection retains its channel, numeric beta/RC revisions compare correctly, and deliberate reinstall pins the actual current version.
Execute the actual menu through confined offline transport and stopped mutation boundaries. Preserve explicit version, interactive removal, signature and all-unit quiescence contracts; reconcile the inherited comment-only preview assertion with the real selector consumer.
Change-source: pulse-maintainer
Read the live report and label set instead of a delayed event snapshot. Stop on failed or mismatched reads, skip closed issues and pull requests, and do not restore decomposition work from superseded events. Keep individual label deltas and community-owned retest decisions; remove the unrelated release lookup. Add six discriminating regressions and document the boundary.
Change-source: pulse-maintainer
Contract-Neutral: Repairs the existing metadata synchronizer without changing issue-form fields, supported labels, public contact or disposition authority, product APIs or subsystem contracts.
System Logs pauses and clears only its browser display, while Support Bundle exports server logs and configuration. Explain those existing limits, warn about Debug's private guest details, and qualify warn-level suppression without changing runtime or recommending new probes. Keep the three shipped guides in sync and exercise their safety boundaries in the existing docs check.
Contract-Neutral: Documentation and focused guidance checks only; existing log controls, exports, monitoring, API and backup policy are unchanged.
Change-source: pulse-maintainer
Retain exact reviewed PI commit af6cc9019f and its software-versus-chart explanation. Resolve AUTO_UPDATE overlap by retaining the newer canonical text byte-for-byte, including installed paths, private-edition and failed-helper safeguards; align the inherited wording assertion additively next.
Change-source: pulse-maintainer
Accept exact reviewed Delivery commit 56fec40f2d with retained offline selector, signed-recipe and resilience controls. No third-party helper repair or installed update is claimed.
Change-source: pulse-maintainer
Use one complete-metadata selector for installer URLs and server archives. Exclude chart and draft releases, reject unusable metadata and transport bodies, and preserve explicit pins, signed assets and downgrade refusal. Exercise the actual selectors with bounded offline controls and retain native installation as separate acceptance.
Change-source: pulse-maintainer
Contract-Neutral: Restore server-only discovery within existing stable/preview channels; installer authority, signatures, architecture admission, downgrade refusal and state contracts are unchanged.
Accept the exact reviewed Web candidate d96ab64e01. Retain its focused documentation checks and inspected desktop/phone evidence; no updater repair or installed recovery is claimed.
Change-source: pulse-maintainer
Preserve the exact prior Core history alongside current canonical Patrol resource-owner resolution and recovery cleanup. Runtime source retains the TrueNAS alert-policy repair and sequential repeated-name Docker assertions; current bytes require isolated qualification.
Change-source: pulse-maintainer
Merge exact upstream 7f466fc183 without re-parenting its reviewed history. Retain both independent contract sections in the two documentation conflicts; no frontend resolution or runtime correction.
Change-source: pulse-maintainer
Use the ownership-checked existing-installation procedure for LXC and systemd update help instead of unconditional /bin/update commands. Explain chart selection without asserting a latest-pointer cause, and preserve exact signed downloads, private editions and existing state.
Contract-Neutral: Documentation-only update guidance and regression checks; no installer, updater, API or frontend runtime behaviour changes.
Change-source: pulse-maintainer
Keep server-update help from treating a community helper as Pulse's signed updater or choosing a Helm chart as a server archive. Preserve current-state checks, full-state backup precautions and the existing signed route after a failed update.
Contract-Neutral: Clarifies existing update routes and release identities; no runtime, API, release policy or subsystem contract change.
Change-source: pulse-maintainer
Host filesystem alerts identify a disk child that Patrol does not collect as
a separate resource. Bind an exact collected alert to its current canonical
owner through the shared inventory contract, including linked agents, and
retain its filesystem, threshold and breach evidence in the scoped prompt.
Keep missing owners, ambiguous source identities and uncollected child
subjects fail-closed. Add evaluator-to-handler, repeated scope resolution
and browser admission coverage.
When a Docker image update is available but the server refuses
execution, an Update button suggests Pulse can still apply it. Show a
readable amber Update available badge with a lock indicator. Its hover,
tap and keyboard-focus explanation preserves the server refusal and
directs the operator to their container manager on the host. Keep
available updates and audited action progress usable.
Validation: 15 update-control regression tests, frontend typecheck, full
commit governance checks and frontend lint. Browser verification at
1440, 900 and 390 pixels covers light/dark styling, hover, keyboard,
dismissal, passive status clicks and the available update review flow
using fixture responses without dispatching updates.
Muted two-line statuses obscure available image updates and expand otherwise compact container rows. Use one amber badge with a lock indicator, keeping the server refusal and host guidance in its accessible explanation.
An Update control suggests Pulse can apply an image even when the host cannot execute commands. Show update availability and host guidance with the server refusal, while preserving audited reviews and progress for actions that can run.
Preserve d525ef6583 and reviewed 7f026a40 ancestry. Keep current main node-pair source attribution and holder-bound folds, add the preserved API seed and snapshot-threshold lifecycle controls, and retain upstream disk-exclusion semantics. No frontend source changed.
Change-source: pulse-maintainer
pulse-triage[bot]