🤖 CI is red for an infrastructure reason, not the code. The runner gets HTTP 429 from the hub while fetching private modules (amadan.net/oficina/estilo, amadan.net/carlos/platform) at the vet step, or during sync. main @ 3339ff6 fails the same way. One re-run of #71 (8673aea) hit the same 429. I've stopped retrying so I don't add to the rate limiting. The local gate passes: see the opening post.
Keep the space in the hero headline on phones open
On branch fix/r1-phone-headline
🤖 Polish round 1: the phone headline.
static/site/index.html:35 wrote new<br>office, and home.css:175 hides .hero-h br at 30rem and below. Every phone therefore read "Open your newoffice suite."
Fix (cf013aa): changed it to new<br> office. When the break shows, the space collapses at the start of the line. When the break is hidden, the space separates the words.
Test: TestFrontPageLineBreaksKeepTheirSpace requires every front-page <br> to have whitespace beside it. It fails before the fix and passes after.
Live check: in Chromium at 390px the h1 reads "Open your new office suite." At 1280px it still breaks after "new".
Gate: vet, fmt, build and go test all pass. Race passes (pinned toolchain; provisioner is linux-only, so CI covers it).
Needs a highest-capability review before merge.
🤖 Whole-branch review — Claude Fable 5.1 (claude-fable-5-1), per AGENTS.md "Review". Diff origin/main...origin/fix/r1-phone-headline (head cf013aa) in a scratch worktree.
VERDICT: APPROVE
- Root cause confirmed:
home.css:175hides.hero-h brat ≤30rem, andnew<br>officehad no whitespace on either side.new<br> officeis the right shape: the leading space collapses at the start of the wrapped line when the<br>shows, and separates the words when it is hidden.index.htmlis the only<br>understatic/site/. - Test exercises the fix:
TestFrontPageLineBreaksKeepTheirSpaceruns against the embeddedindexPage(page.go:29) and fails on main's markup (front page has <br> with no whitespace beside it: ["w<br>o"]), passes on the branch. Its rule ("every front-page<br>needs whitespace on one side") is general enough to catch the next one. - Gate:
GOTOOLCHAIN=go1.26.5 make test-vet test-fmt test-build test-go— allok, exit 0. - No findings. CI red is the hub's HTTP 429 on private modules (main fails the same way); AGENTS.md still wants a green run before the squash.
Merging without a green hub CI run, on Paul's instruction of 2026-09-23 ("Can we merge and deploy where we're at, and continue?"). CI fails for infrastructure reasons only: the hub runner gets HTTP 429 fetching private modules, and its module cache can't be reset (main fails the same way). Fable 5.1 approved the branch, and the local gate passes (GOTOOLCHAIN=go1.26.5 make test-vet test-fmt test-build test-go).