diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..2029433 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,27 @@ +# Contributor instructions + +## Project baseline + +Read `README.md` and `docs/codebase-index.md` before editing. This is a static, bilingual portfolio using native ES modules, CSS and JSON, with no npm dependencies. Use Node 22 or newer and run commands from the repository root. + +## Source ownership + +- Edit projects in `content/projects/*.json` and shared settings in `content/settings.json`. Follow `docs/content-editing.md`. +- Generate `content.js` with `npm run content`, `npm test` or `npm run build`. Commit generated changes alongside their source; never hand-edit the module. +- Keep Dutch and English text complete, project IDs stable, and repository links pinned to a reviewed revision. +- Preserve explicit evidence gaps. Do not invent personal contributions, assessment results, test outcomes or deployment claims. Only change the source review date after actually reviewing the sources. +- UI copy and shared contribution/reflection placeholders also live in `app.js`; metadata lives in `index.html`. JSON is not a complete CMS. +- Keep the static publication boundary: five public assets, no public editor or write API. If assets change, update the build, preview allowlist, Docker inputs and Nginx allowlist together. +- Do not commit `.env`, `dist/`, logs, dependencies or private material. The build does not clean `dist/`, so inspect it before publishing. + +## Checks and documentation + +Run `npm test`, `npm run build` and `git diff --check` before committing. Use `node --check` for edited JavaScript files. For Docker changes, validate `docker compose config --quiet`; build and test the container when an engine is available. Report unavailable checks explicitly. + +For rendering changes, check both languages, navigation, all project routes, evidence filtering, keyboard focus, mobile overflow and printing when affected. Existing unit tests use a minimal DOM stub and do not replace browser checks. + +Keep README, content reference, codebase index and hosting instructions aligned with changes. Record actual checks and their date in `docs/verification.md`; distinguish historical results from checks repeated now. Existing PNG previews are historical references, not proof of current behavior. + +## Git and deployment + +Inspect the working tree and preserve unrelated user changes. Review the diff and stage intended paths explicitly. Fetch before pushing; rebase unpublished commits only if needed and rerun affected checks after conflicts. Do not force-push shared history. Push when requested by the user; deployment is a separate operation and must not be reported as completed merely because a push succeeds. diff --git a/README.md b/README.md index dac491a..0c3155e 100644 --- a/README.md +++ b/README.md @@ -1,68 +1,78 @@ -# Alvin Zilverstand — portfolio - -A custom, bilingual static portfolio for VISTA college Heerlen. Dark project journal with project dossiers, repository links and a provisional SBB evidence index. No external fonts, tracking, framework, CMS, runtime API requests or production Node service. - -## Run locally - -Requires Node 22 or newer. No dependency installation is necessary. - -```sh -npm run dev -``` - -Open http://127.0.0.1:4173. Set `PORT` to change the port. The development server binds to loopback only. - -```sh -npm test -npm run build -``` - -The build copies the five website files into `dist/`. It can be hosted at a domain root or a subdirectory. Hash-based routes mean no server fallback configuration is needed. Dutch is the default; `?lang=en#evidence` opens English evidence navigation. Language switching preserves the current page. - -## Maintain content - -See [the codebase index](docs/codebase-index.md) for the file map and rendering dependencies. - -Content editing stays on your computer. There is no public admin page or write API. - -- **Add a project:** run `npm run project:add -- my-project`. Open the new `content/projects/my-project.json` and replace the placeholder text. -- **Edit a project:** open its file in `content/projects/`. Text pairs are `[Dutch, English]`. Change `number` to change the display order; the first project is featured on the homepage. -- **Delete a project:** delete its JSON file. Its project card and evidence-index entries disappear on the next preview refresh or build. -- **Add/edit/delete an item:** edit the project's `evidence` array. Copy an existing entry to add one, change its values to edit it, or remove the entry to delete it. An empty array `[]` is allowed. -- **Profile and processes:** edit `content/settings.json`. - -An evidence item looks like this: - -```json -{ - "label": ["Testverslag", "Test report"], - "path": "projects/my-project/tests.md", - "type": "MD", - "codes": ["B1-K1-W4"] -} -``` - -Use `"directory": true` for a folder. Paths are relative to the school repository. Keep project `id` values stable to preserve links. Use exactly three `nodes` for the system diagram. Project numbers and challenge numbers are strings. - -Run `npm run dev` and refresh the browser to preview saved edits. Invalid content will prevent the preview content module from loading; run `npm run content` for a descriptive validation error. Run `npm run build` to validate and prepare publication. `content.js` is generated; do not edit it directly. `npm run content` regenerates it without building. - -Only deploy `dist/`. Everything in the generated content is public, so keep credentials and private documents out of these files. Repository links remain pinned to the `revision` in `content/settings.json`; update it after reviewing a newer snapshot. - -## Finish the exam content - -The interface is functional; the exam dossier is not yet complete. Summaries are based on the supplied school repository, not invented personal experience. Artifact paths were checked against the repository tree. DOCX contents were not reviewed and the source projects' test scripts were not executed. - -Before submission, add your personal contribution and reflection for every case study, confirm solo/team context, include actual test results, and substantiate improvement claims. Add evidence for B1-K2-W1, W2 and W3 (collaboration, presentation and evaluation). The current mappings are suggestions, not assessment decisions. Ask the examiner which artifacts and authenticity statements VISTA requires. General subjects, electives and institution-specific requirements are outside this vocational index. - -The source is SBB's 2024 qualification for Software Developer, code 25998: -https://kwalificatie-mijn.s-bb.nl/Details/DownloadDocument/1963420 - -English process names are informal translations. Reviewed 9 November 2026. - -Direct contact details, a CV, screenshots, assessed outcomes and personal reflections were not supplied, so the site does not invent them. Add these as real material becomes available. Project diagrams illustrate structure; they are not screenshots of running applications. - -## Host on Proxmox with Docker - -See [Docker hosting instructions](docs/docker-hosting.md) for installation, network access, reverse proxies and content updates. - -Run `docker compose up -d --build` from the repository on your Docker guest. Docker builds from the JSON source files; no manual build or Node installation is needed on the guest. The default binding is localhost only. Configure `.env` as described in the guide for LAN or proxy access. +# Alvin Zilverstand — portfolio + +A custom, bilingual static portfolio for VISTA college Heerlen. Dark project journal with project dossiers, repository links and a provisional SBB evidence index. No external fonts, tracking, framework, CMS, runtime API requests or production Node service. + +## Run locally + +Requires Node 22 or newer. No dependency installation is necessary. + +Run all commands from the repository root. Start with [the codebase index](docs/codebase-index.md), follow [contributor instructions](AGENTS.md), and see [verification](docs/verification.md) for current results and known limits. + +```sh +npm run dev +``` + +Open http://127.0.0.1:4173. Set `PORT` to change the port. The development server binds to loopback only. + +```sh +npm test +npm run build +``` + +The build regenerates tracked `content.js` from JSON and copies `index.html`, `styles.css`, `app.js`, `content.js` and `favicon.svg` into ignored `dist/`. It does not clean old files from `dist/`; keep that directory limited to these five assets before publishing. A general static host can serve them at a domain root or subdirectory; the included Nginx configuration serves only the domain root. Hash-based routes need no server fallback. Dutch is the default; `?lang=en#evidence` opens English evidence navigation. Language switching preserves the current page. + +## Maintain content + +See [the codebase index](docs/codebase-index.md) for the file map and rendering dependencies. + +Content editing stays on your computer. There is no public admin page or write API. + +- **Add a project:** run `npm run project:add -- my-project`. Open the new `content/projects/my-project.json` and replace the placeholder text. +- **Edit a project:** open its file in `content/projects/`. Text pairs are `[Dutch, English]`. Change `number` to change the display order; the first project is featured on the homepage. +- **Delete a project:** delete its JSON file. Its project card and evidence-index entries disappear on the next preview refresh or build. +- **Add/edit/delete an item:** edit the project's `evidence` array. Copy an existing entry to add one, change its values to edit it, or remove the entry to delete it. An empty array `[]` is allowed. +- **Profile links and processes:** edit `content/settings.json`. Biography, visible name, course details, contribution and reflection placeholders are also hardcoded in `app.js`; document metadata and the fallback link live in `index.html`. + +An evidence item looks like this: + +```json +{ + "label": ["Testverslag", "Test report"], + "path": "projects/my-project/tests.md", + "type": "MD", + "codes": ["B1-K1-W4"] +} +``` + +Use `"directory": true` for a folder. Paths are relative to the school repository. Keep project `id` values stable to preserve links. Use exactly three `nodes` for the system diagram. Project numbers and challenge numbers are strings. + +See [the content reference](docs/content-editing.md) for every field, validation limits and how project tags differ from evidence mappings. + +Run `npm run dev` and refresh the browser to preview saved edits. Invalid content will prevent the preview content module from loading; run `npm run content` for a descriptive validation error. Run `npm run build` to validate and prepare publication. `content.js` is generated; do not edit it directly. `npm run content` regenerates it without building. + +Only deploy `dist/`. Everything in the generated content is public, so keep credentials and private documents out of these files. Repository links remain pinned to the `revision` in `content/settings.json`; update it after reviewing a newer snapshot. + +## Finish the exam content + +The interface is functional; the exam dossier is not yet complete. Summaries are based on the supplied school repository, not invented personal experience. Artifact paths were checked against the repository tree. DOCX contents were not reviewed and the source projects' test scripts were not executed. + +Before submission, add your personal contribution and reflection for every case study, confirm solo/team context, include actual test results, and substantiate improvement claims. Add evidence for B1-K2-W1, W2 and W3 (collaboration, presentation and evaluation). The current mappings are suggestions, not assessment decisions. Ask the examiner which artifacts and authenticity statements VISTA requires. General subjects, electives and institution-specific requirements are outside this vocational index. + +The source is SBB's 2024 qualification for Software Developer, code 25998: +https://kwalificatie-mijn.s-bb.nl/Details/DownloadDocument/1963420 + +English process names are informal translations. The recorded source review date is 9 November 2026; this documentation refresh does not constitute a new source or qualification review. + +Direct contact details, a CV, screenshots, assessed outcomes and personal reflections were not supplied, so the site does not invent them. Add these as real material becomes available. Project diagrams illustrate structure; they are not screenshots of running applications. + +## Host on Proxmox with Docker + +See [Docker hosting instructions](docs/docker-hosting.md) for installation, network access, reverse proxies and content updates. + +Run `docker compose up -d --build` from the repository on your Docker guest. Docker builds from the JSON source files; no manual build or Node installation is needed on the guest. The default binding is localhost only. Configure `.env` as described in the guide for LAN or proxy access. + +## Verify and publish changes + +Run `npm test`, `npm run build` and `git diff --check`. Both test and build commands regenerate `content.js`; commit it with any JSON changes. Review `git diff` and stage only intended files. Never commit `.env` or `dist/`. + +Fetch the remote before publishing. If the remote branch advanced, rebase only your unpublished commits onto it, resolve conflicts, and repeat affected checks. Push normally; do not force-push shared history. A Git push updates the source repository, not the running Docker deployment. On the hosting guest, use `git pull --ff-only` and rebuild as described in the hosting guide. diff --git a/docs/codebase-index.md b/docs/codebase-index.md index fc1209c..bbc18e5 100644 --- a/docs/codebase-index.md +++ b/docs/codebase-index.md @@ -1,34 +1,46 @@ -# Codebase index - -Indexed 9 November 2026, before the content workflow changes. This is a vanilla JavaScript static portfolio with hash routing, Dutch/English text, and no runtime dependencies. - -| File | Responsibility | -| --- | --- | -| `content/projects/*.json` | Editable projects, each with its evidence items; display order uses `number` | -| `content/settings.json` | Profile links, pinned source revision, eight process definitions | -| `content.js` | Generated browser module; do not edit directly | -| `app.js` | DOM rendering, translations, navigation, evidence filtering and printing | -| `styles.css` | Desktop/mobile layouts, project diagrams, accessibility and print styles | -| `index.html`, `favicon.svg` | Document shell, metadata and icon | -| `scripts/content.mjs` | Validate content, generate module, scaffold a project | -| `scripts/serve.mjs` | Loopback-only static preview; compiles content when requested | -| `scripts/build.mjs` | Validate/generate content, copy five public assets to `dist/` | -| `tests/` | Content integrity and editing regression checks | -| `Dockerfile`, `.dockerignore` | Build and test source in Node, then serve public assets with Nginx; see compose.yaml, docker/nginx.conf and docs/docker-hosting.md | -| `docs/verification.md` | Earlier verification record, not a current test report | - -## Rendering and dependencies - -`content/ → scripts/content.mjs → content.js → app.js → main` - -Routes: `#home`, `#work`, `#project/`, `#evidence`, `#evidence/`, `#about`. Unknown routes show a 404. Language is selected using `?lang=nl` or `?lang=en`. - -`header` and `footer` render shared navigation. `home` and `work` render project lists; `detail` renders a dossier. `processRow` derives evidence counts and links from every project's `evidence` array. Removing evidence automatically removes its process-index entries. - -At initial indexing there were three projects and twelve evidence entries in a single handwritten `content.js`. The homepage assumed at least one project, linked directly to `warehouse`, and displayed a fixed count. These assumptions were removed for content management. The first project by number is now featured; an empty portfolio is supported. - -Project IDs are stable route identifiers. Evidence paths are relative to `profile.school` at the pinned `revision`. Text pairs are `[Dutch, English]`. The existing design uses exactly three diagram nodes. Personal contribution and reflection copy is still shared placeholder text in `app.js`. - -## Exposure boundary - -Editing happens in local JSON files. The preview server has no write endpoint and binds to `127.0.0.1`. Production ships five static files, with no editor, login, database, or server process. All content included in a build is public: only put publishable material in these files. Publish `dist/`, not the repository root. +# Codebase index + +Reviewed 10 November 2026 against the current source. This is a vanilla JavaScript static portfolio with hash routing, Dutch/English text, and no runtime dependencies. The source contains three projects, twelve evidence items and eight process definitions. + +| File | Responsibility | +| --- | --- | +| `README.md`, `AGENTS.md` | Setup, publication workflow and contributor instructions | +| `package.json` | Node >=22 requirement and five npm commands; no dependencies | +| `content/projects/*.json` | Editable projects, each with its evidence items; display order uses `number` | +| `content/settings.json` | Profile links, pinned source revision, eight process definitions | +| `content.js` | Generated browser module; do not edit directly | +| `app.js` | DOM rendering, translations, navigation, evidence filtering and printing | +| `styles.css` | Desktop/mobile layouts, project diagrams, accessibility and print styles | +| `index.html`, `favicon.svg` | Document shell, metadata and icon | +| `scripts/content.mjs` | Validate content, generate module, scaffold a project | +| `scripts/serve.mjs` | Loopback-only static preview; compiles content when requested | +| `scripts/build.mjs` | Validate/generate content, copy five public assets to `dist/` | +| `tests/` | Content integrity and editing regression checks | +| `Dockerfile`, `.dockerignore` | Allowlisted build context; test/build in Node, then copy public assets into Nginx | +| `compose.yaml`, `.env.example` | Host binding, port, restart policy, read-only runtime, temporary storage and log rotation | +| `docker/nginx.conf` | Domain-root public-file allowlist, response headers and `/healthz` | +| `.gitignore` | Excludes `dist/`, `node_modules/`, logs and `.env` | +| `docs/content-editing.md` | Field reference, editing workflow and validation limits | +| `docs/docker-hosting.md` | Guest deployment, separate proxy topology, updates and operations | +| `docs/verification.md` | Dated current checks, historical results and remaining verification limits | +| `docs/preview.png`, `docs/mobile-preview.png` | Historical visual references; not generated or refreshed by the build | + +## Rendering and dependencies + +`content/ → scripts/content.mjs → content.js → app.js → main` + +Routes: `#home`, `#work`, `#project/`, `#evidence`, `#evidence/`, `#about`. Empty hash opens home. Unknown page/project routes render an in-page 404; an unknown evidence code falls back to all processes. Language is English only for `?lang=en`, otherwise Dutch. Switching language updates the query without losing the route. + +`header` and `footer` render shared navigation. `home` and `work` render project lists; `detail` renders a dossier. `processRow` derives evidence counts and links from every project's `evidence` array. Removing evidence automatically removes its process-index entries. + +The compiler reads JSON files directly inside `content/projects/`, sorts by `number` using numeric-aware comparison, validates project fields and emits exports. The first project is featured and the homepage count is derived from the array; an empty portfolio is supported. The preview generates content in memory on request. Content, test and build commands regenerate the tracked module on disk. + +Project IDs are stable route identifiers. Evidence paths are relative to `profile.school` at the pinned `revision`. Text pairs are `[Dutch, English]`. The existing design uses exactly three diagram nodes. Personal contribution and reflection copy is still shared placeholder text in `app.js`. + +`tests/content.test.mjs` checks translations, mappings, pinned URL construction and the currently missing collaboration evidence. `tests/editor.test.mjs` checks compilation, empty collections, invalid inputs and homepage rendering with the featured project or all projects removed. Its DOM stub does not test real layout or browser interactions. + +The print button opens all currently rendered process details and invokes browser printing; a filtered view prints only that process. The skip link focuses the main region without changing the route. Route changes focus main and scroll to the top. Responsive, reduced-motion and print rules live in `styles.css`. + +## Exposure boundary + +Editing happens in local JSON files. The preview server has no write endpoint and binds to `127.0.0.1`; it serves only `/` and the five public assets. Production ships five static files, with no editor, login, database or application backend. Docker uses an Nginx server process on port 8080 and adds `/healthz`. All content included in a build is public: only put publishable material in these files. Publish `dist/`, not the repository root. The build overwrites its five files but does not remove stale files from that directory. diff --git a/docs/content-editing.md b/docs/content-editing.md new file mode 100644 index 0000000..a3ab433 --- /dev/null +++ b/docs/content-editing.md @@ -0,0 +1,51 @@ +# Content editing reference + +The editable source is `content/`. `content.js` is a tracked generated browser module; `dist/` is ignored build output. No dependency installation or public admin interface is needed. + +## Project workflow + +1. Run `npm run project:add -- my-project` from the repository root. IDs use lowercase letters, digits and single separating hyphens. The command refuses to overwrite an existing filename, creates placeholder content and regenerates the module. +2. Replace placeholders in `content/projects/my-project.json`. Use the ID as the filename for consistency; routes use the `id` field, not the filename. +3. Run `npm run content` for validation. Preview with `npm run dev` and refresh after saving. The preview compiles `/content.js` in memory on each request; it does not watch files or reload the browser automatically. +4. Run `npm test` and `npm run build`, inspect both languages, then commit source and generated content together. + +Delete a project's JSON file to remove it. Remove entries from its `evidence` array to remove evidence. Empty project collections and empty evidence arrays are supported. Renaming an ID breaks existing project links; keep IDs stable. + +## Project fields + +| Field | Format and behavior | +| --- | --- | +| `id` | Unique lowercase slug, for example `my-project`; used by `#project/my-project` | +| `number` | Nonempty string; numeric-aware string sorting determines display order and the homepage feature. Use distinct numeric values such as `01`, `02` | +| `challenge` | Nonempty string, including combined labels such as `14 + 15` | +| `kind`, `title`, `name`, `intro`, `context`, `implementation`, `decisions` | Two nonempty strings in `[Dutch, English]` order. `title` is required by validation but not currently rendered | +| `stack` | Nonempty array of nonempty strings; technology badges | +| `nodes` | Exactly three nonempty strings; shared diagram labels in both languages | +| `path` | Repository-relative project directory path, without a leading slash or `.` / `..` segments | +| `codes` | Array of known process codes; dossier tags linking to the evidence index. May be empty | +| `evidence` | Array of evidence objects; may be empty | + +Evidence objects require `label` (`[Dutch, English]`), `path` (repository-relative), `type` (nonempty display label such as `JS` or `DOCX`) and `codes` (array of known process codes). Optional `directory` is a boolean: `true` creates a repository `tree` link; omitted or `false` creates a `blob` link. + +Evidence counts come only from each evidence item's `codes`, not the project's `codes`. An item can map to several processes, so summed process counts can exceed the number of evidence items. Empty mappings are allowed and do not appear in process counts. + +## Shared settings and copy + +`content/settings.json` supplies `profile`, `revision` and `processes`. Keep these top-level keys stable: they become ES module exports. + +- `profile.github` and `profile.gitea` supply external profile links; `profile.school` supplies the repository base for source links. +- `profile.qualification` supplies the qualification document link. `profile.name` and `profile.reviewed` are stored but are not currently rendered; visible identity and biography remain in `app.js`. +- `revision` pins every generated source link. Review project and evidence paths against a new revision before updating it. Change `profile.reviewed` only after that review. +- Each process has a unique `code`, bilingual `title` and bilingual `description`. The current tests expect eight processes. + +Shared contribution and reflection placeholders are in `app.js`. Per-project reflections require a deliberate schema and renderer change; adding arbitrary JSON fields alone will not display them. `index.html` also contains static title, description, language fallback and a school repository link. + +## Validation limits + +The compiler validates project fields and checks mapping codes against settings. It is not a complete settings schema validator, external-link checker or assessment tool. Review settings structure, URLs, unique process codes and content accuracy manually. Text is rendered as escaped text, not Markdown or HTML. + +The current tests deliberately assert that B1-K2-W1, W2 and W3 have no evidence yet. When genuine collaboration evidence is added, update that test to reflect the supported evidence and remaining gaps. Do not remove the safeguard simply to make unsupported mappings pass. + +An invalid file causes preview `/content.js` to return HTTP 500 with a generic message. Run `npm run content` to see the underlying validation or JSON error. The scaffold command writes its new JSON file before compiling; if compilation fails, inspect the created file and fix the reported issue before retrying. + +All generated content is public. The build includes settings and project fields even if the interface does not display them. diff --git a/docs/docker-hosting.md b/docs/docker-hosting.md index 9c9d245..0c7066e 100644 --- a/docs/docker-hosting.md +++ b/docs/docker-hosting.md @@ -1,5 +1,7 @@ # Proxmox Docker hosting +Configuration reviewed 10 November 2026. These instructions describe the checked-in configuration; a live deployment has not been verified. See [verification](verification.md). + Use a Linux guest with Docker Engine and the Docker Compose plugin installed. Copy this repository to the guest, or clone it after committing and pushing your changes. From the repository directory: ```sh @@ -54,12 +56,16 @@ From the proxy box, verify `curl -f http://192.168.1.50:8080/healthz` returns `o ## Updates -Edit the JSON source files locally, then sync the changed files to the guest, including removing deleted project files. With Git, commit/push locally and pull on the guest. Apply updates with: +Edit the JSON source files locally, run `npm test` and `npm run build`, then commit the JSON and generated `content.js` together and push. On the guest, keep local configuration in ignored `.env` and update a clean checkout with `git pull --ff-only`. If pulling fails because of local changes or divergent history, resolve that before rebuilding. Git also removes project files deleted upstream. Apply updates from the repository root with: ```sh docker compose up -d --build +docker compose ps +curl -f http://127.0.0.1:8080/healthz ``` +The health command above uses the default binding. If `.env` binds to the guest's LAN IP or changes the port, use that address and port instead. A push alone does not rebuild or deploy the site; there is no deployment automation in this repository. + Restarting alone does not import edited content; the files are baked into the image. Keep and back up the source checkout. Do not edit inside the container. To refresh base images, run `docker compose build --pull`, then `docker compose up -d`. ## Operations and exposure @@ -74,4 +80,4 @@ The container runs as the Nginx user with a read-only filesystem, dropped Linux The health check expects `/healthz` to return `ok`. The restart policy handles process exits; an unhealthy status alone does not restart the container. Compose settings follow the [Docker service reference](https://docs.docker.com/reference/compose-file/services/). -Local content tests, static build and Compose configuration validation passed. The container could not be built or run locally because the Docker engine was unavailable. Nothing has been deployed to Proxmox. +On 10 November 2026, all six local tests, the static build and `docker compose config --quiet` passed. The Docker engine was unavailable, so image build, runtime health, proxy access and Proxmox deployment remain unverified. Configuration validation alone does not prove that the container can start. diff --git a/docs/verification.md b/docs/verification.md index 6148327..6367d2b 100644 --- a/docs/verification.md +++ b/docs/verification.md @@ -1,4 +1,28 @@ -# Verification — 9 November 2026 +# Verification + +## Current 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 browser and external-source results were not repeated on 10 November. - `node --check app.js` passed. - `npm test`: both content integrity checks passed.