docs(redesign): record Rules draft repair acceptance

docs/redesign/phase-5/p5-15/READINESS_DEBT.md

@@ -31,7 +31,7 @@ Owners below are responsible roles, not invented assignees. Each next checkpoint
 | **RD10 production Linux/fonts/photos/print/other browsers — UNVERIFIED.** Local 16/16 standard (36=36 pages) and 8/8 settings (24=24) unchanged fidelity are finite. Photo/wrapped-line/template/font/native-print qualification remains open. | **B** for full affected CV acceptance; **A** for release environment font/data smoke | CV/rendering + release reviewer; isolated production-equivalent render checkpoint | Effective Linux/browser/fonts/image revisions; native preview/private/public PDF/photo/non-ASCII/long-line/template checks at unchanged tolerances and manual readability/print; supported alternate-browser/device evidence. Do not infer missing production fonts from local success or alter tolerances. |
 | **RD11 P5-06-O01 language preference 500 — OPEN, root cause unproven.** Actual PUT `/api/auth/preferences/language` uses `UserManager.UpdateAsync`; source caller applies UI/localStorage first and swallows failed PUT. This can silently leave server preference stale; concurrent Dashboard reads accompany the historical 500, not a proved root cause. | **B** for reliable affected Settings/locale acceptance; **A** if reproduced on intended production provider/workflow; **D** only for independent presentation scope | Backend/identity + i18n owner; scoped reliability investigation before locale persistence acceptance | Reproduce overlapping native path on disposable intended provider with sanitized exception/status/correlation and before/after preference; verify failure feedback and recovery, successful readback/relogin, account isolation and regression. Fixture sequencing/204 on later saves does not close original 500 or swallowed failure. |
 | **RD12 P4-04-O02 notification-setting contention — OPEN.** Native PUT `/api/notification-settings` through `UserManager.UpdateAsync` produced SQLite error 5/DB locked in **2/10**; readback retained old value. Settings currently retains draft and in-page error; sequential success is not a contention fix. | **B** for complete affected settings reliability; **A** if intended deployed provider reproduces; **D** for unchanged independent UI | Backend/identity owner; scoped concurrent API reproduction before more polling/writes | Trace exact locking/transaction/provider cause and bounded fix, concurrent success/failure/draft/retry/readback evidence on real disposable DB. Never treat GET 200 as PUT success or hide a 500 with generic retries. |
-| **RD13 P2-O01 rules-save 500 — historical unconfirmed, still OPEN.** Rules GET can create per-user settings; PUT gets/creates then `SaveChangesAsync`. Creation-race catch/reload exists, but does not prove the historical failure cause. Save error is currently transient toast; draft remains. | **D** conditional reliability; **B** if recurrence/failure feedback prevents affected flow acceptance; **A** if deployed critical persistence fails | Backend/rules + Settings owner; scoped triage if recurring and M07 error acceptance | Retain trace/status/exception and native before/after rule values; investigate actual concurrent/create/save path. Prove accessible actionable error and deliberate successful recovery; do not equate this unproven cause with notification locking. |
+| **RD13 P2-O01 rules-save 500 — historical unconfirmed, still OPEN.** Rules GET can create per-user settings; PUT gets/creates then `SaveChangesAsync`. Creation-race catch/reload exists, but does not prove the historical failure cause. R-02 provides persistent in-page save feedback, explicit retry/discard and internal draft retention; the historical server500 cause remains unknown/open. | **D** conditional reliability; **B** if recurrence/failure feedback prevents affected flow acceptance; **A** if deployed critical persistence fails | Backend/rules + Settings owner; scoped triage if recurring and M07 error acceptance | Retain trace/status/exception and native before/after rule values; investigate actual concurrent/create/save path. Prove accessible actionable error and deliberate successful recovery; do not equate this unproven cause with notification locking. |
 | **RD14 command/dialog focus observations P5-04b-R01/P5-07-O01 — OPEN.** Command focus gained/lost around entry; attachment Shift+Tab failed while existing `onEntered` refocused Cancel. Unchanged focused reruns passed; transition race is not instrumented/proven. | **B** affected shared focus acceptance | Shared dialog/shell owner; targeted instrumented investigation plus M02/M05/M09 | Preserve failed observations; reproduce/instrument entry/exit focus ownership, keyboard trap and return under normal/reduced motion and AT, then bounded fix/retest if warranted. Rerun alone does not close it. |
 | **RD15 P5-04b-R02 CV section expansion — cause unproven.** One unchanged full-run smoke failed before PDF; three unchanged focused runs passed. | **D** baseline investigation; **B** if recurring affected CV preservation failure | CV readiness owner; targeted expansion reproduction before broader CV acceptance | Actual event/focus/expanded-state trace and retained assertion, diagnosis or bounded reproduction-backed disposition. Keep original failure; do not mark fixed from later broad pass. |
 | **RD16 P4-02-D02 company error outside modal — OPEN.** Failed save retains draft, but transient toast is outside modal's accessible subtree. P5-00 bottom feedback placement does not repair this. | **B** for full affected dialog acceptance; **D** for unrelated local P5 slices | Company form/Phase 7 owner; M07/M09 targeted accessibility checkpoint | Durable visible/spoken in-modal failure, retained draft, retry/recovery and focus/return evidence without disabling background isolation. No universal dialog pass while this counterexample remains. |