Run a browser smoke test against conderis.com after every deploy #345

Why

Finished web changes are deployed right away (see the always-deploy decision), and several UI changes went live without anyone seeing them in a browser. A failed deploy or a broken circuit should show up at once, not when the user next opens the site.

Work

• Playwright (or similar) checks against https://conderis.com, run at the end of scripts/Publish-Web.ps1 -Deploy.
• Signed in through a dedicated test account whose credentials stay out of the repository.
• Checks: home page loads and the circuit starts; sidebar opens, search filters and clears; a project page loads its tabs; toggling a favorite moves the project into Favorites and back; no console errors.
• The script fails loudly and names the step that broke.

Acceptance

• One command runs the smoke test locally and against production.
• Publish-Web.ps1 runs it after a real deploy and reports the result.
• The test leaves no data behind (favorite toggled back, no created items).
• Documented in WEB.md.