> 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/archive/sessions/phase02-session05-battlefield-asset-and-public-demo-parity/tasks.md).

# Task Checklist

**Session ID**: `phase02-session05-battlefield-asset-and-public-demo-parity` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-05-29

***

## 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     | 4      | 4      | 0         |
| Implementation | 10     | 10     | 0         |
| Testing        | 3      | 3      | 0         |
| **Total**      | **20** | **20** | **0**     |

***

## Setup (3 tasks)

Initial verification and baseline evidence capture.

* [x] T001 \[S0205] Verify Session 04 prerequisites, current app/demo asset inventory, documented byte budget, and public demo standalone constraints (`.spec_system/PRD/phase_02/session_05_battlefield_asset_and_public_demo_parity.md`)
* [x] T002 \[S0205] Create implementation notes with baseline commands, asset measurements, service worker cache state, decisions, and open-risk log (`.spec_system/specs/phase02-session05-battlefield-asset-and-public-demo-parity/implementation-notes.md`)
* [x] T003 \[S0205] Audit current battlefield, media provenance, public demo, and code-sharing docs before edits (`docs/battlefield.md`, `docs/media-assets.md`, `docs/public-demo-code-sharing.md`)

***

## Foundation (4 tasks)

Deterministic parity checks and browser guard support.

* [x] T004 \[S0205] \[P] Create battlefield asset parity checker with schema-validated asset manifest, bounded byte-budget checks, workspace-import exclusion checks, service worker precache checks, and explicit error mapping (`scripts/check-battlefield-assets.mjs`)
* [x] T005 \[S0205] Add a root command for the battlefield asset parity checker (`package.json`)
* [x] T006 \[S0205] Document the battlefield asset parity checker and expected repository-root usage (`scripts/README_scripts.md`)
* [x] T007 \[S0205] Strengthen browser guard helpers for public demo asset request failures and offline reload diagnostics with explicit error reporting (`tests/e2e/support/browserGuards.ts`)

***

## Implementation (10 tasks)

Main asset, public demo, service worker, and documentation parity work.

* [x] T008 \[S0205] Align public demo battlefield token state badges, selected labels, and accessible names with platform-appropriate accessibility labels, focus management, and input support (`public-demo/index.html`)
* [x] T009 \[S0205] Add public demo background and hero fallback state treatment with explicit loading, empty, error, and offline states (`public-demo/index.html`)
* [x] T010 \[S0205] Add public demo empty-board clear behavior with state reset or revalidation on re-entry (`public-demo/index.html`)
* [x] T011 \[S0205] Align public demo coordinate mapping, hero filtering, and dismissed-state treatment with bounded positioning and deterministic ordering (`public-demo/index.html`)
* [x] T012 \[S0205] Replace stale or overclaiming demo copy with synthetic-data, no-local-server, no-LLM-endpoint, no-plan-workpad, and no-War-Room-federation limitation copy (`public-demo/index.html`)
* [x] T013 \[S0205] Verify or update public demo service worker precache paths and cache version when shell asset entries change (`public-demo/sw.js`)
* [x] T014 \[S0205] Update public demo README with current battlefield parity, synthetic data, audio, service worker, and limitation behavior (`public-demo/README_public-demo.md`)
* [x] T015 \[S0205] Update public demo validation docs with asset parity command, desktop/mobile checks, failed-request checks, and offline reload steps (`public-demo/docs_public-demo/validation.md`)
* [x] T016 \[S0205] Update public demo maintenance docs with app/demo parity triggers, service worker cache rules, and no-import boundaries (`public-demo/docs_public-demo/maintenance.md`)
* [x] T017 \[S0205] Update stable battlefield, media asset, and public-demo sharing docs with current parity validation results and asset provenance caveats (`docs/battlefield.md`, `docs/media-assets.md`, `docs/public-demo-code-sharing.md`)

***

## Testing (3 tasks)

Focused verification and quality gates.

* [x] T018 \[S0205] \[P] Extend public demo Playwright coverage for asset loading, state labels, selection reset, limitation copy, failed-request guards, and offline reload (`tests/e2e/public-demo.e2e.ts`)
* [x] T019 \[S0205] \[P] Extend app Playwright coverage for battlefield asset loading and visible state expectations used by parity validation (`tests/e2e/app.e2e.ts`)
* [x] T020 \[S0205] Run battlefield asset parity check, focused public demo/app Playwright checks, focused Biome checks, `git diff --check`, ASCII validation, LF validation, and record results (`.spec_system/specs/phase02-session05-battlefield-asset-and-public-demo-parity/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] Ready for the validate workflow step

***

## Next Steps

Run the implement workflow step to begin AI-led implementation.


---

# 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/archive/sessions/phase02-session05-battlefield-asset-and-public-demo-parity/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.