> 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-session08-claude-code-parity-responsive-e2e/tasks.md). # Task Checklist **Session ID**: `phase25-session08-claude-code-parity-responsive-e2e` **Total Tasks**: 21 **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 | 9 | 9 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **21** | **21** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. * [x] T001 \[S2508] Verify Phase 25 prerequisites, analyzer state, Session 07 validation evidence, and Mission Control route/e2e file paths (`.spec_system/PRD/phase_25/session_08_claude_code_parity_responsive_e2e.md`) * [x] T002 \[S2508] \[P] Create implementation notes scaffold for parity decisions, command output, browser checks, and known follow-ups (`.spec_system/specs/phase25-session08-claude-code-parity-responsive-e2e/implementation-notes.md`) * [x] T003 \[S2508] \[P] Create security compliance scaffold for parity testing, mocked fixtures, route-boundary review, and unchanged bridge writes (`.spec_system/specs/phase25-session08-claude-code-parity-responsive-e2e/security-compliance.md`) *** ## Foundation (5 tasks) Core structures and base implementations. * [x] T004 \[S2508] \[P] Create shared Mission Control e2e bridge fixture with long prompts, human briefings, archived missions, and safe mocked paths matching declared contracts (`tests/e2e/fixtures/hermes-mission-control.ts`) * [x] T005 \[S2508] Add e2e helpers for route navigation, Mission tab activation, drawer opening, copied prompt assertions, and no-overflow checks with deterministic waits (`tests/e2e/fixtures/hermes-mission-control.ts`) * [x] T006 \[S2508] Audit Mission Control presentation contract for Hermes and Claude Code copy, actor labels, archive labels, prompt labels, and exhaustive variant handling (`src/components/hermes/hermes-mission-control.tsx`) * [x] T007 \[S2508] Add stable accessible labels or named regions for drawer, prompt text, archive list, active rail, and copy buttons with platform-appropriate accessibility labels, focus management, and input support (`src/components/hermes/hermes-mission-control.tsx`) * [x] T008 \[S2508] Audit Claude Code route shell live/demo/admin state mapping with explicit loading, empty, error, offline, token-failure, demo, admin-disabled, and admin-ready states (`src/components/hermes/claude-code-mission-page.tsx`) *** ## Implementation (9 tasks) Main feature implementation. * [x] T009 \[S2508] Fix Hermes and Claude Code Mission Control copy or contract drift discovered by the parity audit while keeping shared hook-mediated behavior (`src/components/hermes/hermes-mission-control.tsx`) * [x] T010 \[S2508] Harden long mission prompt, goal prompt, and human briefing containers with wrapping, internal scrolling, and focus-safe drawer close behavior (`src/components/hermes/hermes-mission-control.tsx`) * [x] T011 \[S2508] Harden active rail, optimized preview, create/import forms, and archive list responsive constraints so dynamic text cannot create horizontal overflow (`src/styles.css`) * [x] T012 \[S2508] Align Claude Code page header, support banners, stat tiles, and Mission Control mount with Hermes layout constraints and no horizontal overflow (`src/components/hermes/claude-code-mission-page.tsx`) * [x] T013 \[S2508] Extend route tests to prove Claude Code uses existing Hermes bridge calls and rejects Claude-specific spawn, shell, git, workspace, or execution endpoints (`src/routes/__tests__/agents.test.tsx`) * [x] T014 \[S2508] Extend Mission Control component tests for presentation parity, drawer copy labels, archive labels, rail labels, and long text fallback behavior (`src/components/hermes/__tests__/hermes-mission-control.test.tsx`) * [x] T015 \[S2508] Extend Hermes e2e coverage for assembled Mission layout, long prompt drawer, copy fallback, and mobile no-overflow checks (`tests/e2e/hermes-agent.spec.ts`) * [x] T016 \[S2508] Create Claude Code e2e coverage for live route parity, Mission Control behavior, long prompt drawer, archive action visibility, and mobile no-overflow checks (`tests/e2e/claude-code-agent.spec.ts`) * [x] T017 \[S2508] Add viewport matrix assertions for desktop, tablet, and mobile scroll width plus key Mission Control bounding boxes (`tests/e2e/claude-code-agent.spec.ts`) *** ## Testing (4 tasks) Verification and quality assurance. * [x] T018 \[S2508] \[P] Run focused Mission Control component tests and agent route tests, then record command output (`package.json`) * [x] T019 \[S2508] \[P] Run Playwright Hermes and Claude Code route specs with mocked bridge data and desktop/mobile coverage (`package.json`) * [x] T020 \[S2508] Run typecheck, script typecheck, lint, ASCII validation, and manual responsive review for both routes (`package.json`) * [x] T021 \[S2508] Update implementation notes and security compliance with test output, browser evidence summary, residual risks, and follow-up recommendations (`.spec_system/specs/phase25-session08-claude-code-parity-responsive-e2e/implementation-notes.md`) *** ## 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-session08-claude-code-parity-responsive-e2e/tasks.md?ask=&goal= ``` `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.