diff --git a/REPORT-testers-2026-10-10.md b/REPORT-testers-2026-10-10.md index 1bdf1f0c..95e21a76 100644 --- a/REPORT-testers-2026-10-10.md +++ b/REPORT-testers-2026-10-10.md @@ -27,7 +27,15 @@ with the tester**, who carries on paying for it. It is never asked back. Felhom with a Cloudflare token scoped so it sees exactly that one zone — the restriction the hub already enforces (`architecture/01-topology-and-trust.md` §7). -**D2 — the places.** The closed test runs with **at most 5 households**. Two exist, so three are open. +**D2 — the places.** The closed test runs with **at most 5 households**. + +**Corrected the same evening, by you: nobody is testing today.** „Tester 1” is a disposable virtual +box, not a household; „Tester 2” is a friend who agreed but has not assembled the machine, and the +laptop is off. So **all five places are open** — the page said „Néhány hely már betöltve”, which was +untrue and is now „A teszt most indul, így jelenleg mind az 5 hely szabad”. The same correction went +into `OUTREACH.md` (five people needed, not three), `CONTEXT.md`, and the terms-1.1 mail, which has +**one** real recipient rather than two. **No scheduled post needed changing** — post 7.1 says +„Keresünk öt magyar háztartást” and never claimed a place was filled. Both are recorded as dated operator rulings at the top of `CONTEXT.md`, and both are published. @@ -172,6 +180,55 @@ thousand impressions. --- +## 5a. The design round (after your screenshots) + +You were right on all four points, and three of them had one cause. + +**`.info-card` and `.highlight-box` are scoped per page** in `site.css` — `.page-technologiak` and +`.page-biztonsagimentes`. The new pages carry `.page-teszteles`, which is not one of those scopes, so +**none of the card chrome applied**: no background, no border, no padding, no list styling. That is why +the numbered points read as a run of plain text. The tester pages now join the technologiak scope, +whose `h3` is a flex row — the right one, because these headings carry an icon. + +**The link colour was a site-wide bug, not a tester-page bug.** There was **no base `a` rule at all**, +so an inline link in body copy fell through to the browser default and changed colour once visited. +`.legal` was the only place it had been fixed. `/gyik` (6 links), `/technologiak` (3) and +`/biztonsagimentes` (2) had the same defect. Fixed for all of them, scoped to text containers so it +cannot touch the nav, the footer, `.cta-button` or the 189 picture-gallery openers — checked: all 189 +are outside `

`/`

  • ` and unchanged, and `/gyik`'s links now compute to `#2EA8F5` (`--blue-bright`). + +**Two smaller gaps the new pages exposed:** `code` was styled only under `.legal`, and a `