Adds AI-DLC construction docs for the front-end shell feature

Functional design, NFR requirements, code generation plan and summary,
and build-and-test instructions with results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-18 17:05:03 +02:00
co-authored by Claude Opus 5.5
parent 4d6408b607
commit 069c7cb7eb
27 changed files with 2343 additions and 16 deletions
@@ -0,0 +1,75 @@
# Build and Test Summary — frontend-shell
Run on 2026-10-18, on a clean install (`node_modules` removed, `pnpm install --frozen-lockfile`), with the full `pnpm check`: **exit 0, 225 s**.
## Build Status
- **Build tool**: pnpm 12 + Vite 8 (`tsc && vite build`)
- **Build status**: ✅ Success
- **Clean install**: ✅ `postinstall` generated the Chakra types automatically
- **Artifacts**: `dist/` with `index.html`, hashed assets, one chunk per route, plus:
- `sitemap.xml` (home only)
- `robots.txt`
- `og-image.jpg`
- `logo.png`
- **Accepted warning**: main chunk > 500 kB (≈170 kB gzip), mostly Chakra; see performance
## Test Execution Summary
### Unit tests
- **Total**: 82 tests in 18 files. **Passed**: 82. **Failed**: 0.
- **Property-based**: 18 properties over 8 pure functions. The seed is logged on every run (e.g. `1344216500`).
- **Coverage**: 100% on all pure functions (enforced); ≈80% of lines overall (reported).
- **Status**: ✅ Pass
### Integration tests
- **Scenarios**: 7 automated (`src/app.test.tsx`) + 5 build-level checks. **Passed**: all.
- **Status**: ✅ Pass
### Performance (Lighthouse)
| Measure | Result | Target |
|---|---|---|
| Home, mobile | 82 | ≥ 80 (temporary) |
| Home, desktop | 99 | ≥ 90 |
| Other pages | 94–95 mobile, 100 desktop | ≥ 90 |
| Accessibility / Best Practices | 100 everywhere | 100 |
| SEO | 100 on indexed pages | 100 indexed |
**Status**: ✅ Pass (with the agreed exception for home mobile)
### Additional tests
- **Security**: ✅ Pass
- `audit:deps` clean.
- All 5 security headers present on `preview`.
- CSP test, e-mail and devtools absent from the build, only the own origin loaded.
- `audit:dev` reports 8 dev-tool advisories, non-blocking by decision.
- **Accessibility (automated)**: ✅ Pass. axe on every page and component; Lighthouse 100.
- **Manual keyboard / screen reader** ([manual-test-instructions.md](manual-test-instructions.md)), run by the owner:
- K3–K6, K9, screen reader and responsive: ✅ good.
- K7–K8: ✅ on mobile with a screen reader; desktop not testable yet (too little content).
- **K1 (skip link invisible): fixed.** Chakra's skip link has no z-index and sat under the fixed header; it now uses `zIndex: skipNav` and `margin: 0`. ✅ Retested by the owner.
- **K2 (Tab after the skip link went into the menu): resolved with K1.** ✅ Retested by the owner: focus moves to the content.
- **"SOCIALS" spelled out by a mobile screen reader**: CSS uppercase is read as an abbreviation. Footer headings now carry an `aria-label` in normal casing (owner choice A). ✅ Mobile: read correctly. Windows desktop screen reader: still spelled out; **accepted by the owner** (visual "SOCIALS" preferred over "Social media"). Option B remains available if this ever needs to change.
- **Contract tests**: N/A, no API yet.
- **E2E**: covered by integration tests in jsdom and by Lighthouse in a real browser. No separate E2E framework.
## Extension Compliance (Build and Test)
- **PBT-08**: ✅ Compliant.
- Shrinking is on.
- Seed logged on every run and replayable with `FC_SEED`.
- Property tests are part of `pnpm check`, the future CI step.
- **SECURITY-04 / 10 / 13 / 15**: ✅ Compliant, see [security-test-instructions.md](security-test-instructions.md).
- **Other rules**: N/A at this stage.
## Overall Status
- **Build**: ✅ Success
- **All automated tests**: ✅ Pass
- **Open**: none (one accepted known issue, see manual tests)
- **Ready for Operations**: Yes, if chosen.
## Follow-ups (carried forward)
1. **CI/CD**: run `pnpm check` on every push.
2. **Production host**: send the same security headers.
3. **Responsive images**: from the API/CMS.
4. **Prerendering**: restores home mobile to ≥ 90 and correct link previews per page.
5. **Contact form and spam filter**: with the .NET API.
6. **Wider browser support**: once visitor statistics exist.