Add reviewed AccuWeather mirror, tasks, and deterministic verifiers

[JeremyJC67]

Adds the AccuWeather mirror at port 40031 with 20 reviewed tasks, judge rubrics, and deterministic verifiers. Preserves @sarendis56's site contribution from #93 and @JeremyJC67's review work, and includes the subsequent GUI audit fixes.

Corrects mobile search and form layouts, menu destinations, radar/AQI legends, and forecast consistency. Task 8 explicitly requests the alert confirmation and task 17 requests the numeric maximum; grading checks units, city/value attribution, contradictions, navigation, and exact database changes.

Integrates current main while preserving the existing 31 site ports. The Dockerfile generates AccuWeather's reset seed from tracked code. .assets-revision retains the merged global asset pin fa1e8a5b9e8e5d0e42764cd658825f4dea088d8f and independently pins the validated AccuWeather archive at immutable HF commit 0a73c1c1ac2e47513389a8a1a67601f75c8c4150 (HF #66). Asset fetching supports scoped revisions and sites with a generated seed and no required downloaded media.

Validation:

• 20/20 tasks completed through GUI actions during the audit, with 20 GIFs; all saved runs also pass the official evaluator from the integrated checkout.
• 111 copied-evidence controls match their expected outcomes; 301 verifier tests and 8 asset-download tests pass.
• Fresh asset download/extraction succeeds for all 32 sites; the registry and all task URLs agree on 40000–40031.
• Full Docker build succeeds; all 32 sites are healthy and respond HTTP 200. All 51 tracked AccuWeather runtime files match the checkout.
• Task 6 passes a fresh scripted GUI replay on the integrated image; reset after its saved-location mutation restores seed byte identity, and process restart preserves it.

Weather is synthetic and radar is illustrative. The secondary LLM judge was not run because its API/model configuration is absent. Detailed corrections and integration evidence are documented in review-reports/accuweather-pr98-fixes.md.

[sarendis56]

Contributor asset follow-up for the remaining archive-layout finding:

HF PR #66 is updated at 0a73c1c1ac2e47513389a8a1a67601f75c8c4150. It now contains only accuweather/static/images/ (eight SVG icons), with no unsupported fonts root, stale seed database, or AppleDouble/Finder metadata. This matches this branch's build-generated seed contract.

I downloaded the uploaded bundle and confirmed it passes validate_asset_archive.py (10 managed members). Your code, tasks, and verifiers are untouched. HF merge and the subsequent .assets-revision pin remain the release steps.

[JeremyJC67]

Independently validated, and it matches your report. Downloaded refs/pr/66 at 0a73c1c1 on the review host and ran the repo's own validator:

bytes: 5524      md5: 522284a9610b5699d3982b48878b3623
members: 10      AppleDouble/DS_Store: 0
archive roots: accuweather/        second level: accuweather/static
validate_asset_archive.py -> validated 10 managed members for accuweather

That clears the blocker. The archive is rooted at accuweather/, carries only the managed static/images root, and no longer ships the unsupported fonts root or the stale seed database — which is right, since this site generates its seed at image build time.

One thing worth knowing that is on my side, not yours: when I merged the 26-site main into this review branch, my conflict resolution took upstream's Dockerfile wholesale and silently dropped the accuweather build-time seed step. The container then died at boot on cp -a .../instance_seed before the control plane came up. I have restored that step verbatim (e9e0809) and the site is being re-verified now. Nothing in your code or assets caused it.

Remaining is release mechanics only: a maintainer merges HF #66, then I pin .assets-revision to the merge sha.

[JeremyJC67]

Rebased onto the 26-site main — this branch is now site 27 / port 40026

main merged FedEx (40024) and WebMD Doctor (40025) overnight, which put every open site
branch into conflict. This branch has been brought up to date by merging main rather than
rebasing, so every contributor and reviewer commit is preserved verbatim, and re-slotted to
index 26 / port 40026: registry, Dockerfile EXPOSE, the shared docs and every
site-local port reference follow. The slot is provisional as always — say the word at merge
time and I will re-slot in whatever order you land things.

The whole environment was then rebuilt and re-verified at the new slot:

check	result
HTTP sweep	27/27 return 200
GET /health	ok, 27/27 alive and ready
POST /reset/accuweather → md5	cbddbe8704539f93e5be0f5f87959099, identical to the seed
POST /reset-all	ok, 27/27 ready, 1.63 s
verifier no-op matrix	20/20 FAIL
registry + docs tests	4 passed, 3,343 subtests

Worth recording because it was my fault, not yours: my first attempt at this merge resolved the
Dockerfile conflict by taking upstream's copy wholesale, which dropped this site's build-time
seed step. Since accuweather ships no instance_seed, websyn_start.sh then died on
cp -a .../instance_seed and the container exited six seconds after start. The step is restored
verbatim in e9e0809 and the run above is with it in place.

Still blocked only on HF #66 being merged, after which I repin .assets-revision.