8.9 KiB
Verification
Latest checks — security verification, 10 November 2026
The initial working tree was clean. The checked-in baseline already contained staged replacement of build output, guarded preview URL parsing, strict settings validation, explicit module exports, process-code escaping and four security regression tests. This pass reviewed and verified those protections, made invalid review dates report the intended validation error, added direct bilingual rendering-injection and export-surface assertions, and corrected outdated publication/settings documentation. No project content, source-review dates, Docker/Nginx allowlists or rendering code changed. Generated content.js was regenerated by commands and remains byte-identical.
- Node v24.5.0;
npm test: all 14 tests passed. npm run build: passed. Regression tests confirm exactly five byte-identical public assets, removal of a nested synthetic stale file, rejection of redirected output, repository-relative operation from another working directory, and preservation of existing output when content validation fails.- Preview regression: malformed URL returns 400, subsequent valid request returns 200; source/private paths return 404 and all five public assets return 200. Loopback binding remains unchanged.
- Settings regressions cover structure, unsafe URLs, unexpected export keys, duplicate/injected codes, incomplete translations and invalid dates. Renderer regression deliberately bypasses validation and verifies escaped process codes in option attributes, option labels, summaries and dossier links in both languages.
node --check: passed for scripts/content.mjs, scripts/build.mjs, scripts/serve.mjs, tests/editor.test.mjs, tests/security.test.mjs, app.js and generated content.js.docker compose config --quiet: passed. Docker engine unavailable: Docker Desktop Linux engine named pipe missing; image build and runtime tests could not run.- Browser: home, work, all nine project routes, about and evidence checked in Dutch and English at 320px without document-width overflow. Evidence filter selected B1-K1-W4, rendered one open process and focused main; switching to Dutch preserved the filter. Keyboard activation of the skip link focused main and preserved the filter. No browser console errors recorded. Temporary viewport override reset afterward.
- Port 4173 was unavailable (EACCES); browser checks used an automatically assigned loopback port instead.
git diff --check: passed. Historical results below are retained.
Limits: print/PDF was not rendered again; no rendering or print implementation changed in this pass. Container runtime, reverse proxy and deployment remain unverified. No external evidence review, commit, push or deployment was performed.
Latest checks — documentation follow-up, 10 November 2026
Checked the documentation against the current compiler, renderers, tests and generated content. Confirmed nine projects, twenty-four source/evidence items and twelve mapped items. Updated contributor rules for repository overrides and context, clarified forge-specific evidence URLs and scaffold defaults, and separated historical eleven-project checks from the current nine-project selection.
- Repeated
npm test: all eight tests passed. - Repeated
npm run build: passed. - Local Markdown targets and
git diff --check: passed. - Browser, external repositories and Docker were not rechecked in this documentation-only follow-up. Earlier results below retain their original scope.
Earlier checks — selection adjustment, 10 November 2026
Removed Femcode and Tralalero at Alvin’s request, renumbered the LXC toolbox to 09 and updated bilingual biography copy and current project counts. Nine projects and twenty-four source/evidence items remain.
- Repeated
npm test: all eight tests passed. - Repeated
npm run build,node --check app.js,node --check content.jsandgit diff --check: passed. - Browser work archive checked in Dutch and English: nine project cards, neither removed project visible.
- Broader navigation, mobile and evidence checks below belong to the earlier expansion pass and were not repeated for this removal.
- No push or deployment performed.
Earlier checks — repository expansion, 10 November 2026
Added eight reviewed projects, bilingual context labels and per-project pinned GitHub/Gitea source links. See repository-review.md for scope, revisions, selection decisions and limitations.
- Node v24.5.0.
npm test: all eight tests passed, including forge-specific links and repository validation.npm run build: passed; generated content and exactly five public assets.node --check: app.js, content.js, scripts/content.mjs and both test files passed.- All 39 project and artifact paths verified through repository APIs at the selected commit IDs.
- Real browser: 15 routes (home, work, eleven projects, evidence, about) in Dutch and English at the default viewport and 320px; no document-width overflow or undefined output.
- Language switching preserved the selected project and focused the language control. Navigation focused main; keyboard activation of the skip link preserved the evidence route and focused main.
- Filtering B1-K1-W4 displayed the three existing testing sources. No browser console errors observed. Music Guessr inspected visually at default and mobile widths.
git diff --check: passed after correcting mixed line-ending whitespace in edited lines.- Build output inspected for the five allowed assets and byte equality with source.
Preview uses http://127.0.0.1:5178 because port 4173 returned EACCES. Print/PDF rendering was not repeated; print CSS and the set of mapped exam evidence are unchanged. Source applications, installers, live Proxmox scripts and their test suites were not executed. DOCX contents, personal authorship and assessment outcomes remain unverified. Docker configuration was unchanged, so Docker checks were not repeated. No commit, push or deployment was performed.
Earlier documentation checks — 10 November 2026
Documentation baseline reviewed against all tracked source, configuration, tests, JSON content, generated content and saved PNG references. No application behavior was changed in this pass.
| Check | Result |
|---|---|
| Node environment | v24.5.0; project requires >=22 |
node --check app.js and node --check content.js |
Passed |
npm test |
All six tests passed; regenerates content.js first |
npm run build |
Passed; generated module and five static assets |
docker compose config --quiet |
Passed |
| Local Markdown links | All relative targets resolve |
| Build output inspection | Exactly five assets, byte-identical to their source files |
git diff --check |
Passed |
| Docker engine availability | Unavailable: Docker Desktop Linux engine named pipe missing |
The six tests cover content translations/mappings, pinned source URL construction, explicit collaboration gaps, compiler consistency, empty collections, invalid input and homepage rendering after project removal. They do not verify remote artifact existence, a real browser DOM or visual layout.
The saved desktop and mobile PNGs were inspected as historical references, not recaptured. Browser interactions, responsive layout and print/PDF were not rerun in this documentation pass. Docker image build/runtime, reverse proxy and Proxmox deployment remain unverified. No external source documents or school-project tests were reviewed or executed again; the source review date remains 9 November 2026.
Historical record — 9 November 2026
The following is the previous verification record, retained for context. Its two-test count predates the current six-test suite; these results describe that earlier pass. See the latest checks above for the subsequently repeated browser and source-path checks.
node --check app.jspassed.npm test: both content integrity checks passed.npm run buildpassed; static output is indist/.- Local HTTP server returned 200.
- All 15 referenced project/artifact paths exist in the inspected school repository snapshot.
- Browser verified Dutch/English switching and preservation of the selected project.
- Evidence filter opened the software-testing process and displayed its three source links.
- Project navigation and keyboard skip link worked; skip retained the current route and focused the main region.
- All seven main routes were checked at 320px in both languages without document-width overflow.
- Homepage and project page inspected visually at mobile widths; homepage also inspected at 1440px. The English hero overflow found during inspection was fixed.
- No browser console errors were observed in the checked session.
- Preview saved in
docs/preview.png.
Limits: print/PDF layout has a dedicated stylesheet but was not rendered to a PDF in this pass. Docker deployment was not run. Linked DOCX contents were not reviewed. Source project tests were not executed. These checks validate the portfolio implementation, not the completeness or acceptance of exam evidence.