docs(docs): R4.10 owner decisions: J2.3 option 1 (expected result corrected), J1.7 rectified as PASS with a picker-delay reserve, R4.8 deletion trace (23 files), RUST.md §10.12 ZenQuality logo diagnosis, CHANGELOG, contract, TODO

This commit is contained in:
bchanot committed 2026-10-21 15:47:19 +02:00
1 parent dcc79400de
commit c619f3eba2
9 files changed
+156 -21

No files matched your search

+58 -4
View File
@@ -2226,10 +2226,15 @@ core alone no longer compiled with no feature (`facade::restore_copy` used
the feature-gated reader's cap; the workspace run unified the wasm crate's
features and hid it from `rust:check` and `check:all`): fixed, and
`rust:check` now lints the core alone; pass 2 found the §6 register without
the J2 merge-gate row: added; pass 3 CONFORME 16/16. The floor lists the 21
test files R4.8 deleted (approved in the owner's brief, every case in the
ledger with a present target): they clear formally only with the owner's
own `[gated]` line. Security, fresh: pass 1 BLOCK(1) on the R4.1
the J2 merge-gate row: added; pass 3 CONFORME 16/16. The floor lists the
test files R4.8 deleted (23 by `git log --diff-filter=D` on 0dc1ba2, the
one deleting commit of the branch; the verifier counted 21): approved in
the owner's brief, 22 traced case by case in the ledger with a present
target, the glue's `pdf-export.ts-engine.test.ts` traced in §10.10; the
owner's written approval is the R4.9 contract's header (2026-10-20) and
BDR-064. The floor clears formally only with the owner's own `[gated]`
line; the owner asked (2026-10-21) for the trace to be verified, not for
a marker. Security, fresh: pass 1 BLOCK(1) on the R4.1
`.gitleaks.toml` path allowlist, which carries no owner `[gated]` marker
(the owner approved it on 2026-10-18; only the owner adds the marker), and
a MEDIUM, the recette server bound every interface on an empty `--host`;
@@ -2282,6 +2287,17 @@ 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).
Settled by the owner (2026-10-21, mini-recette M1 and M2 on Firefox and
Brave, the kit stored locally): with the system's network cut, the file
dialog takes about one minute to open, from Ctrl+O in an empty tab as from
the Faunosteo button alike, and the offline import then works. The
symptom exists outside Faunosteo, so no proof of an application defect
remains; J1.7 is a functional PASS with a performance reserve on the
picker's opening. The cause of the minute is not established (the share
hypothesis is not confirmed; nothing was measured or traced) and no
application change follows without proof of a Faunosteo defect. The
recette server's cache fix stays: a demonstrated defect on its own.
**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
@@ -2300,3 +2316,41 @@ result of J2.3 written at R4.6 was wrong: it described the oracle's
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).
Owner decision (2026-10-21): option 1. A new export from the editor is a
new document with the application's current branding; the archive keeps
its own branding for a faithful reproduction by the tool
(`export_from_envelope`). Only the expected result of J2.3 and the recette
documents changed; the owner's observed result is acceptable under the
corrected rule, subject to the logos shown being the current branding.
**C. The footer's ZenQuality logo under the production CSP (2026-10-21,
owner's ask).** `Footer.tsx` loaded « Propulsé par » from
`https://zenquality.fr/assets/logo-horizontal-1024.png` since the footer
exists (caac149, 2026-05-21), and DEPLOY.md's CSP, `img-src 'self' data:
blob:`, dates from the same day (98117b3). Impact: on an origin that sends
that policy, the image is refused and its slot shows the alt text
« ZenQuality » (or the browser's broken-image mark); the link itself still
works, nothing else on the page depends on it. The exported PDF is not
affected: `pdf/branding.ts` embeds the bundled `zenquality-logo-fr.png`,
never a fetched file. Where the policy lives: the VPS reverse proxy
(DEPLOY.md, nginx Option A or Caddy), not `docker/nginx.conf`, which sets
no CSP; `faunosteo.com` answered with no `Content-Security-Policy` header
on 2026-10-21 (HEAD request), so the live site does not refuse it today.
Why the recettes did not report it: the J1 / J2 checklists carry no
footer item, and the development server (`pnpm dev`) sets no policy; the
headless CSP proofs did see it, on every page since the R2 app-image proof
(§8) and in `r4-app-csp.mjs` (§10.3), recorded as "the one known
violation" and excluded from their verdict. Fix (R4.10j): the same file
bundled under `src/assets/brand/zenquality-logo-horizontal.png` (1024 ×
237, the bytes fetched from zenquality.fr on 2026-10-21, sha256
`8625f6b1…`) and imported with `?url` like the partner's drawing, so the
pixels do not change and the CSP stays as documented; the hotlink no longer
sends the visitor's address to a third party either.
`components.Footer` pins it (every footer image served by the application;
the test fails on the hotlinked version); `r4-app-csp.mjs` drops its
known-host exception, any violation is now a problem: 12 passes, no
violation, no report (`results/2026-10-21-r4-csp.json`);
`r4-offline-import.mjs` 6 runs as expected on the same build
(`results/2026-10-21-r4-offline-import.json`). The two `?inline` PDF logos
and the `fr` variant are untouched: the footer shows the file it always
showed.