mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-24 04:33:17 +00:00
pulse-triage[bot]
835f88576f
Preserve the existing authoritative selected-memory annotation through raw, API, unified and canonical frontend projections. Qualify current, last-known, unknown and unavailable drawer context from its own original source/time, not disk deferral or renewed guest LastSeen. Keep retained numbers separate from current legends and stored points, including measured zero, denied history and independent live readings. Memoize History reads by actual target/range coordinates so same-guest snapshot replacements update without extra reads or chart remounts. Complete connected source controls and owning subsystem contracts; record the inspected 24-case Chromium/WebKit desktop and narrow light/dark proof against this commit's own parent. No route, collector, threshold, retention, permission or native recovery claim. Change-source: pulse-maintainer
Browser verification receipts
Each commit that changes user-visible frontend source adds one receipt here. The file name is the fingerprint of the content the receipt verified, so no two changes write the same file and open frontend pull requests cannot conflict on their receipts.
Create the skeleton for the staged change, then fill it in after the browser pass:
python3 scripts/release_control/browser_verification_guard.py --write-template
Do not edit, rename or delete another change's receipt in a commit that adds
one. A receipt is read from the commit that recorded it, so receipts whose
commits are already on main are dead weight; remove them in a change that
records none:
python3 scripts/release_control/browser_verification_guard.py --prune
The rules live in the Frontend Browser Verification Gate section of
docs/release-control/v6/internal/CANONICAL_DEVELOPMENT_PROTOCOL.md.