> 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/phase40-session10-assets-and-media-compliance/tasks.md). # Task Checklist **Session ID**: `phase40-session10-assets-and-media-compliance` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-07-03 *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID. *** ## Setup (4 tasks) * [x] T001 \[S4010] Verify analysis state, required Session 01 and Session 09 artifacts, worktree cleanliness, and current asset inventory (`.spec_system/specs/phase40-session10-assets-and-media-compliance/implementation-notes.md`) * [x] T002 \[S4010] Capture baseline asset-size, SVG-safety, and Ministry hero evidence with current commands (`.spec_system/specs/phase40-session10-assets-and-media-compliance/asset-provenance.md`) * [x] T003 \[S4010] Confirm final provider and model-intelligence coverage from existing Hermes catalog and Session 09 artifacts (`scripts/lib/hermes-dev-bridge.ts`) * [x] T004 \[S4010] Create the final Hermes logo namespace for rehomed provider SVG assets (`src/assets/logos/hermes/`) *** ## Foundation (5 tasks) * [x] T005 \[S4010] Move the 15 staged root provider SVGs into the final Hermes logo namespace (`src/assets/logos/hermes/`) * [x] T006 \[S4010] \[P] Create script-side expected media inventory and path metadata for provider logos and the Ministry hero (`scripts/lib/hermes-media-audit.ts`) * [x] T007 \[S4010] \[P] Implement SVG safety, logo-size, root-path cleanup, and duplicate-decision audit helpers (`scripts/lib/hermes-media-audit.ts`) * [x] T008 \[S4010] \[P] Implement Ministry hero size and provenance audit helpers against the existing optimized WebP asset (`scripts/lib/hermes-media-audit.ts`) * [x] T009 \[S4010] \[P] Create the browser-safe Hermes provider asset registry with alias normalization, product labels, alt text, and explicit fallbacks (`src/lib/hermes-provider-assets.ts`) *** ## Implementation (6 tasks) * [x] T010 \[S4010] Map Phase 40 Hermes provider aliases to approved logo assets, including OAuth/upstream aliases and uncovered-provider null fallbacks (`src/lib/hermes-provider-assets.ts`) * [x] T011 \[S4010] Add Ministry hero metadata export with descriptive alt text and browser-safe source notes (`src/lib/hermes-provider-assets.ts`) * [x] T012 \[S4010] \[P] Add script-side media audit tests for inventory, rehomed paths, root cleanup, and duplicate decisions (`scripts/lib/__tests__/hermes-media-audit.test.ts`) * [x] T013 \[S4010] \[P] Add script-side media audit tests for forbidden SVG tokens, logo manual-review caps, and Ministry hero cap (`scripts/lib/__tests__/hermes-media-audit.test.ts`) * [x] T014 \[S4010] \[P] Add browser asset registry tests for provider alias lookup, fallback behavior, labels, alt text, and Ministry hero metadata (`src/lib/__tests__/hermes-provider-assets.test.ts`) * [x] T015 \[S4010] Write asset provenance notes with source-path gap audit, final path decisions, duplicate comparisons, hero compression details, and validation evidence (`.spec_system/specs/phase40-session10-assets-and-media-compliance/asset-provenance.md`) *** ## Testing (5 tasks) * [x] T016 \[S4010] Run focused Vitest coverage for media audit and provider asset registry behavior (`bunx vitest run scripts/lib/__tests__/hermes-media-audit.test.ts src/lib/__tests__/hermes-provider-assets.test.ts`) * [x] T017 \[S4010] Run the repository asset-size validation script and record the result (`bash scripts/check-asset-sizes.sh`) * [x] T018 \[S4010] Run app and script type checks for new asset registry and media audit owners (`bun run typecheck && bun run typecheck:scripts`) * [x] T019 \[S4010] Run lint plus ASCII, LF, and whitespace checks over changed source, tests, assets, and session artifacts (`bun run lint`) * [x] T020 \[S4010] Complete final asset verification for root-logo references, browser-safe metadata, no new debug UI copy, and provenance completeness (`verification-scenarios`) *** ## 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 `creview` 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase40-session10-assets-and-media-compliance/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.