Prepare project for pipeline takeover: task tracker, UX doc, CLAUDE.md pointers

Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with
statuses.md as the new status source of truth) and docs/ux-design.md
(retrospective design-system reference), and points CLAUDE.md at them.
docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy
docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as
historical/traceability records, superseded but not deleted.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

docs/tasks/9-1.md

@@ -0,0 +1,27 @@
+---
+id: 9-1
+title: 9-1 Color System Implementation
+status: QA Review
+date: 2026-09-27
+parent: 9
+---
+
+## Description
+
+As a developer, I want to implement the complete color palette as Tailwind CSS theme, So that brand colors are consistently applied throughout the application. The file resources/css/app.css already exists with: - Tailwind and Flux CSS imports (PRESERVE these) - Zinc color palette (can be REMOVED - not used in brand) - Accent color variables using neutral-800 (REPLACE with brand colors) - Flux field/label/control selectors (PRESERVE these). Full implementation history: docs/stories/story-9.1-color-system-implementation.md
+
+## Acceptance Criteria
+
+- [ ] Dark Navy Blue: #0A1F44 (backgrounds, headers)
+- [ ] Gold/Brass: #D4AF37 (accents, buttons, links)
+- [ ] Light Gold: #F4E4B8 (hover states)
+- [ ] Off-White/Cream: #F9F7F4 (text, cards)
+- [ ] Charcoal Gray: #2C3E50 (secondary text)
+- [ ] Success Green: #27AE60 (approved status)
+- [ ] Warning Red: #E74C3C (rejected, errors)
+- [ ] Pending Yellow: #F39C12 (pending status)
+- [ ] Custom Tailwind colors configured via @theme
+- [ ] Color variables for easy maintenance
+- [ ] Semantic color aliases (primary, accent, etc.)
+- [ ] Dark mode is **deferred** to a future story
+- [ ] Document that dark mode will require additional color mappings later