docs(docs): R4.10 owner results as declared (J1.7 FAIL Firefox + Brave, J2.3 FAIL), RUST.md §10.12 diagnosis of both anomalies, mini-recette, TODO R4.10

This commit is contained in:
bchanot committed 2026-10-21 00:26:06 +02:00
1 parent 63034e10c4
commit 868aa3d001
5 files changed
+166 -34

No files matched your search

+60
View File
@@ -2240,3 +2240,63 @@ at most the 50 MiB cap after checking the file's type. Last re-gate PASS,
LOW residuals only (a local writer swapping a FIFO in between the CLI's
stat and open can make it wait). Final `pnpm check:all` green on 49b812b
(2 min 51 s).
### 10.12 R4.10: the J1 / J2 anomalies (2026-10-21, `scripts/browser/results/2026-10-20-r4-offline-import.json`)
The owner's run (computer: Chrome, Firefox, Brave; Android; Safari iOS not
run) reported two failures. Results as declared: `R4_J1_RESULTS.md`,
`R4_J2_RESULTS.md`.
**A. J1.7, offline import (FAIL on Brave and Firefox, surface 2).**
Reproduced headless on the same build and server (reference PDF imported
online, editor loaded, network cut, « Accueil », « Choisir un fichier »,
« Remplacer », same PDF), two ways to cut: Playwright's offline mode and
the server process killed.
| Engine | Before (serve.mjs without cache lines) | After (nginx.conf lines) |
|---|---|---|
| Chromium | the worker chunk refused from the cache (`net::ERR_ABORTED`), inline line « Le moteur de lecture n'a pas pu être chargé. » | editor, both cuts |
| Firefox | editor (offline mode serves the stale entry) | editor, both cuts |
| WebKit | inline line | inline line, both cuts |
Cause found: `scripts/browser/serve.mjs` sent no `Cache-Control` and no
validator on `/assets/`, where `docker/nginx.conf` sends `public,
max-age=31536000, immutable`; without it a browser may not reuse the
prefetched worker chunk offline. A recette surface defect, not an
application one: production already sends the line. Fixed: the server
sends the two nginx lines (`env.js` no-store, `/assets/` immutable);
`scripts/browser/r4-offline-import.mjs` re-runs the path on the three
engines and both cuts and checks the headers (6 runs as expected; with the
old server, Chromium fails both: exit 1). Headless WebKit never takes a
worker script from the HTTP cache offline, even immutable: the page shows
the inline line, stays usable, no data changes. Whether Safari iOS does the
same is not known: J1.7 on the iPhone tells.
Not reproduced: the file picker that does not open and the browser that
becomes unusable. In every headless run the page answers (picker event,
editor or inline line, no page error). The picker is the
operating system's dialog, which a headless browser replaces; the page's
click handler calls `input.click()` synchronously, before any network
call. A dialog that hangs when the network goes is consistent with a file
dialog opening on a network folder (the kit read from a share) but nothing
proves it yet: the mini-recette's discriminating step settles it (Ctrl+O
offline in an empty tab, the kit copied to a local folder).
**B. J2.3, export without logos (FAIL).** The reference file
`1-reference/r3-demo.fr.nologos.pdf` carries an archive whose branding has
the four logo slots `null` (the R3 oracle's `nologos` mode: the logo fetch
answered 404, `STEP6_PDF_ARCHIVE_ANALYSIS.md` §17). The editor export builds its branding from
`apps/app/src/pdf/branding.ts` (`loadBranding()`, the four bundled logos)
on every export; the imported archive's branding is kept in the session
(`osteo:archive`) but never handed to the writer. Same rule before R4:
`apps/app/src/pdf/export.ts` at 66909b6 already passed `loadBranding()` to
the TypeScript engine. The archived branding is used only by
`export_from_envelope` (cargo, the oracles), never by the application. The
writer draws the text fallback only for a `null` slot or a logo that
failed to embed, which the application's bundled branding never has since the logos are bundled (Step 6,
fetch removed). So the application behaves as specified, and the expected
result of J2.3 written at R4.6 was wrong: it described the oracle's
`nologos` file, not an editor export. Nothing changed (goldens, oracles,
rules and the expected result untouched); an owner decision is needed:
keep the rule and correct the expected result of J2.3, or make a re-export
of an imported bilan reuse the archived branding (a product change).