docs(docs): R4 close: J1/J2 results as declared (real iPhone Safari iOS, missing details listed), RUST.md §10.15 residual risks and final checks, PDF_IMPORT_HARDENING.md §7, CHANGELOG headers, TODO R4.13, BDR-067
This commit is contained in:
1 parent
22bbfb4c8b
commit
3a7937e9fb
8 files changed
+174
-44
No files matched your search
@@ -165,3 +165,24 @@ only; a refused import leaves the tab's texts in place: app suites
|
||||
Owner reading at the R4.9 checkpoint: no item in this table is a code
|
||||
change pending in R4; items 3, 9 and 19 are the device runs (J1 and J2),
|
||||
items 12, 15 and 18 are the public-exposure gate, item 7 is measured and bounded (the browser's raster path), its device check is J2.6 / J2.7.
|
||||
|
||||
## 7. R4 close (2026-10-21, merged into develop)
|
||||
|
||||
The owner ran J1 and J2 on the OD-6 devices (computer with Chrome, Firefox
|
||||
and Brave; Android with its browser; a real iPhone with Safari iOS) and
|
||||
reports both recettes as passed with no blocking anomaly
|
||||
(`R4_J1_RESULTS.md`, `R4_J2_RESULTS.md`, `docs/development/RUST.md`
|
||||
§10.15). Effect on the §6 table, nothing else changed:
|
||||
|
||||
- Items 3 and 19 (the device runs) no longer block the merge: every device
|
||||
was run. Their per-check detail (J1.2, J1.10, J2.1 to J2.14 on each
|
||||
device) was declared as a whole, not individually.
|
||||
- Items 5, 6, 7, 9 and 20 stay **accepted temporarily**: what closes them
|
||||
is a measure or an observation on the phone (the J1.8 time and tab
|
||||
survival, the J1.9 and J1.10 memory behaviour, the J2.6 and J2.7 growth,
|
||||
the J1.12 timings behind the timer rule, the worker `error` event over
|
||||
repeated imports), and none was reported. They close when the owner
|
||||
reports those observations, or at the next device recette.
|
||||
- Items 12, 15 and 18 (**before public exposure**) are untouched: the
|
||||
import stays a local-tool feature behind the gate of §5, and the merge
|
||||
of R4 opens nothing to external users.
|
||||
Reference in new issue
Block a user