Validation: #252 Create arch-landing-site architecture note

validation-252-2026-04-14 Doc

validation pass

Project

Validation: #252 — arch-landing-site note created

Verdict: PASS

[x] Note arch-landing-site exists — get_note(slug="arch-landing-site") returns note id 1538, note_type=doc, project westside-basketball, tags architecture,active,arch:landing-site,westside.
[x] All 4 required sections present — get_note_toc returns: Overview (level 3), Route Group (level 3), Deploy Path (level 3), References (level 3).
[x] All 8 public routes enumerated — Route Group table lists /, /about, /staff, /teams, /tryouts, /schedule, /gear, /sponsors.
[x] Deploy path documented — includes Woodpecker → Harbor (westsidekingsandqueens/app) → kustomize (pal-e-deployments) → ArgoCD → k8s namespace westsidekingsandqueens → Tailscale funnel westsidekingsandqueens.tail5b443a.ts.net.
[x] Links included — References section links project-westside-basketball, reference_westside_email.md, arch-jersey-intake, deployment-lessons, feedback_landing_vs_app.md, convention-architecture-ids.
[x] Structure mirrors arch-jersey-intake — title heading + intro paragraph + themed level-3 sections + References list at bottom.

arch-jersey-intake contains the old misspelled email westsidebasketball@gmail.com in the System B data flow section (step 8). Should be updated to westsidebasktball@gmail.com per reference_westside_email.md. Ironic parallel to the #249 fix on the frontend.
Architecture note coverage gap — several other arch labels in use on board items may lack backing notes. Should audit: grep all arch:* labels, cross-reference with search_notes, file tickets for any misses.