Verified on 7 November 2026. Host: Windows / PowerShell 7 / Node 26.13.0. Production image: Node 24 Alpine, running as the non-root node user. Integration database: isolated PostgreSQL 17 Alpine containers.
| Check | Result |
|---|---|
npm run lint |
Passed, no lint errors |
npm run typecheck |
Passed with strict TypeScript settings |
npm run build |
Passed |
npm test -- --runInBand |
10 suites, 29 tests passed |
npm run test:e2e |
2 suites, 41 tests passed, real PostgreSQL |
npm audit --omit=dev |
0 known production vulnerabilities |
Full npm audit |
9 low-severity development-tool findings; no moderate/high/critical findings |
Production docker build |
Passed, including a clean npm ci, compilation and pruning development dependencies |
| Docker Compose configuration | Validated with temporary test settings |
pwsh -File test/verify-runtime.ps1 -SkipBuild |
Passed against the final image |
The 41 integration tests cover 33 authentication/security cases and eight retained p6 business cases. They exercise normalized login, per-request profiles, hashed refresh storage, rejection of old API keys, missing/malformed/expired/tampered JWTs, algorithm/issuer/audience/purpose checks, invalid claim types, subject/session binding, future issuance, maximum token lifetime, anonymous access, role boundaries, password non-disclosure, input validation, uniqueness, password byte limits, refresh rotation/replay/concurrency/absolute expiry, logout/all-device logout, password changes and admin resets, user deactivation, last-admin protection, persistent account cooldown, IP throttling and CORS. Business cases cover idempotency, full transaction rollback, partial order updates, inventory restoration, history retention, payment restrictions and concurrent overselling prevention.
The independent production-image smoke check used a fresh PostgreSQL database with no published ports. It ran both migrations, bootstrapped the first administrator, confirmed bootstrap rerun refusal, started the actual compiled production server, authenticated an admin, created and authenticated a reader, checked role restrictions and password exclusion, created a customer/product/order, checked the total and reserved stock, rotated/replayed refresh tokens, checked immediate access-token revocation and logout, ran the cleanup CLI, verified a non-root UID and confirmed Nest CLI was absent from the runtime. Its temporary containers were stopped automatically.
The remaining development findings stem from the deepmerge advisory GHSA-gcqx-w48m-w2h4 through Jest/Nest CLI tooling. The audit suggested major downgrades of the toolchain rather than a compatible patch; those downgrades were not applied. These tools are excluded from the production image. This audit is a point-in-time dependency check, not a penetration-test certification.
The implementation was first verified in a separate p6_1a directory, then copied into the existing p6_1 Git working tree at the user's request. The repository was clean before replacement; its history and remote configuration are retained. No existing application database was modified. Test containers used disposable data and were removed after verification. Configure your own deployment secrets and initial admin before running a persistent environment; no default credentials were installed.
After replacement, 84 application/configuration/test files were checked byte-for-byte against the verified p6_1a version. Three documentation files were adjusted to describe the existing repository location. A fresh locked dependency install, lint, type checking, build and all 29 unit tests passed in the original Git working tree. Git whitespace checks passed. The 41 PostgreSQL integration tests and production-image checks above were run on the identical implementation before relocation. Obsolete legacy implementation files were removed; changes remain unstaged and uncommitted on the existing main branch for review.