> 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_05_hero_roster_summon_discharge_and_tomes.md).

# Session 05: Hero Roster, Summon, Discharge, And Tomes

**Session ID**: `phase25-session05-hero-roster-summon-discharge-and-tomes` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Polish the hero roster, hero card, and tome collection path so arrivals, active rally, formal discharge, and collected tomes are readable as deliberate events without disrupting selection, sorting, modal details, or existing audio click behavior.

***

## Scope

### In Scope (MVP)

* Add summon banner-rise presentation for newly spawned or spawning heroes
* Add rally treatment for active transitions where existing state proves work has begun
* Add compact Counsel badge for awaiting-input heroes only when board focus is on their flare
* Add honorable-discharge treatment for dismissed hero evidence that is already visible in the UI
* Preserve `HeroRoster` sorting, selected hero behavior, capped visible window, and forced selected-hero visibility
* Preserve `HeroCard` selection and click voice behavior
* Add `collect_scroll` treatment to `ScrollShelf` rows when a scroll is collected
* Add rarity beam and static rarity chip treatments for common, uncommon, rare, epic, and legendary tomes
* Add shelf-fill treatment to the compact Tomes count
* Preserve tome detail modal, portal behavior, Escape close, backdrop close, metadata table, five fundamental tomes, and Lobster unlock logic
* Extend Hero Roster, Hero Card, and Scroll Shelf tests
* Include existing hero detail tests if labels or drawer links change

### Out of Scope

* Hall of Banners, titles, veteran gallery, new achievements, or reward grants
* New tomes or changed Lobster unlock logic
* Generic achievement toast redesign beyond keeping tome ceremony distinct
* New achievement grants for summon, discharge, or tome polish

***

## Prerequisites

* [ ] Session 01 registry is available
* [ ] Shared ceremony presentation components are available

***

## Deliverables

1. Hero arrival, rally, and discharge presentation
2. Tome collection and rarity presentation with static reduced-motion fallback
3. Tests preserving roster sorting, hero card behavior, and scroll modal behavior

***

## Success Criteria

* [ ] Roster sorting, selected hero behavior, and click voice behavior remain unchanged
* [ ] Tome collection idempotency and attribution remain intact
* [ ] Tome ceremony is visually distinct from generic achievement presentation
* [ ] Reduced-motion mode communicates rarity and collection states statically


---

# 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_05_hero_roster_summon_discharge_and_tomes.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.