Visitor response policy: verification
18 September 2026. Local changes on base 91cec88a; not deployed.
Changes
- Fixed replies for explicit past-edition questions, redirecting to current/future event pages; prompt policy covers other historical phrasing.
- Personal-information requests receive a non-disclosure response and Support privacy/data-processing contact. Seeded name/email/company were not disclosed. Details/corrections and genuine enquiry-send requests remain supported.
- UNLEASH WORLD capitalization and standard support email addresses are normalized across streamed chunk boundaries.
- Clear sponsor/exhibitor contact questions use Customer Success; other contact questions use Support. Direct contact questions return one address without retrieval. Application policy overrides stale CMS/FAQ instructions.
Validation
- Web package: 156 tests passed, zero failed, including six new policy tests.
- Chunk-boundary tests split brand/email Markdown at every offset; ordinary text is delivered before stream close.
- Biome and diff whitespace checks passed. Typecheck has existing repository diagnostics; no diagnostics in touched files.
- Nine live local HTTP API cases passed the targeted assertions below. No contact request or real enquiry was sent.
| Case | Result | HTTP | Chunks |
|---|---|---|---|
| past-year | Pass | 200 | 1 |
| past-general | Pass | 200 | 1 |
| privacy | Pass | 200 | 1 |
| privacy-spex | Pass | 200 | 1 |
| refund | Pass | 200 | 1 |
| spex | Pass | 200 | 1 |
| ambiguous | Pass | 200 | 1 |
| brand | Pass | 200 | 30 |
| current | Pass | 200 | 97 |
Limits and exploratory findings
The initial exploratory run encountered Pinecone network/retry failures and produced a confusing conditional department sentence in the ambiguous-contact case. This led to the deterministic direct-contact answer. The final run above uses that correction. Both sets of transcripts are retained.
These checks establish the specified responses and control behavior, not universal semantic coverage. Historical questions phrased outside the explicit guard patterns rely on the model following the application prompt; no claim of exhaustive detection is made. Past references in a current/future question remain answerable. This is local API testing, not a staging deployment or full UAT rerun.