docs(docs): J1: iPhone deferred by the owner, stays not tested; computer run reported without failure

This commit is contained in:
bchanot committed 2026-10-18 21:22:06 +02:00
1 parent 769544a1e8
commit 73706c074e
3 files changed
+14 -10

No files matched your search

+1
View File
@@ -288,3 +288,4 @@ Owner validated R4.0 plan with conditions (BDR-057, plan §A.6, LRN-059/060). R3
- 2026-10-18 owner validated R4.2 (BDR-058): thresholds 400,000 / 1 GiB final; R4.3 go on feature branch; app import switch gated on the 20–50 MiB file memory fix (WebKit 324 vs 76 MiB) re-measured on 3 engines, and leak series (init apart, ≥ 5 imports, ≤ 10 MiB recurring). LRN-061, LRN-062 written. Next: R4.3a bytes API + streaming read, worker protocol, HomeRoute, CSP proof, series measurements.
- 2026-10-18 R4.3 done on feature/rust-r4-pdf-core (52471db..b08373a): FileBytes sink + import_pdf_bytes/restore_copy_bytes; worker protocol v1 (task/chunk/ack/end → ready/result/failed), page reads file in 1 MiB BYOB chunks (amendment B.1.5: WebKit worker file read ≈180 MiB), client timers + settle-once + terminate, controller, HomeRoute switched, B.1.8 messages pinned on O8/O7/O2/O3 via in-process worker, 6 suites migrated (458 app tests). Security gates: reader PASS after fix, worker PASS 7 LOW → hardenings 8ddf185. Browser proofs on dist: 666/678, W5 0 long tasks, CSP with/without OK; 50 MiB WebKit 145 vs TS 76 (was 324); leak series Chromium OK, Firefox sawtooth reclaimed, WebKit grows with same-tab navigation (control too). DEPLOY note, R4_J1.md + kit script. Open for owner: WebKit large-file gate, WebKit leak criterion. Next: owner decision, J1 on devices.
- 2026-10-18 owner: J1 authorised with both WebKit reserves (BDR-059), cap 50 MiB kept, no streaming scanner, criterion 10 MiB / 5 imports kept with same-page vs navigation split + control. Kit generated (../faunosteo-j1-kit, 13 MB, L report as rescue copy for the 42 MB export), R4_J1_RESULTS.md template. STOP: waiting for device results; no merge, no R4.4.
- 2026-10-18 J1 partial: owner ran the functional checks on a computer, no failure (browser/version, timings pending); iPhone not available, deferred → stays NON TESTÉ, blocks final R4.3 acceptance (OD-6). Proposed: continue R4.4 on the branch with the iPhone J1 as a blocking item before any merge; waiting for the owner's decision. No merge, no R4.4 started.
+7 -5
View File
@@ -5,16 +5,18 @@ Procedure: `R4_J1.md`. One column per device actually run; `PASS`, `FAIL` or
timing and memory event. A device or browser not run stays `NON TESTÉ`.
Status 2026-10-18: the owner reports the functional checks they executed as
passed, with no failure. Which devices, browsers and versions ran, which of
the twelve checks each one covered, the J1.8 / J1.12 timings and the J1.9 /
J1.10 memory observations have not been given yet: every cell below stays
`NON TESTÉ` until the owner confirms it, nothing is inferred.
passed, with no failure, on a computer (browser and version to be given).
iPhone / Safari iOS: not run, deferred by the owner to a later date; it
stays `NON TESTÉ` and blocks the final acceptance of R4.3 (plan §A.4, OD-6:
a device not run is never reported validated). The J1.8 / J1.12 timings and
the J1.9 / J1.10 memory observations on the computer are pending too; every
cell below stays `NON TESTÉ` until the owner confirms it, nothing is inferred.
| Device, browser, version | Surface (1 dev / 2 prod CSP) | Date |
|---|---|---|
| (to be confirmed by the owner) | | 2026-10-18 |
| Check | Device A | Device B | Device C |
| Check | Computer (browser, version?) | iPhone, Safari iOS (deferred) | Android (not run) |
|---|---|---|---|
| J1.1 reference PDFs open the editor | NON TESTÉ | NON TESTÉ | NON TESTÉ |
| J1.2 hostile folder: message per file | NON TESTÉ | NON TESTÉ | NON TESTÉ |
+6 -5
View File
@@ -1403,11 +1403,12 @@ not reproduce).
J1 device run (2026-10-18, `R4_J1.md`, owner decisions BDR-059: both
WebKit reserves accepted provisionally, PDF cap kept at 50 MiB): the owner
reports the functional checks they executed as passed, no failure. The
device list, versions, the checks covered per device, the timings (J1.8,
J1.12) and the memory observations (J1.9, J1.10) are recorded in
`R4_J1_RESULTS.md` as the owner confirms them; until then they are not
claimed here. Headless engines never stand for Safari or a phone.
reports the functional checks they executed on a computer as passed, no
failure; iPhone / Safari iOS could not be run and is deferred, so it stays
not tested and the final acceptance of R4.3 waits for it (OD-6). The
browser and version, the checks covered, the timings (J1.8, J1.12) and the
memory observations (J1.9, J1.10) are recorded in `R4_J1_RESULTS.md` as the
owner confirms them. Headless engines never stand for Safari or a phone.
Residual risks and open points (R4.3, for the J1 checkpoint):