v1.1: harden recovery and control boundaries

WP-D and WP-E complete the planned v1.1 implementation packages.

WP-D — recovery honesty:
- backups verify the completed copy with PRAGMA integrity_check
- corruption missed by quick_check is detected by the full check
- existing good backups remain protected
- oversized exports are still delivered but declare whether this version can
  import them, while the 20 MB import limit remains unchanged
- backup was exercised through the real browser UI on both the normal campaign
  database and a campaign-shaped database over 100 MB

WP-E — control-boundary contrast:
- interactive control boundaries meet the WCAG 1.4.11 3:1 target
- the contrast audit is now a failing gate rather than an advisory
- rendered browser measurements pass for the composer, controls, tabs and nav
- text contrast and focus visibility remain intact
- owner reviewed and approved the before/after screenshots

Reports:
- planning/reports/v1.1/V1.1-WP-D-REPORT.md
- planning/reports/v1.1/V1.1-WP-E-REPORT.md

All planned v1.1 work packages A-E are now complete. Release validation has not
yet begun.

planning/V1.1-PLAN.md

@@ -16,10 +16,16 @@ real-model limitation** (owner decision, 2026-09-15):
 
 The evidence is in `reports/v1.1/V1.1-WP-B2-REPORT.md` §S and §T.
 **WP-B.2** is committed and signed as `0c1ba83`. **WP-C**, browser release
-coverage, is complete and staged for owner review. Its final run passed 91 checks
+coverage, is committed and signed as `59b5ebc`. Its final run passed 91 checks
 (the 38 existing and 53 new) with 0 failed and 0 skipped, over trusted-LAN HTTPS,
-including real export downloads (`reports/v1.1/V1.1-WP-C-REPORT.md`). WP-D and WP-E
-have not started. No v1.1 version or tag exists.
+including real export downloads (`reports/v1.1/V1.1-WP-C-REPORT.md`).
+**WP-D** (recovery honesty) and **WP-E**
+(control-boundary contrast) are complete and staged for owner review, each with
+its own report: `V1.1-WP-D-REPORT.md` and `V1.1-WP-E-REPORT.md`. The final
+browser run covers all three suites — M11 38, WP-C 53, WP-E 10: **101 passed, 0
+failed, 0 skipped**. Every planned v1.1 work package (WP-A1, WP-A2, WP-B, WP-C,
+WP-D, WP-E) is now implemented and reported; release validation has not begun,
+and no v1.1 version or tag exists.
 
 This document replaces nothing. `BUILD-MILESTONES.md` stays as the closed v1
 history (M1-M11), and its *Post-v1 backlog* is this plan's input. The v1