# HRC Delete No-Blink QA Evidence

Date: 2026-05-27 | Environment: dataverse-ehr.local | Scope: patient Documents and Results delete flow

## Reported Behavior

When the user confirms delete on a document / health-record row, the patient screen blinks. It is small on a single delete, but becomes continuous and annoying when multiple delete operations happen.

## Fix

- Health-record delete no longer routes through the global patient `syncLoading` wrapper.
- The delete saga still performs the same backend delete and same local health-record update, but does not toggle page-level `loadingPatient`.
- The touched delete path also now stores a valid formatted `updatedAt` timestamp instead of constructing an invalid Moment value.
- The QA scratch rule was tightened so generated screenshots/videos/logs/recorders stay under gitignored workspaces.

Primary files: `document_root/web/src/redux/patient/saga.js`, `document_root/web/src/redux/patient/saga.test.js`, `AGENTS.md`.

## Proof

Before: six disposable document rows are deleted. The global page spinner/blur is visible. Metrics: `spinSamples=112/180`, `maxSpinning=2`, `maxBlurred=2`.
After: the same six-row delete flow completes without page-level blink. Metrics: `spinSamples=0/286`, `maxSpinning=0`, `maxBlurred=0`.

## Verification

- Passed: focused ESLint for `saga.js` and `saga.test.js`.
- Passed: focused Jest suite `src/redux/patient/saga.test.js`.
- Passed: browser video proof before and after using six disposable synthetic documents.

## Commit

- `619abfbcc` Avoid global spinner on HRC delete

## Notes

The evidence data was synthetic and disposable. The after recording includes deliberate human-readable pauses around each delete action.