The pages carry the CMS markers (data block, list regions, JSON-LD price,
inline price); PackagesProvider reads the host's data block after hydration
and asks the API only when there is none; the site address comes from the
block. A stand-in for the host (config/hostInjector.ts, --cms-data in the
preview server) and browser tests check the behaviour with different data.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The CMS serves a second banner at /api/v1/offerings/banner?position=top. The
site bakes it into the HTML at build time and replaces it live after
hydration, like the banner under the cards, and both may show at once.
The cards now sit in a wrapping flex row so an incomplete last row is centred
for any number of cards on desktop; phone and tablet stay one column.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The build still bakes the current packages and the active banner into the HTML.
After hydration the page asks /api/v1/offerings and /api/v1/offerings/banner
once and replaces what differs; errors and time-outs keep what was baked, and
a 204 from the banner route hides the banner. The banner is now the
OfferingBanner contract (title, text, optional link) instead of layout=banner.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
With contactForm.enabled=true the e2e and Lighthouse runs asked a token route
that CI does not have (404, console error, run 666). The preview server gets an
opt-in --contact-stub (token 200 without captcha, submit 202); the e2e server
helper and the Lighthouse start command switch it on. Tests that need another
answer still replace it per page with page.route.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
frame-src gets the three exact Friendly Captcha global hosts (no wildcard).
When the widget errors, is blocked or shows no sign of life, the form says so
and offers the mail button instead of blocking silently. Adds an e2e for the
form with a mocked API, a draft privacy text for approval, and label tests.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The test route on the proxy Pi now points at the CMS host on port 5200.
verify-deployment.sh gets a --cms mode that checks the exact security
headers, caching, gzip only, a percent-encoded redirect, the 405 for
POST, and the CMS routes. The deploy-test job uses it once the Gitea
variable ASF_TEST_SERVED_BY_CMS is true.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
On the catch-all 404 page the router shows its pending copy for 500 ms while
the server copy stays hidden with display:none. The test counted h1 elements in
that window and found the hidden one on the faster PC runner. It now counts what
a visitor or screen reader gets, then checks that the hidden copy is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The script body had been saved twice, so a production upload would have run
twice and left web.config backups on the host. Browser tests also get longer
limits on the slow CI runner; the page behaves the same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A remote of . or .. could have made the cleanup pass delete the wrong folder, so
such paths are refused before anything runs. A connection error now ends in the
normal summary instead of aborting the check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each pass is now its own lftp session with a marker in the log, so a failed
asset pass stops the script before any HTML goes up. The test checks those
markers instead of lftp's output format.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The preview server must behave like the real server, or Lighthouse and the
browser tests prove the wrong thing. The tests also cover the new URLs in a real
browser: one redirect, one title, a clean hydration.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The preview server and web.config now follow the same URLs as nginx, without
the SPA fallback. Lighthouse exceptions need a recorded reason and the 404 page
is audited through an opt-in route. The deploy checks the build first and the
served result afterwards. The IIS rules stay unverified until a host exists.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Real nginx passes all 134 server rule tests in CI. The seven remaining failures
were tests cut off at 60 seconds on the Raspberry Pi.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Plain map keys compare case-insensitively, so /Over-Mij was not redirected. A
path starting with an encoded backslash could become an open redirect through
the trailing-slash rule; it now gets the 404 page. Also makes the tests readable
for nginx's workers and less sensitive to the slow CI runner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pages now map to their html file, other forms get one redirect, unknown URLs
get a real 404 and responses are compressed. A browser-free test suite runs the
rules against a real nginx, in CI only so far.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lazy loading saved its bytes during page load, but left the logo empty for a
moment when navigating to the homepage on a wide screen. Also adds the second
unit's code summary and the shared docs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tests cover every page without JavaScript, the menu by keyboard and pointer,
the fade-in at load and on scroll, and image requests per width. They found that
the closed menu's shoot links could take focus, which is fixed here.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The prerendered 404 page is served for other URLs, so its dehydrated match id
differs and the router renders the catch-all's pending component first. Without
one that render was empty, which gave React error 418 and duplicate head tags.
The tests run the built output in a real browser under the production CSP.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>