> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/prd/phase_25/session_02_town_crier_toasts.md).

# Session 02: Town Crier Toasts

**Session ID**: `phase25-session02-town-crier-toasts` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Convert generic toasts into accessible Town Crier cards that preserve the toast store contract, severity behavior, and work-critical priority.

***

## Scope

### In Scope (MVP)

* Update `apps/web/src/components/ToastTray.tsx` to resolve `VerbCeremonySpec` values for visible toasts
* Preserve severity filtering, max visible count, dismissal, and `role="status"`
* Add Town Crier header treatment, priority ribbon, verb label, icon well, and bounded body copy
* Ensure long title/body text wraps or truncates without layout overlap
* Preserve seniority for work-critical messages over game-event presentation
* Add required ceremony data attributes and screen-reader summaries
* Extend `apps/web/src/index.css` with `.ceremony-town-crier` and tone classes needed by this surface
* Extend `apps/web/tests/ToastTray.test.tsx` for behavior preservation and ceremony mapping

### Out of Scope

* New toast store fields
* Audio playback
* Media-sheet runtime loading
* Changes to toast source payloads or severity semantics

***

## Prerequisites

* [ ] Session 01 registry and selector helpers are available

***

## Deliverables

1. Town Crier toast presentation using the shared registry
2. CSS classes for toast ceremony and tone variants
3. Tests for achievement, warning, error, success, info, permission, plan, scan, War Room, scroll, and channel-command toasts

***

## Success Criteria

* [ ] Existing toast filtering, cap, dismissal, and status role behavior remain unchanged
* [ ] Work toasts and game toasts are visually distinct through one component path
* [ ] Toast text remains bounded and does not expose new raw payload detail
* [ ] Game chrome never makes work-critical messages look less important
* [ ] Reduced-motion-safe data attributes and screen-reader summaries are present


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/prd/phase_25/session_02_town_crier_toasts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.