Files
pulse/docs/release-control
pulse-triage[bot] be5a59d66c Keep incomplete backup entries out of completed restore totals (#3218)
**Keep incomplete backup entries out of completed restore totals**

Use the same completion predicate for latest backups, restore-point and
byte totals, PBS coverage and per-day count/volume charts. Keep running
and failed entries visible, with separate counts and honest
inventory-entry labels. Completion is not verification, restore or guest
thaw.

Add registered model and consuming-table regressions for mixed and
incomplete-only inventories, unknown chronology and completion
transitions. Guest operations and server policy are unchanged.

Contract-Neutral: Apply established completion semantics and
inventory-entry wording only; resource transport, identity, persistence
and shared table contracts are unchanged.

**Use supported role-query options in backup completion tests**

The committed-source type check rejected exact on ByRoleOptions. String
role names already match exactly; remove the two unsupported options
without changing assertions or runtime source.

**Verify completed backup totals in production browsers**

Record actual production-asset proof at 1440px Chromium and 320px
WebKit, including count/volume, incomplete-only inventory,
keyboard/touch details and Coverage navigation. Preserve initial driver
failures and targeted follow-up evidence; all fourteen retained captures
were opened natively.

Keep the both-inventories-failed negative assertion matched to the new
completed-point wording, so it still rejects a fabricated zero summary
rather than merely rejecting retired copy.

**Keep visible Infrastructure and Patrol text in accessible action
names**

Name Add shortcuts by their action and group, retain update counts and
affected systems, and let Patrol rows expose their full visible
evidence. Preserve scoped handlers, read-only restrictions and native
selection; keep the WCAG rule unchanged.

Contract-Neutral: Accessible-name correction only at unchanged
agent-lifecycle and API boundaries: no enrollment, update execution, API
payload, authorisation, state or route changes. Frontend and Patrol
contracts and registered consuming tests are updated.

**Keep read-only update indicators inert even with a retained callback**

The new read-only control found that the component relied solely on its
parent to remove Agent Doctor callbacks. Guard both responsive chips
locally. Match the existing registry-routing fixture by its displayed
non-resource-leading title.

Contract-Neutral: Enforce the existing read-only UI invariant only; no
agent lifecycle, API, update execution, payload or permission change.
The frontend contract and registered component and Patrol consuming
tests cover the boundary.

**Align Infrastructure architecture guard with visible Add naming**

The complete frontend suite passed 22,274 tests and failed only this
retired source-string assertion. Keep its route-backed action guard and
require the new visible-action/group accessible name instead.

**Verify accessible Infrastructure and Patrol controls in browsers**

Bind final built producer bytes to desktop Chromium and narrow WebKit
interaction/pixel evidence. Preserve the original backup own-parent
receipt and all adverse fixture, query and manual-review results in the
lane receipts.

---
Fleet candidate `20261024T184532Z-web-product` from the `web-product`
lane. Reviewed tip `5f1c3d36fb69772f1371a5a7bc68368e5866ad93` on `main`.

[How Pulse handles
triage](https://github.com/rcourtman/Pulse/blob/main/docs/AI_TRANSPARENCY.md)
2026-10-24 20:30:28 +00:00
..