feat(ui): migrate reminders and protect follow-up recovery
This commit is contained in:
@@ -146,3 +146,11 @@ Public18 top-document all-enabled scans0/12 retain sandbox frame-tested occurren
|
||||
### P7-05 Offers evidence
|
||||
|
||||
[Offers results](p7-05/evidence/offers-results.json) correct unsupported deadline-sort intent with explicit existing effectiveorder, unlabelled first25 sample, misleading decision-deadline wording, host-number locale and locale-triggered refetch/fallback/recovery focus. Original numeric/free-text/currency contract retained; no server data meaning change. Fourteenall-enabled scans0/15 retain contextual contrast incompletes; human/device/zoom/output/production obligations remain. No whole PRES or inherited scaling/calendar/provider debt closes.
|
||||
|
||||
### P7-06 confirmed compose safety entry dependency
|
||||
|
||||
Read-only connected-code inspection confirms existing CorrespondenceInboxPage updateDraft implicitly rotates UUID/clears every delivery result, allowing edits to erase uncertain/pending/sending/sent/failed safeguards. A held draft Save can merge into later work; Save and Send can race while new persistence assigns a server UUID. Recipient-only/subject-only dirty checks are incomplete. Runtime RED remains required; these are confirmed code paths, not passing evidence or a completed repair. Before P7-06 compose presentation acceptance, serialize captured-identity mutations/confirmations and preserve explicit definitive-failure new-attempt/revision/owner/idempotency contracts, with meaningful unit/native failure recovery. No real mail/provider execution or backend/schema change is authorized by this finding. Keep approved embedded-forms then inbox/read then compose/send commit sequence; independently push the coherent safety repair at that boundary.
|
||||
|
||||
### P7-05 Reminders finite evidence
|
||||
|
||||
[Reminders results](p7-05/evidence/reminders-results.json) repair reproduced duplicateheldPATCHs, toast-only local failure, host-locale dates, localeGET and managedfocus/reflow in the existing owner. Old GET-only retry/movedfocus behaviors already passed RED and remain. Explicit captured write Retry does not prove network-uncertain event deduplication; lastwriter/date/DST obligations remain. Clear shows existing Shellpoll lag; generated English reasons inNB go toP7-11, customfallback staysraw. New17all-enabledscans0/114 retain full contrast/heading-context requirements; no human/device/output/wholePRES debt closes.
|
||||
|
||||
Reference in New Issue
Block a user