gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-24 04:33:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Compose retained guest History correction with current main

Browse Source 
Preserve the exact reviewed History candidate and its own-parent browser receipt. The updated main frontier changes setup help only; executor readiness and complete source qualification remain unfinished.

Change-source: pulse-maintainer
This commit is contained in:
pulse-triage[bot]
2026-10-04 04:54:36 +01:00
parent a6b83db5bb 28bb0fb51a
commit ba8b9fcd32
12 changed files with 928 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release-control/v6/internal/subsystems/frontend-primitives.md
+21
View File
@@ -69,6 +69,27 @@ The legacy Workloads `DiskList` is exercised only by tests/fixtures, not a
shipped caller. Its empty-state title is not evidence of readable touch guidance;
the shipped guest Overview supplies the readable pre-sample explanation.
Guest History applies the same provenance to its live legend fallback. A VM
filesystem reason withdraws the `current` disk fallback; only a `prev-` reason
with a valid retained value supplies a separately labelled `last known` value.
Explicit telemetry unavailability and unknown/non-finite values stay unavailable,
not zero. The readable fixed-reason notice remains beside the utilization group
even when stored disk observations exist. Its wording identifies a live read,
not the date or provenance of those stored points. Legend assistive descriptions
reference that notice. CPU, memory and I/O evidence remain independent.
Deferred live evidence never supplies a chart point, timestamp or dated
inspection value. Keyboard/pointer inspection continues to show only the
selected stored observations, and denied History withdraws the whole chart
including its deferred evidence. Fresh same-VM evidence clears the notice;
lock clearance without a new read does not. `GuestDrawer.test.tsx`,
`GuestDrawerHistory.disk-provenance.test.tsx` and `GuestDrawerHistory.sparse.test.tsx`
cover the model, actual drawer plumbing, shared fallback precedence, retained
zero, pre-sample status, dated inspection, access denial and resumption.
`browser-tests/guest-history-provenance.cjs` uses the production full drawer
and History API client at desktop and touch widths with synthetic responses.
These checks do not establish native guest thaw, collection or release availability.
### Completed guest backup evidence versus current activity
The guest Overview keeps the last completed backup age and its existing
docs/release-control/v6/internal/subsystems/performance-and-scalability.md
+13
View File
@@ -15,6 +15,19 @@
## Purpose
### Guest History live filesystem provenance
The guest drawer derives deferred filesystem context from its current snapshot,
separately from current CPU, memory and I/O. A retained `prev-` value may populate
only the labelled last-known legend, never the current fallback or chart geometry.
The added presentation input does not create a polling timer, trigger a guest
read, or change History target/range ownership. Stable-target context updates
reuse the mounted chart and existing query; the drawer's pre-existing target
recomputation on guest-snapshot changes is unchanged. Mounted regressions in
`GuestDrawer.test.tsx` and `GuestDrawerHistory.disk-provenance.test.tsx` verify
the actual fallback/resumption path and request counts. This is presentation
proof, not a native CPU improvement, QGA/thaw result or delivery acceptance.
### Guest filesystem provenance preserves dense row geometry
Visible retained/unavailable filesystem cues must fit the existing dense row