> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase25-session06-active-mission-rail-progress/tasks.md).

# Task Checklist

**Session ID**: `phase25-session06-active-mission-rail-progress` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-08

***

## Legend

* `[x]` = Completed
* `[ ]` = Pending
* `[P]` = Parallelizable (can run with other \[P] tasks)
* `[SNNMM]` = Session reference (NN=phase number, MM=session number)
* `TNNN` = Task ID

***

## Progress Summary

| Category       | Total  | Done   | Remaining |
| -------------- | ------ | ------ | --------- |
| Setup          | 3      | 3      | 0         |
| Foundation     | 5      | 5      | 0         |
| Implementation | 8      | 8      | 0         |
| Testing        | 4      | 4      | 0         |
| **Total**      | **20** | **20** | **0**     |

***

## Setup (3 tasks)

Initial configuration and environment preparation.

* [x] T001 \[S2506] Verify Phase 25 prerequisites, analyzer state, Session 05 validation evidence, and active Mission Control file paths (`.spec_system/PRD/phase_25/session_06_active_mission_rail_progress.md`)
* [x] T002 \[S2506] \[P] Create implementation notes scaffold for rail, progress, command output, and manual checks (`.spec_system/specs/phase25-session06-active-mission-rail-progress/implementation-notes.md`)
* [x] T003 \[S2506] \[P] Create security compliance scaffold for presentation-only mission projection and unchanged admin-gated writes (`.spec_system/specs/phase25-session06-active-mission-rail-progress/security-compliance.md`)

***

## Foundation (5 tasks)

Core structures and base implementations.

* [x] T004 \[S2506] \[P] Create exact mission progress helper with raw percent, display percent, milestone positions, and empty-state handling (`src/lib/hermes-mission-progress.ts`)
* [x] T005 \[S2506] Add current-goal selection and deterministic sorted-goal helpers with types matching the declared Hermes mission contract and exhaustive status handling (`src/lib/hermes-mission-progress.ts`)
* [x] T006 \[S2506] \[P] Create focused mission goal rail component shell with typed props, stable stage dimensions, and existing action callback boundaries (`src/components/hermes/hermes-mission-goal-rail.tsx`)
* [x] T007 \[S2506] Define rail keyboard, scroll, and selection state with cleanup on scope exit for all acquired listeners (`src/components/hermes/hermes-mission-goal-rail.tsx`)
* [x] T008 \[S2506] Add route-scoped rail class names and CSS custom property contract for progress fill and milestone ticks (`src/components/hermes/hermes-mission-goal-rail.tsx`)

***

## Implementation (8 tasks)

Main feature implementation.

* [x] T009 \[S2506] Replace rounded mission metric geometry with exact progress helper while preserving rounded labels (`src/components/hermes/hermes-mission-control.tsx`)
* [x] T010 \[S2506] Render the active mission rail above the existing full mini-goal grid with explicit loading, empty, error, and demo-state preservation through the parent state branches (`src/components/hermes/hermes-mission-control.tsx`)
* [x] T011 \[S2506] Wire rail detail, copy, and tick controls to the existing Mission Control handlers with duplicate-trigger prevention while actions are in-flight (`src/components/hermes/hermes-mission-control.tsx`)
* [x] T012 \[S2506] Implement one-goal focus, prev/next controls, direct goal selection, keyboard navigation, and revalidation on active mission changes (`src/components/hermes/hermes-mission-goal-rail.tsx`)
* [x] T013 \[S2506] Implement milestone-aligned gradient progress bar using exact CSS width values, deterministic tick positions, and rounded display text only (`src/components/hermes/hermes-mission-goal-rail.tsx`)
* [x] T014 \[S2506] Preserve full grid scan behavior, card action parity, actor pills, estimates, status display, and reduced-motion-safe confetti behavior (`src/components/hermes/hermes-mission-control.tsx`)
* [x] T015 \[S2506] Add route-scoped rail, scrollbar, progress animation, responsive sizing, text wrapping, and reduced-motion fallback styles (`src/styles.css`)
* [x] T016 \[S2506] Confirm Hermes and Claude Code presentation parity for rail labels, actor labels, progress display, and shared action behavior without new bridge behavior (`src/components/hermes/hermes-mission-control.tsx`)

***

## Testing (4 tasks)

Verification and quality assurance.

* [x] T017 \[S2506] \[P] Write unit tests for exact progress ratios, display rounding, milestone positions, empty/all-done missions, and current-goal selection (`src/lib/__tests__/hermes-mission-progress.test.ts`)
* [x] T018 \[S2506] Extend component tests for rail rendering above the grid, exact progress geometry at representative ratios, and full-grid preservation (`src/components/hermes/__tests__/hermes-mission-control.test.tsx`)
* [x] T019 \[S2506] Extend component tests for prev/next, keyboard navigation, detail/copy/tick actions, reduced-motion behavior, and Claude Code parity (`src/components/hermes/__tests__/hermes-mission-control.test.tsx`)
* [x] T020 \[S2506] Run focused tests, typecheck, lint, ASCII validation, and manual desktop/mobile rail overflow review (`package.json`)

***

## Completion Checklist

Before marking session complete:

* [x] All tasks marked `[x]`
* [x] All tests passing
* [x] All files ASCII-encoded
* [x] implementation-notes.md updated
* [x] security-compliance.md updated
* [x] Ready for the validate workflow step

***

## Next Steps

Run the validate workflow step to verify session completeness.


---

# 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase25-session06-active-mission-rail-progress/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.