Feature/grounded shop assistant page

[jy7lsna]

Description

Adds a new use-case detail page, /use-cases/grounded-shop-assistant, showcasing the statewave-grounded-shop-assistant reference build: a shopper + ops assistant pair that answers strictly from retrieved evidence, validates every citation against what was actually retrieved, and routes ungrounded questions into a coverage-gap episode the content team resolves.

Related Issue

N/A — no tracking issue.

Closes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📚 Documentation update
• 🔧 Maintenance (refactoring, dependencies, CI, etc.)
• 🧪 Test improvement

Changes Made

• New GroundedShopAssistantPage (src/pages/GroundedShopAssistantPage.tsx): hero with chat mockup, "two outcomes" grounding explainer, why-grid, architecture/pipeline walkthrough, ops console mockup, subjects table, API reference, run instructions, closing CTA
• Registers the route in src/App.tsx (lazy-loaded) and src/lib/seo-meta.ts (title/description/canonical/OG/Twitter meta)
• Adds the page to the use-case registry (src/lib/use-case-pages.ts), which feeds the UseCaseSwitcher dropdown on every use-case page automatically
• Adds the "Grounded shop assistant" card to the use-case grid on UseCasesPage

Testing

• Unit tests pass locally
• Manual verification completed (typecheck, lint, route/SEO wiring reviewed by hand)
• New tests added for new functionality not needed: tests/seo.test.tsx and tests/seo-static.test.ts iterate PUBLIC_ROUTES, so the new route's title/description/canonical/OG/Twitter tags are covered automatically

Test Commands Run

npm run typecheck
npm run lint
npm test

All green. (One caveat: npm test showed 4 failures on the first run, in /why and /product SEO/route/smoke tests confirmed pre-existing test-order flakiness unrelated to this change by rerunning each failing file in isolation, where all passed.)

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have commented my code where necessary
• I have updated documentation as needed (SEO meta, use-case registry)
• My changes generate no new warnings or errors
• I have added tests that prove my fix/feature works covered by existing route-driven SEO tests, see above
• All existing tests pass
• I have checked for breaking changes none; new route only, no existing routes touched

Screenshots / Recordings

Additional Notes

[vercel]

@jy7lsna is attempting to deploy a commit to the Statewave Team on Vercel.

A member of the Team first needs to authorize it.

[smaramwbc]

Shipped 🎉 — landed on main via #237 (squashed as 5d76012) with the other pages. One change on the way in: the page now links the reference build's new home at smaramwbc/statewave-grounded-shop-assistant — the TypeScript version of the repo that went live this week. Thanks for building both the assistant and its page; closing since the content is merged.