Files
jobtrackingapp/docs/verification/jt-018-developer-documentation.md
T
2026-08-30 11:32:00 +02:00

2.2 KiB

JT-018 developer and operator documentation verification

Implemented

  • Replaced the obsolete Create React App frontend guide with the actual Next.js 16, React 19, TypeScript, Jest, ESLint and Playwright workflow.
  • Corrected the root quickstart to use the committed npm and NuGet lock files (npm ci and dotnet restore --locked-mode).
  • Documented the separate normal-development (3000) and isolated Playwright (3300) frontend ports.
  • Removed the obsolete npm peer-dependency override and verified the current graph installs without it.
  • Corrected the production provider matrix: SQLite and MariaDB/MySQL are implemented; PostgreSQL is not.
  • Corrected the architecture inventory to React Router 7 and removed completed roadmap suggestions from the runtime README.
  • Linked environment, architecture, deployment, audit and programme sources so historical phase notes are not mistaken for current setup instructions.

Proof

  • Clean npm ci: passed without the removed .npmrc override and without lockfile drift.
  • Frontend lint: zero warnings.
  • Frontend Jest: 64/64 suites, 272/272 tests.
  • CV Builder autosave regression: 12/12 tests; timing-dependent manual-save assertions now verify the actual debounced autosave contract.
  • Next.js production build and integrated TypeScript check: passed.
  • API and test-project NuGet restore with --locked-mode: passed.
  • Backend: 719/719 tests passed on SDK 9.0.317.
  • Documentation stale-claim and referenced-path checks: passed; the only PostgreSQL mention explicitly states that it is unsupported.

Environment note

SDK 9.0.317 is installed at the user-local .dotnet location. This workstation also has a runtime-only C:\Program Files\dotnet host earlier on PATH; verification therefore invoked the installed SDK host explicitly. The repository's global.json correctly rejects the runtime-only host instead of silently selecting a different SDK.

Remaining external proof

A truly clean second machine and production operator rehearsal were not used. The documented install, lint, test, build and locked-restore commands were executed against a clean frontend dependency installation and the current repository checkout.