Files
faunosteo/docs/development/R4_MINI_RECETTE.md
T

47 lines
2.8 KiB
Markdown

# R4 mini-recette after R4.10 (J1.7 and its dependencies)
Re-runs only what R4.10 touched: the offline import (J1.7) and the import
path it shares with J1.1 and J1.13. Diagnosis: RUST.md §10.12. J2.3 waits
for the owner's decision on the branding of a re-export; nothing to run for
it until then.
## 1. Setup (computer, development machine)
1. Branch `feature/rust-r4-pdf-core` at its last commit; `pnpm build:preview`.
2. Open port 4173 for the session (ENVIRONMENTS.md §3):
`sudo ufw allow in on enp89s0 from 192.168.1.0/24 to any port 4173 proto tcp comment 'faunosteo recette R4'`
3. Serve: `. scripts/dev-env.sh && node scripts/browser/serve.mjs --host "$FAUNOSTEO_DEV_HOST" --port 4173`.
The server now sends the Cache-Control lines of `docker/nginx.conf`.
4. On the computer that runs the browsers, copy `faunosteo-j1-kit` to a
local folder (Documents or Desktop), not a network share.
5. In each browser, clear the site's data once (the old build's entries had
no Cache-Control line), then open `http://<DEV origin>:4173/`.
## 2. Checks
| Check | Steps | Expected |
|---|---|---|
| M1 file dialog offline, no Faunosteo page | cut the network the same way as at J1.7, open an empty tab, Ctrl+O | the browser's own « Ouvrir un fichier » dialog opens and closes normally |
| M2 J1.7 again | as written in `R4_J1.md` J1.7, the PDF picked from the local copy of step 4 | the editor opens with the bilan, the browser stays usable |
| M3 J1.7 with the browser's offline switch | network kept up for the system; DevTools, Network tab, « Offline » (Chrome, Brave) or « Travailler hors connexion » (Firefox); then the J1.7 steps | the editor opens |
| M4 J1.1 | one reference PDF online | the editor, the message of `ATTENDU.md` |
| M5 J1.13 | as written in `R4_J1.md` | both refusals, the bilan in progress kept |
| M6 J1.7 on the iPhone (when available) | as M2 on Safari iOS | the editor, or the line « Le moteur de lecture n'a pas pu être chargé. Réessayez l'import. » with the page still usable (the headless WebKit result) |
Browsers: Chrome and Firefox (OD-6), Brave as run on 2026-10-21; Android
with its browser for M2 and M4 when convenient.
How to read M1 and M2: if M1 hangs, the operating system's file dialog
hangs without the network whatever the page, a browser or system
limitation to note. If M1 opens but M2 hangs, the defect is Faunosteo's and
R4.10 continues. If M2 passes from the local copy but failed from the share
at J1, the kit's location caused it.
## 3. What to report
Per check and browser: PASS / FAIL / NON TESTÉ; the operating system of the
computer and the browser versions; how the network was cut (Wi-Fi off,
cable, airplane mode, DevTools); where the kit was read from at J1 and now.
Afterwards delete the UFW rule (`sudo ufw status numbered`, then
`sudo ufw delete <n>`).