Adds the AI-DLC documents of the testimonials redesign
Continuous Integration / check (pull_request) Successful in 1m45s
Continuous Integration / deploy-test (pull_request) Skipped
Continuous Integration / lighthouse (pull_request) Successful in 8m44s
Continuous Integration / deploy-production (pull_request) Skipped

Requirements, execution plan, functional design, code summaries, build and test results and the audit log; the reverse-engineering notes and the feature registry are updated.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-06 01:24:15 +01:00
co-authored by Claude Sonnet 5.5
parent b03b18f58e
commit 7a5e713b69
26 changed files with 1593 additions and 5 deletions
@@ -0,0 +1,38 @@
# Code summary: section-heading (unit 1)
## What changed
| File | Change |
|---|---|
| `web/src/theme.ts` | New text style `sectionHeading`: heading font, `text-transform: uppercase`, `letter-spacing` from the shared `caps` token (0.22em), line-height 1.15, 26 px on phones and 30 px from `md`. The comment of `sectionTitle` now says it is the plain h2 for blocks that do not use `SectionHeading`. |
| `web/src/components/SectionHeading/SectionHeading.tsx` | The `Heading` uses `textStyle="sectionHeading"`. No new props; alignment, spacing, eyebrow and lead are untouched. The component comment says the case is only CSS. |
| `web/src/components/SectionHeading/SectionHeading.test.tsx` | Two new example tests: the title keeps its text and accessible name while the CSS rules hold uppercase and the `caps` letter-spacing; the plain h2 of `CallToAction` does not get the new style. |
| `aidlc-docs/features/testimonials-redesign/inception/requirements/requirements.md` | FR-TR-05 states 30 px from `md` and 26 px below; A2 holds the estimate for the longest title. |
No callers changed: the eight users of `SectionHeading` (`AboutBlock`, `ContactSection`, `IntroGallery`, `Pricing`, `Testimonials`, `InstagramGrid`, `AboutIntro`, `ShootPage`) get the new style through the component. The five h2 elements that use `sectionTitle` directly (`CallToAction`, `PackageBlock`, `ShootBlock`, `ShootPage` twice, `StoryBlocks`) keep their style (assumption A1).
No file was created or duplicated in `web/`; nothing else in the tests or e2e files referred to the old style.
## Verification of this unit (Step 13.5)
| Check | Result |
|---|---|
| Type check (`tsc --noEmit`) | passed |
| Lint on the changed files | passed |
| Format check (`prettier --check .`) | passed |
| `SectionHeading` tests | 5 passed |
| Whole unit-test run (`vitest run`) | 132 files, 1392 tests passed |
One test assertion was corrected during the run: the rule holds the token as a CSS variable (`var(--slp-letter-spacings-caps)`), not the literal `0.22em`. The code was right; the assertion was changed to check the variable.
Not part of this unit (phase-level Build and Test): prerender build, e2e tests, Lighthouse, and a visual check of every page that shows a `SectionHeading`, including the wrapping of the longest title (A2).
## Extension compliance
| Extension | Rule | Status | Note |
|---|---|---|---|
| Security Baseline | SECURITY-04 | Compliant | The new style is a generated CSS class; no inline style, no header change |
| Security Baseline | SECURITY-10 | N/A | No dependency change (`pnpm install --frozen-lockfile` only restored the worktree) |
| Security Baseline | other rules | N/A | Front-end style change; no inputs, storage, API or identity |
| Property-Based Testing | PBT-01..09 | N/A | No logic and no pure function added |
| Property-Based Testing | PBT-10 | Compliant | Example tests only, because there are no properties to check; existing property tests still pass |