Files
SluijsensandClaude Opus 5.5 b6d5a85e41 Applies the owner's Lighthouse targets
Three pages no longer need an exception and the homepage target rises to its
measured score, so the gain cannot slip away unnoticed. Also adds the third
unit's code summary and updates the shared docs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 20:07:24 +01:00

17 KiB

Verification log: hosting and targets (unit 3)

Source of the points: construction/hosting-and-targets/infrastructure-design/infrastructure-design.md § 12. Settled-in step: § 3.2 of the code generation plan.

Status values: OK, BLOCKED, DEVIATION, WITHDRAWN, OPEN.

V# Point Step Outcome Evidence Status
V1 The generated nginx file loads in a real nginx (nginx -t) as an http-level include without any other directive from the Pi; map before server works in conf.d. Every directive is checked against the nginx 1.30 documentation (the Pi runs 1.30.6; CI has 1.24) 3 (documentation), 6 (real nginx) OK on nginx 1.24.0: the generated file loads (nginx -t in the harness runs before every start) as an http-level include, map before server works; documentation part checked earlier (see below). Not proven: nginx 1.30.6 on the Pi (CI has 1.24.0); the real check is nginx -t plus the curl matrix during the Pi rollout (H2, H3). Checked against nginx.org docs on 2026-11-01: map (context http only; exact string beats regex, first regex in file order wins; ~* case-insensitive; no default gives empty), if/return/rewrite (server, location; rewrite permanent = 301, original args appended unless replacement ends in ?), try_files (server, location), error_page (http, server, location; without = keeps the status), internal (location), absolute_redirect (http, server, location; since 1.11.8, default on), autoindex (http, server, location; default off), gzip/gzip_vary/gzip_proxied/gzip_http_version/gzip_comp_level/gzip_min_length/gzip_types (http, server, location; text/html always compressed). The generated file puts map at http level (conf.d include) and all others in server or location. NOT documented by nginx.org: escaping of the rewrite replacement (BR-HST-06 relies on it; settled only by the real nginx test on //evil.example/ and /evil.example/); the safety of if with only return comes from the nginx wiki, not the page. CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06).
V2 Server-level if ... return 301 and rewrite ... permanent responses carry all five headers and Cache-Control with real nginx; absolute_redirect off gives a relative Location; / works without an index directive 6, 16 OK: 301 from the server-level if and from rewrite carry all five security headers, X-Robots-Tag and exactly one Cache-Control (raw header count); Location is relative (absolute_redirect off); / works without an index directive. Not proven: nginx 1.30.6 on the Pi (CI has 1.24.0); the real check is nginx -t plus the curl matrix during the Pi rollout (H2, H3). CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06). OK
V3 /soorten-fotoshoots (file) and /soorten-fotoshoots/ (directory) behave as in section 3.1 on nginx and preview; /assets and /assets/ as well 6, 8, 16 OK on nginx: /soorten-fotoshoots serves the file with the directory soorten-fotoshoots/ next to it, /soorten-fotoshoots/ gives one 301, /assets gives 404, /assets/ gives 301 to /assets. Preview-server side OK (config/previewServer.test.ts: resolver table and a server-level test with a page next to its directory; /assets 404, /assets/ 301 to /assets); real-nginx parity still open (Step 16). Not proven: nginx 1.30.6 on the Pi (CI has 1.24.0); the real check is nginx -t plus the curl matrix during the Pi rollout (H2, H3). CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06). OK (nginx part)
V4 /404 and /404.html give 404 with the page and the five headers on nginx; error_page keeps the status; HEAD works 6, 16 OK: /404 and /404.html give 404 with the page and all headers, a missing asset gives the 404 page with no-cache (not immutable), error_page keeps the status, HEAD works. Not proven: nginx 1.30.6 on the Pi (CI has 1.24.0); the real check is nginx -t plus the curl matrix during the Pi rollout (H2, H3). CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06). OK
V5 A HTTP/1.0 request with Accept-Encoding: gzip to the generated block gets Content-Encoding: gzip for .html, .js, .css, .svg, .json, .xml (all sizes above 256 bytes) and not for .woff2/images 6, 16 OK: HTTP/1.1 and raw HTTP/1.0 requests get gzip for html, js, css, svg, json, xml, txt in both mime variants, none for woff2 and png; Vary: Accept-Encoding present. Not proven: nginx 1.30.6 on the Pi (CI has 1.24.0); the real check is nginx -t plus the curl matrix during the Pi rollout (H2, H3). CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06). OK
V6 Withdrawn for this unit (IIS needs a host). The checks move to the "Before go-live" list, U1 to U6 WITHDRAWN (no host) WITHDRAWN
V7 previewServer.ts: the new resolveRequest contract (redirect result, query handling, --audit-route); unit 1 tests for BR-SRV-07 are updated (the "interim" rules become final); pageFiles.ts stays the single path to file mapping 7, 8 OK: resolveRequest returns FileResult or RedirectResult (301) and takes { auditRoute }; handle() sends the 301 with a relative Location plus the raw query, Content-Length: 0, the security headers and no Cache-Control, also for HEAD; /404 and /404.html are 404; /__audit/404 is 200 only with --audit-route; //x and /%5Cevil.example/ give the 404 page. The BR-SRV-07 tests are rewritten into the final rules. pageFiles.ts is still the only path-to-file mapping. pnpm exec vitest run config/previewServer.test.ts: 89 passed (two runs, seeds 943967193 and 1045251215); tsc --noEmit and eslint clean OK
V8 The 301 is followed by Chrome with the query string intact for ?pakket= and ?shoot= links, and the hydrated page has 1 title (extend the existing "URL die de server niet kent en de router wel" e2e) 17 OK in Chrome (urls.e2e.ts, hydration.e2e.ts): /Over-Mij, /Over-Mij?pakket=gezin, /over-mij/, /over-mij/?x=1, /soorten-fotoshoots/, /index.html and /over-mij.html each give exactly one 301 and then 200 on the canonical URL with the query kept; hydrated page has 1 title, the title of its own page, no robots tag, no console message or CSP violation. Unknown URL, /404 and /404.html: 404, 1 title, 1 noindex. Local run, pnpm build then pnpm e2e: 12 files passed, 248 tests passed, 204 skipped (nginx), seed 1174228318. The ?shoot= links are not in the list: the redirect keeps the raw query byte for byte (P-HST-05) OK
V9 One Lighthouse run of the 404 page on the preview audit route, and (as comparison) /404.html with ignoreStatusCode; record best-practices for both, then keep the simpler passing option (O2) 22, 23 (measurement-final.md) OK: the audit route is kept (owner choice O2). In the final measurement (3 runs, mobile and desktop) the not-found page through /__audit/404 has no runtime error, best practices 1, accessibility 1 in every run; mobile median performance 0.97, desktop 1.00. The comparison with /404.html and ignoreStatusCode was not run: /404.html is a real 404 now and the audit route passes. SEO 0.58 is the deliberately failing is-crawlable audit. measurement-final.md (Accessibility, best practices, SEO; V9 line), commit 6d4d012 OK
V10 lftp: dry run against a file: target proves that pass 1 skips all nested *.html and web.config, pass 2 uploads them, pass 3 deletes only stale files 14 Proven against a local file: target with real lftp 4.9.2 (CI run 594, commit 38708b8, Ubuntu noble arm64): the per-pass tests passed, so pass 1 (--exclude-glob '*.html' --exclude-glob web.config) copies no HTML (nested included) and no web.config; pass 2 (put -O plus --include-glob '*.html' alone) copies all HTML including the nested page and 404.html, so --include-glob alone includes only HTML and does descend into subdirectories; pass 3 deletes only the stale file; the final tree equals dist plus web.config; LFTP_OPEN=file:/// with an absolute remote dir works. This proves lftp's pattern syntax against a file: target, NOT FTPS against a real host (ssl settings, login, and the host's directory layout are untested). One test failed in that run: it looked for assets/a.js and .html in lftp's verbose output and found no .html line (index of first HTML -1), so lftp's output format is not what that test assumed; the order is now proven by the script itself: one lftp session per round with == Ronde N markers and set -e, plus the per-pass trees. That change (separate sessions, markers) has not yet run in CI. CI run 594 log (25 of 26 deployScripts tests passed); e2e/deployScripts.e2e.ts OK (file: target); FTPS unverified
V11 verify-deployment.sh fails against a copy of the old nginx config (home page for /over-mij) and passes against the new one 13 OK against stubs: verify-deployment.sh exits 1 against a stub that imitates the old nginx config (index.html with 200 for every path), with the messages "/over-mij: antwoord is niet gelijk aan over-mij.html", "status 200, verwacht 404" and "/over-mij/: status 200, verwacht 301"; it exits 0 against a stub with the new rules (also with a trailing slash on the URL) and against the preview server on the fixture site. Also fails per missing security header, with --test without X-Robots-Tag or gzip; gzip missing only warns without --test. Not run against the real old or new nginx file on the Pi (nothing is contacted); the first deploy-test run shows it against the new config. pnpm exec vitest run --config vitest.e2e.config.ts e2e/deployScripts.e2e.ts: 22 passed, 5 skipped (lftp) OK (stubs)
V12 CI: the lighthouse job (or a new server-rules job) installs nginx, pnpm e2e includes serverRules.e2e.ts, and the job fails if nginx is missing 5, 16 OK: the lighthouse job installs nginx and lftp, Browsertests runs with CI=true, serverRules ran with nginx present. The missing-nginx failure path was proven locally (CI=true without nginx fails with "nginx ontbreekt in CI (BR-HST-24)"). CI run 593 (commit 8cb9185), job lighthouse, step Browsertests, nginx/1.24.0 (Ubuntu) on the Pi runner (container, root); e2e/serverRules.e2e.ts: 134 tests, all passed, none skipped (2088 ms), 67 per mime variant (.js as text/javascript and as application/javascript); the run totals 348 tests with 341 passed and 7 failed, all 7 in images.e2e.ts and reveal.e2e.ts (timeouts, unrelated); the test prints "[serverRules] nginx -v: nginx version: nginx/1.24.0 (Ubuntu)" once per variant. Earlier cycles found and fixed three defects through this proof: workers as www-data could not read the mkdtemp fixture (harness, run 592: 403), map plain keys ignore case so /Over-Mij was not redirected (generator), and /%5Cevil.example/ produced Location /evil.example (generator, BR-HST-06). The install step in run 593 uses policy-rc.d to keep the package from starting a service. OK
V13 lighthouserc.cjs: the exception table is empty on delivery unless an owner decision exists; P-HST-11 passes; pnpm lighthouse still starts the preview with --audit-route and Local appears for startServerReadyPattern 11, 12, 26 OK. On delivery (Step 11) the table held the 8 carried-over entries with a provisional decision text; the owner decided per page on 2026-11-01 after the final measurement and the table now holds 5 entries, each with the owner's decision text (see code-summary.md, NFR-PR-P-01). Effective targets mobile: / 0.85; zwangerschap, gezin, loveshoot, portret 0.85; all other URLs 0.9; desktop 0.9 everywhere. config/lighthouserc.test.ts and src/app.test.tsx: 55 tests green; lhci assert on the unit's final measurement (36 runs per preset): all 12 URLs pass, mobile and desktop. The start command has --audit-route, numberOfRuns is 1. Earlier evidence (Step 12): pnpm exec lhci collect --url=http://localhost:4173/__audit/404 --numberOfRuns=1 started pnpm preview --port 4173 --strictPort --audit-route, the Local line was seen, Lighthouse audited the page with status 200 and no run warning. OK
V14 The generated header comment fits the Pi: install path /etc/nginx/conf.d/andreaslop-test.conf (included from nginx.conf:38), no sites-enabled, no global nginx.conf change; the file works for a first install and for an update of an existing file 3 Header comment rewritten: install path /etc/nginx/conf.d/andreaslop-test.conf, included in http {} from nginx.conf, no sites-enabled, no global nginx.conf change, own gzip block because the Pi has none, works behind an HTTP/1.0 proxy, 444 from 00-default.conf for an unknown host (old WordPress remark removed), server_name and root adaptable, no default_server. The same file serves a first install and an update (it replaces the existing file in place). Generated deploy/nginx/andreaslop-test.conf (lines 1-12); equals nginxTestConf() (serverConfig.test.ts sync test green) Fit check against pi-install-instructions.md (final conf, 2026-11-01): (1) backup lives outside conf.d, no .bak in documents or generated comments: OK. (2) install path, root /var/www/html/andreaslop-test = DEPLOY_PATH_TEST, header mentions 00-default.conf and 444: OK. (3) every location repeats the full set of seven headers, /assets/ has one Cache-Control, no etag directive, /robots.txt is a test-only location, no map rule matches /404 or /404.html: OK. (4) proxy checks are the owner's, nothing in the code depends on them: OK. Expected results of the instructions hold in the conf by reading. Not run against a real nginx here. OK