fix(site): the weekend rule reached the table and not the sentence

[lroolle]

PRICE_SCHEDULE learned on 2026-08-22 that peak is weekdays only. Four
places a reader — or a search engine — actually reads did not.

What was stale

• cost/ rate-card blurb: "Peak hours are 01:00–04:00 and 06:00–10:00 UTC daily"
• three JSON-LD FAQ answers on news/, which is the text that gets quoted back in search results
• bench/'s "schedule what can be scheduled" bullet, which named the windows and not the days
• price_now_verdict()'s not-yet-live branch, which still described the previous era's flip: adding the weekend era repointed eras[-1] at a new instant while the copy went on saying "every hour bills at the flat card below"

make price-check compares the CLI's card against the gateway's, and
build.py --check compares committed HTML against the generator. Neither
can see a sentence disagreeing with the table it sits next to.

What stops it recurring

check_peak_claims() runs on every build and every --check. It splits
each page on <h2> — the unit a reader arrives at from a search result —
and fails when a section quotes both peak windows without the day
restriction read off PRICE_SCHEDULE, not typed into the check.
price_now_verdict() now derives that phrase too, so both branches of it
follow the data.

The escape hatch is a marker, not a turn of phrase: a news entry about a
superseded announcement carries <!-- claim:historical -->. "This is
history" is a claim the author makes on purpose.

Verified both directions

break	result
drop the qualifier from one live bullet	exit=1, names bench/: What it means in practice
drop days from PRICE_SCHEDULE	exit=1, names all five sections that still say Mon–Fri

make site-check clean. No rate-card numbers changed — the card already
matched both published tables.