> 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/specs/phase24-session05-scrying-and-alert-focus/tasks.md).

# Task Checklist

**Session ID**: `phase24-session05-scrying-and-alert-focus` **Total Tasks**: 18 **Estimated Duration**: 2-4 hours **Created**: 2026-07-08

***

Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID.

***

## Setup (2 tasks)

* [x] T001 \[S2405] Verify prerequisite session artifacts and live battlefield files (`.spec_system/specs/phase24-session03-live-enemy-presentation/validation.md`, `.spec_system/specs/phase24-session04-combat-playback-effects-layer/validation.md`, `apps/web/src/components/battlefield/Battlefield.tsx`)
* [x] T002 \[S2405] Confirm current alert-focus and hero-activity contracts (`apps/web/src/lib/gameProjection.ts`, `apps/web/src/store/useGameStore.ts`, `apps/web/tests/gameProjection.test.ts`)

***

## Foundation (4 tasks)

* [x] T003 \[S2405] Create scrying and alert-focus presentation types plus named threshold constants (`apps/web/src/lib/scryingAndAlertFocus.ts`)
* [x] T004 \[S2405] Implement per-hero activity derivation from event log, missions, heroes, and projection clock with bounded labels (`apps/web/src/lib/scryingAndAlertFocus.ts`)
* [x] T005 \[S2405] Implement alert focus target resolution for flare, gate, siege, ram, skirmisher, and newCamp using existing coordinates and anchors (`apps/web/src/lib/scryingAndAlertFocus.ts`)
* [x] T006 \[S2405] Write pure derivation tests for threshold edges, clearing, target resolution, fallback labels, and calm silence (`apps/web/tests/scryingAndAlertFocus.test.ts`)

***

## Implementation (8 tasks)

* [x] T007 \[S2405] Create board-internal scrying and alert focus layer with product-facing summaries (`apps/web/src/components/battlefield/ScryingAndAlertFocusLayer.tsx`)
* [x] T008 \[S2405] Wire one shared Battlefield clock with cleanup on scope exit for threshold updates (`apps/web/src/components/battlefield/Battlefield.tsx`)
* [x] T009 \[S2405] Pass derived scrying and alert-focus presentations into layer ordering without blocking hero, camp, or wraith controls (`apps/web/src/components/battlefield/Battlefield.tsx`)
* [x] T010 \[S2405] Integrate channeling posture into HeroToken badge, aria label, and data attributes with accessible state copy (`apps/web/src/components/battlefield/Battlefield.tsx`)
* [x] T011 \[S2405] Add rune-circle, static channeling badge, single alert ring, and reduced-motion static styles (`apps/web/src/index.css`)
* [x] T012 \[S2405] Neutralize or re-scope competing urgency pulse styles so `alertFocus` is the only urgency pulse while preserving non-urgent static twins (`apps/web/src/index.css`)
* [x] T013 \[S2405] Add Battlefield component tests for scrying appearance, clearing, one alert ring, focus promotion, and ten-event-free-minute calm behavior (`apps/web/tests/Battlefield.test.tsx`)
* [x] T014 \[S2405] Add reduced-motion and accessible-state interaction tests for channeling badges and single focus treatment (`apps/web/tests/BattlefieldInteraction.test.tsx`)

***

## Testing (4 tasks)

* [x] T015 \[S2405] Run focused Vitest targets (`npm test -- apps/web/tests/scryingAndAlertFocus.test.ts apps/web/tests/Battlefield.test.tsx apps/web/tests/BattlefieldInteraction.test.tsx`)
* [x] T016 \[S2405] Run web package typecheck (`npm --workspace apps/web run typecheck`)
* [x] T017 \[S2405] Run root format check (`npm run format:check`)
* [x] T018 \[S2405] Validate ASCII and LF requirements for session artifacts and touched web files (`.spec_system/specs/phase24-session05-scrying-and-alert-focus`, `apps/web/src/lib/scryingAndAlertFocus.ts`, `apps/web/src/components/battlefield/ScryingAndAlertFocusLayer.tsx`, `apps/web/src/components/battlefield/Battlefield.tsx`, `apps/web/src/index.css`, `apps/web/tests/scryingAndAlertFocus.test.ts`, `apps/web/tests/Battlefield.test.tsx`, `apps/web/tests/BattlefieldInteraction.test.tsx`)

***

## Completion Checklist

* [x] All tasks marked `[x]`
* [x] All tests and checks passing
* [x] All files ASCII-encoded with LF line endings
* [x] implementation-notes.md updated
* [x] Ready for `creview` (next step in the implement -> creview -> validate sequence)

***

## Next Steps

Run the `implement` workflow step.


---

# 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/specs/phase24-session05-scrying-and-alert-focus/tasks.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.
