chore: archive v1.2 Collection Power-Ups milestone
Archive roadmap and requirements to milestones/, evolve PROJECT.md with validated requirements, update retrospective, and reorganize ROADMAP.md with milestone groupings. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,23 @@
|
||||
# Milestones
|
||||
|
||||
## v1.2 Collection Power-Ups (Shipped: 2026-03-16)
|
||||
|
||||
**Phases completed:** 3 phases, 6 plans, 11 tasks
|
||||
**Timeline:** 3 days (2026-03-14 → 2026-03-16)
|
||||
**Codebase:** 7,310 LOC TypeScript, 66 files changed (+7,243 / -206)
|
||||
|
||||
**Key accomplishments:**
|
||||
- Weight unit conversion (g/oz/lb/kg) with segmented toggle wired across all 8 display call sites
|
||||
- Candidate status tracking (researching/ordered/arrived) with clickable StatusBadge popup
|
||||
- Sticky search/filter toolbar with text search and icon-aware CategoryFilterDropdown
|
||||
- Per-setup item classification (base/worn/consumable) with click-to-cycle badge
|
||||
- Recharts donut chart with category/classification toggle, hover tooltips, and weight subtotals
|
||||
- Classification-preserving sync that maintains metadata across atomic setup re-sync
|
||||
|
||||
**Archive:** `.planning/milestones/v1.2-ROADMAP.md`, `.planning/milestones/v1.2-REQUIREMENTS.md`
|
||||
|
||||
---
|
||||
|
||||
## v1.1 Fixes & Polish (Shipped: 2026-03-15)
|
||||
|
||||
**Phases completed:** 3 phases, 7 plans
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## What This Is
|
||||
|
||||
A web-based gear management and purchase planning app. Users catalog their gear collections (bikepacking, sim racing, or any hobby), track weight, price, and source details, and use planning threads to research and compare new purchases. Named setups let users compose loadouts from their collection with live weight/cost totals. Built as a single-user app with a clean, minimalist interface.
|
||||
A web-based gear management and purchase planning app. Users catalog their gear collections (bikepacking, sim racing, or any hobby), track weight, price, and source details, search and filter by name or category, and use planning threads to research and compare new purchases with status tracking. Named setups let users compose loadouts with weight classification (base/worn/consumable), donut chart visualization, and live totals in selectable units. Built as a single-user app with a clean, minimalist interface.
|
||||
|
||||
## Core Value
|
||||
|
||||
@@ -27,18 +27,22 @@ Make it effortless to manage gear and plan new purchases — see how a potential
|
||||
- ✓ Hero image upload area with preview and click-to-upload — v1.1
|
||||
- ✓ Lucide icon picker for categories (119 curated icons, 8 groups) — v1.1
|
||||
- ✓ Automatic emoji-to-Lucide icon migration for existing categories — v1.1
|
||||
- ✓ Search items by name with instant filtering — v1.2
|
||||
- ✓ Filter collection items by category with icon-aware dropdown — v1.2
|
||||
- ✓ Combined text search with category filter and result count — v1.2
|
||||
- ✓ One-action filter clear — v1.2
|
||||
- ✓ Weight unit selection (g, oz, lb, kg) with persistence — v1.2
|
||||
- ✓ All weight displays respect selected unit across entire app — v1.2
|
||||
- ✓ Per-setup item classification (base weight, worn, consumable) — v1.2
|
||||
- ✓ Setup weight subtotals by classification — v1.2
|
||||
- ✓ Donut chart visualization with category/classification toggle — v1.2
|
||||
- ✓ Chart hover tooltips with weight and percentage — v1.2
|
||||
- ✓ Candidate status tracking (researching/ordered/arrived) — v1.2
|
||||
- ✓ Planning category filter with Lucide icons — v1.2
|
||||
|
||||
### Active — v1.2 Collection Power-Ups
|
||||
### Active
|
||||
|
||||
**Goal:** Make core gear management significantly more useful as collections grow — better search, proper weight classification, richer planning threads.
|
||||
|
||||
**Target features:**
|
||||
- Search items by name and filter by category
|
||||
- Classify items as base weight, worn, or consumable per setup
|
||||
- Weight distribution visualization (chart by category/classification)
|
||||
- Candidate status tracking (researching → ordered → arrived)
|
||||
- Weight unit selection (g, oz, lb, kg)
|
||||
- Planning category filter with icon-aware dropdown
|
||||
(No active milestone — use `/gsd:new-milestone` to start next)
|
||||
|
||||
### Future
|
||||
|
||||
@@ -61,10 +65,11 @@ Make it effortless to manage gear and plan new purchases — see how a potential
|
||||
|
||||
## Context
|
||||
|
||||
Shipped v1.1 with 6,134 LOC TypeScript.
|
||||
Tech stack: React 19, Hono, Drizzle ORM, SQLite, TanStack Router/Query, Tailwind CSS v4, Lucide React, all on Bun.
|
||||
Shipped v1.2 with 7,310 LOC TypeScript.
|
||||
Tech stack: React 19, Hono, Drizzle ORM, SQLite, TanStack Router/Query, Tailwind CSS v4, Lucide React, Recharts, all on Bun.
|
||||
Primary use case is bikepacking gear but data model is hobby-agnostic.
|
||||
Replaces spreadsheet-based gear tracking workflow.
|
||||
121 tests (service-level and route-level integration).
|
||||
|
||||
## Constraints
|
||||
|
||||
@@ -96,6 +101,15 @@ Replaces spreadsheet-based gear tracking workflow.
|
||||
| Hero image area at top of forms | Image-first UX, 4:3 aspect ratio consistent with cards | ✓ Good |
|
||||
| Emoji-to-icon automatic migration | One-time schema rename + data conversion via Drizzle migration | ✓ Good |
|
||||
| ALTER TABLE RENAME COLUMN for SQLite | Simpler than table recreation for column rename | ✓ Good |
|
||||
| Weight conversion precision: g=0dp, oz=1dp, lb=2dp, kg=2dp | Matches common usage conventions | ✓ Good |
|
||||
| Unit toggle in TotalsBar (not settings page) | Visible, quick access for frequent switching | ✓ Good |
|
||||
| CategoryFilterDropdown separate from CategoryPicker | Filter vs form concerns are different | ✓ Good |
|
||||
| No debounce on search input | Collection under 1000 items, instant feedback | ✓ Good |
|
||||
| StatusBadge popup with click-outside dismiss | Consistent with CategoryPicker pattern | ✓ Good |
|
||||
| Classification on setupItems join table | Same item can have different roles per setup | ✓ Good |
|
||||
| Click-to-cycle for ClassificationBadge | Only 3 values, simpler than popup | ✓ Good |
|
||||
| Classification-preserving sync via Map | Save metadata before delete, restore after re-insert | ✓ Good |
|
||||
| Recharts for charting | Mature React chart library, composable API | ✓ Good |
|
||||
|
||||
---
|
||||
*Last updated: 2026-03-16 after v1.2 milestone start*
|
||||
*Last updated: 2026-03-16 after v1.2 milestone*
|
||||
|
||||
@@ -91,6 +91,51 @@
|
||||
|
||||
---
|
||||
|
||||
## Milestone: v1.2 — Collection Power-Ups
|
||||
|
||||
**Shipped:** 2026-03-16
|
||||
**Phases:** 3 | **Plans:** 6 | **Files changed:** 66
|
||||
|
||||
### What Was Built
|
||||
- Weight unit conversion (g/oz/lb/kg) with segmented toggle wired across all weight display call sites
|
||||
- Candidate status tracking (researching/ordered/arrived) with clickable StatusBadge popup
|
||||
- Sticky search/filter toolbar with text search and icon-aware CategoryFilterDropdown
|
||||
- Per-setup item classification (base/worn/consumable) with click-to-cycle ClassificationBadge
|
||||
- Recharts donut chart with category/classification toggle and hover tooltips
|
||||
- Classification-preserving sync that maintains metadata across atomic setup item re-sync
|
||||
|
||||
### What Worked
|
||||
- Coarse 3-phase structure again — 19 requirements compressed into 3 phases with clear dependency ordering
|
||||
- TDD red/green commits for schema migrations (status, classification) caught edge cases early
|
||||
- Vertical slice pattern (schema → service → tests → API → UI in one plan) kept each deliverable self-contained
|
||||
- Click-outside dismiss pattern established in v1.1 was reused cleanly in StatusBadge and CategoryFilterDropdown
|
||||
- All 6 plans executed with zero deviations from plan — evidence of mature planning process
|
||||
|
||||
### What Was Inefficient
|
||||
- Some ROADMAP.md plan checkboxes remained unchecked despite summaries existing (persistent cosmetic drift)
|
||||
- Recharts v3 Cell component is deprecated for v4 — will need migration eventually
|
||||
- Phase 8 bundled search/filter with candidate status (different concerns) — could have been separate phases for cleaner scope
|
||||
|
||||
### Patterns Established
|
||||
- Click-to-cycle badge: for small enums (3 values), direct click cycling is simpler than popup menus
|
||||
- Join table metadata preservation: save metadata to Map before atomic sync, restore after re-insert
|
||||
- CategoryFilterDropdown: reusable filter dropdown (separate from form-based CategoryPicker)
|
||||
- Chart data transformation: group items by key, sum weights, compute percentages, filter zeroes
|
||||
- apiPatch helper: PATCH method now available in client API library for partial updates
|
||||
|
||||
### Key Lessons
|
||||
1. Classification belongs on join tables (setupItems), not entity tables (items) — same item has different roles in different contexts
|
||||
2. Vertical slice delivery (schema → service → test → API → UI) is the optimal plan structure for feature additions
|
||||
3. Search complexity should match data scale — no debounce needed for <1000 items
|
||||
4. Recharts composable API (PieChart + Pie + Cell + Tooltip + Label) gives fine-grained chart control with minimal wrapper code
|
||||
|
||||
### Cost Observations
|
||||
- Model mix: quality profile throughout (opus for execution)
|
||||
- Sessions: 3 continuous auto-advance sessions (one per phase)
|
||||
- Notable: All plans completed with zero deviations, execution faster than v1.0/v1.1
|
||||
|
||||
---
|
||||
|
||||
## Cross-Milestone Trends
|
||||
|
||||
### Process Evolution
|
||||
@@ -99,6 +144,7 @@
|
||||
|-----------|---------|--------|------------|
|
||||
| v1.0 | 53 | 3 | Initial build, coarse granularity, TDD backend |
|
||||
| v1.1 | ~30 | 3 | Auto-advance pipeline, parallel wave execution, auto-fix deviations |
|
||||
| v1.2 | 25 | 3 | Zero-deviation execution, vertical slice pattern, join table metadata |
|
||||
|
||||
### Cumulative Quality
|
||||
|
||||
@@ -106,6 +152,7 @@
|
||||
|-----------|-----|-------|-------|
|
||||
| v1.0 | 5,742 | 114 | Service + route integration |
|
||||
| v1.1 | 6,134 | ~130 | Service + route integration (updated for icon schema) |
|
||||
| v1.2 | 7,310 | ~150 | 121 tests (service + route + classification) |
|
||||
|
||||
### Top Lessons (Verified Across Milestones)
|
||||
|
||||
@@ -113,3 +160,5 @@
|
||||
2. Service DI pattern enables fast, reliable testing without mocks
|
||||
3. Always update Zod schemas alongside DB schema — middleware silently strips unvalidated fields
|
||||
4. Auto-advance pipeline (discuss → plan → execute) works well for clear-scope phases
|
||||
5. Vertical slice delivery (schema → service → test → API → UI) is optimal for feature additions
|
||||
6. Join table metadata (not entity table) when same entity plays different roles in different contexts
|
||||
|
||||
@@ -2,89 +2,41 @@
|
||||
|
||||
## Milestones
|
||||
|
||||
- v1.0 MVP -- Phases 1-3 (shipped 2026-03-15)
|
||||
- v1.1 Fixes & Polish -- Phases 4-6 (shipped 2026-03-15)
|
||||
- **v1.2 Collection Power-Ups** -- Phases 7-9 (in progress)
|
||||
- ✅ **v1.0 MVP** — Phases 1-3 (shipped 2026-03-15)
|
||||
- ✅ **v1.1 Fixes & Polish** — Phases 4-6 (shipped 2026-03-15)
|
||||
- ✅ **v1.2 Collection Power-Ups** — Phases 7-9 (shipped 2026-03-16)
|
||||
|
||||
## Phases
|
||||
|
||||
<details>
|
||||
<summary>v1.0 MVP (Phases 1-3) -- SHIPPED 2026-03-15</summary>
|
||||
<summary>✅ v1.0 MVP (Phases 1-3) — SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 1: Foundation and Collection (4/4 plans) -- completed 2026-03-14
|
||||
- [x] Phase 2: Planning Threads (3/3 plans) -- completed 2026-03-15
|
||||
- [x] Phase 3: Setups and Dashboard (3/3 plans) -- completed 2026-03-15
|
||||
- [x] Phase 1: Foundation and Collection (4/4 plans) — completed 2026-03-14
|
||||
- [x] Phase 2: Planning Threads (3/3 plans) — completed 2026-03-15
|
||||
- [x] Phase 3: Setups and Dashboard (3/3 plans) — completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>v1.1 Fixes & Polish (Phases 4-6) -- SHIPPED 2026-03-15</summary>
|
||||
<summary>✅ v1.1 Fixes & Polish (Phases 4-6) — SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 4: Database & Planning Fixes (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 5: Image Handling (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 6: Category Icons (3/3 plans) -- completed 2026-03-15
|
||||
- [x] Phase 4: Database & Planning Fixes (2/2 plans) — completed 2026-03-15
|
||||
- [x] Phase 5: Image Handling (2/2 plans) — completed 2026-03-15
|
||||
- [x] Phase 6: Category Icons (3/3 plans) — completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
### v1.2 Collection Power-Ups (In Progress)
|
||||
<details>
|
||||
<summary>✅ v1.2 Collection Power-Ups (Phases 7-9) — SHIPPED 2026-03-16</summary>
|
||||
|
||||
**Milestone Goal:** Make core gear management significantly more useful as collections grow -- better search, proper weight classification, richer planning threads.
|
||||
- [x] Phase 7: Weight Unit Selection (2/2 plans) — completed 2026-03-16
|
||||
- [x] Phase 8: Search, Filter, and Candidate Status (2/2 plans) — completed 2026-03-16
|
||||
- [x] Phase 9: Weight Classification and Visualization (2/2 plans) — completed 2026-03-16
|
||||
|
||||
- [x] **Phase 7: Weight Unit Selection** - Users see all weights in their preferred unit across the entire app
|
||||
- [x] **Phase 8: Search, Filter, and Candidate Status** - Users can find items quickly and track candidate purchase progress
|
||||
- [x] **Phase 9: Weight Classification and Visualization** - Users can classify gear by role and visualize weight distribution in setups
|
||||
|
||||
## Phase Details
|
||||
|
||||
### Phase 7: Weight Unit Selection
|
||||
**Goal**: Users see all weights in their preferred unit across the entire app
|
||||
**Depends on**: Nothing (first phase of v1.2)
|
||||
**Requirements**: UNIT-01, UNIT-02, UNIT-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can select a weight unit (g, oz, lb, kg) from a visible control and the selection persists after closing and reopening the app
|
||||
2. Every weight value in the app (item cards, candidate cards, category headers, totals bar, setup details) displays in the selected unit with appropriate precision
|
||||
3. Weight input fields accept values and store them correctly regardless of display unit (no rounding drift across edit cycles)
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [x] 07-01-PLAN.md -- TDD formatWeight unit conversion core + useWeightUnit hook
|
||||
- [ ] 07-02-PLAN.md -- Wire unit toggle into TotalsBar and update all 8 call sites
|
||||
|
||||
### Phase 8: Search, Filter, and Candidate Status
|
||||
**Goal**: Users can find items quickly and track candidate purchase progress
|
||||
**Depends on**: Phase 7
|
||||
**Requirements**: SRCH-01, SRCH-02, SRCH-03, SRCH-04, SRCH-05, PLAN-01, CAND-01, CAND-02, CAND-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can type in a search field on the collection page and see items filtered instantly by name as they type
|
||||
2. User can select a category from a dropdown (showing Lucide icons alongside names) to filter items in both collection and planning views
|
||||
3. User can see how many items match active filters (e.g., "showing 12 of 47 items") and clear all filters with one action
|
||||
4. Each candidate in a planning thread displays a status badge (researching, ordered, or arrived) that the user can change by clicking
|
||||
5. New candidates automatically start with "researching" status
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 08-01-PLAN.md -- Candidate status vertical slice (schema migration, service, tests, StatusBadge UI)
|
||||
- [ ] 08-02-PLAN.md -- Search/filter toolbar with CategoryFilterDropdown on gear and planning tabs
|
||||
|
||||
### Phase 9: Weight Classification and Visualization
|
||||
**Goal**: Users can classify gear by role and visualize weight distribution in setups
|
||||
**Depends on**: Phase 7, Phase 8
|
||||
**Requirements**: CLAS-01, CLAS-02, CLAS-03, CLAS-04, VIZZ-01, VIZZ-02, VIZZ-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can classify each item within a setup as base weight, worn, or consumable, and the same item can have different classifications in different setups
|
||||
2. Setup detail view shows separate weight subtotals for base weight, worn weight, and consumable weight in addition to the overall total
|
||||
3. User can view a donut chart in a setup showing weight distribution, and toggle between category breakdown and classification breakdown
|
||||
4. User can hover chart segments to see the category/classification name, weight (in selected unit), and percentage
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 09-01-PLAN.md -- Classification vertical slice (schema, service, tests, API route, ClassificationBadge UI)
|
||||
- [ ] 09-02-PLAN.md -- WeightSummaryCard with subtotals, donut chart, pill toggle, and visual verification
|
||||
</details>
|
||||
|
||||
## Progress
|
||||
|
||||
**Execution Order:** Phase 7 -> Phase 8 -> Phase 9
|
||||
|
||||
| Phase | Milestone | Plans Complete | Status | Completed |
|
||||
|-------|-----------|----------------|--------|-----------|
|
||||
| 1. Foundation and Collection | v1.0 | 4/4 | Complete | 2026-03-14 |
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
gsd_state_version: 1.0
|
||||
milestone: v1.2
|
||||
milestone_name: Collection Power-Ups
|
||||
status: completed
|
||||
stopped_at: Completed 09-02-PLAN.md
|
||||
last_updated: "2026-03-16T14:29:36.577Z"
|
||||
last_activity: 2026-03-16 -- Completed 09-02 weight breakdown visualization
|
||||
status: archived
|
||||
stopped_at: Milestone v1.2 archived
|
||||
last_updated: "2026-03-16T18:30:00.000Z"
|
||||
last_activity: 2026-03-16 -- Milestone v1.2 archived
|
||||
progress:
|
||||
total_phases: 3
|
||||
completed_phases: 3
|
||||
@@ -21,16 +21,13 @@ progress:
|
||||
See: .planning/PROJECT.md (updated 2026-03-16)
|
||||
|
||||
**Core value:** Make it effortless to manage gear and plan new purchases -- see how a potential buy affects your total setup weight and cost before committing.
|
||||
**Current focus:** Milestone v1.2 complete -- all phases finished
|
||||
**Current focus:** Planning next milestone
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: 9 of 9 (Weight Classification & Visualization)
|
||||
Plan: 2 of 2
|
||||
Status: Complete
|
||||
Last activity: 2026-03-16 -- Completed 09-02 weight breakdown visualization
|
||||
|
||||
Progress: [██████████] 100%
|
||||
Milestone v1.2 Collection Power-Ups archived.
|
||||
All 3 milestones shipped (v1.0, v1.1, v1.2).
|
||||
Next step: `/gsd:new-milestone` to start next milestone.
|
||||
|
||||
## Accumulated Context
|
||||
|
||||
@@ -38,23 +35,7 @@ Progress: [██████████] 100%
|
||||
|
||||
(Full decision log in PROJECT.md Key Decisions table)
|
||||
|
||||
- Coarse granularity: 19 requirements compressed into 3 phases (7-9)
|
||||
- Weight unit selection must be Phase 7 (formatWeight refactor touches all weight displays)
|
||||
- Classification belongs on setup_items join table, NOT items table
|
||||
- Candidate status and classification schema migrations in separate phases (sequential)
|
||||
- Weight conversion precision: g=0dp, oz=1dp, lb=2dp, kg=2dp
|
||||
- useWeightUnit validates stored value against known units to protect against corrupt data
|
||||
- Unit toggle placed between title and stats in TotalsBar for subtle utility placement
|
||||
- CategoryFilterDropdown kept separate from CategoryPicker (filter vs form concerns)
|
||||
- No debounce on search input (collection under 1000 items)
|
||||
- Individual clear controls for search and category filter (no combined clear-all)
|
||||
- [Phase 08]: CategoryFilterDropdown kept separate from CategoryPicker (filter vs form concerns)
|
||||
- [Phase 08]: StatusBadge popup uses click-outside + Escape dismiss pattern matching CategoryPicker
|
||||
- [Phase 08]: Status badge uses muted gray tones (bg-gray-100 text-gray-600) per user design decision
|
||||
- [Phase 09]: ClassificationBadge uses simple click-to-cycle (not popup) since only 3 values
|
||||
- [Phase 09]: Classification stored on setupItems join table so same item can differ across setups
|
||||
- [Phase 09]: syncSetupItems preserves classifications via Map before delete/restore after re-insert
|
||||
- [Phase 09]: Recharts v3 Cell component used for per-slice colors (still functional, deprecated for v4)
|
||||
Cleared at milestone boundary. v1.2 decisions archived in milestones/v1.2-ROADMAP.md.
|
||||
|
||||
### Pending Todos
|
||||
|
||||
@@ -66,6 +47,6 @@ None active.
|
||||
|
||||
## Session Continuity
|
||||
|
||||
Last session: 2026-03-16T14:22:28.169Z
|
||||
Stopped at: Completed 09-02-PLAN.md
|
||||
Last session: 2026-03-16
|
||||
Stopped at: Milestone v1.2 archived
|
||||
Resume file: None
|
||||
|
||||
@@ -1,3 +1,12 @@
|
||||
# Requirements Archive: v1.2 Collection Power-Ups
|
||||
|
||||
**Archived:** 2026-03-16
|
||||
**Status:** SHIPPED
|
||||
|
||||
For current requirements, see `.planning/REQUIREMENTS.md`.
|
||||
|
||||
---
|
||||
|
||||
# Requirements: GearBox v1.2 Collection Power-Ups
|
||||
|
||||
**Defined:** 2026-03-16
|
||||
98
.planning/milestones/v1.2-ROADMAP.md
Normal file
98
.planning/milestones/v1.2-ROADMAP.md
Normal file
@@ -0,0 +1,98 @@
|
||||
# Roadmap: GearBox
|
||||
|
||||
## Milestones
|
||||
|
||||
- v1.0 MVP -- Phases 1-3 (shipped 2026-03-15)
|
||||
- v1.1 Fixes & Polish -- Phases 4-6 (shipped 2026-03-15)
|
||||
- **v1.2 Collection Power-Ups** -- Phases 7-9 (in progress)
|
||||
|
||||
## Phases
|
||||
|
||||
<details>
|
||||
<summary>v1.0 MVP (Phases 1-3) -- SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 1: Foundation and Collection (4/4 plans) -- completed 2026-03-14
|
||||
- [x] Phase 2: Planning Threads (3/3 plans) -- completed 2026-03-15
|
||||
- [x] Phase 3: Setups and Dashboard (3/3 plans) -- completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary>v1.1 Fixes & Polish (Phases 4-6) -- SHIPPED 2026-03-15</summary>
|
||||
|
||||
- [x] Phase 4: Database & Planning Fixes (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 5: Image Handling (2/2 plans) -- completed 2026-03-15
|
||||
- [x] Phase 6: Category Icons (3/3 plans) -- completed 2026-03-15
|
||||
|
||||
</details>
|
||||
|
||||
### v1.2 Collection Power-Ups (In Progress)
|
||||
|
||||
**Milestone Goal:** Make core gear management significantly more useful as collections grow -- better search, proper weight classification, richer planning threads.
|
||||
|
||||
- [x] **Phase 7: Weight Unit Selection** - Users see all weights in their preferred unit across the entire app
|
||||
- [x] **Phase 8: Search, Filter, and Candidate Status** - Users can find items quickly and track candidate purchase progress
|
||||
- [x] **Phase 9: Weight Classification and Visualization** - Users can classify gear by role and visualize weight distribution in setups
|
||||
|
||||
## Phase Details
|
||||
|
||||
### Phase 7: Weight Unit Selection
|
||||
**Goal**: Users see all weights in their preferred unit across the entire app
|
||||
**Depends on**: Nothing (first phase of v1.2)
|
||||
**Requirements**: UNIT-01, UNIT-02, UNIT-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can select a weight unit (g, oz, lb, kg) from a visible control and the selection persists after closing and reopening the app
|
||||
2. Every weight value in the app (item cards, candidate cards, category headers, totals bar, setup details) displays in the selected unit with appropriate precision
|
||||
3. Weight input fields accept values and store them correctly regardless of display unit (no rounding drift across edit cycles)
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [x] 07-01-PLAN.md -- TDD formatWeight unit conversion core + useWeightUnit hook
|
||||
- [ ] 07-02-PLAN.md -- Wire unit toggle into TotalsBar and update all 8 call sites
|
||||
|
||||
### Phase 8: Search, Filter, and Candidate Status
|
||||
**Goal**: Users can find items quickly and track candidate purchase progress
|
||||
**Depends on**: Phase 7
|
||||
**Requirements**: SRCH-01, SRCH-02, SRCH-03, SRCH-04, SRCH-05, PLAN-01, CAND-01, CAND-02, CAND-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can type in a search field on the collection page and see items filtered instantly by name as they type
|
||||
2. User can select a category from a dropdown (showing Lucide icons alongside names) to filter items in both collection and planning views
|
||||
3. User can see how many items match active filters (e.g., "showing 12 of 47 items") and clear all filters with one action
|
||||
4. Each candidate in a planning thread displays a status badge (researching, ordered, or arrived) that the user can change by clicking
|
||||
5. New candidates automatically start with "researching" status
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 08-01-PLAN.md -- Candidate status vertical slice (schema migration, service, tests, StatusBadge UI)
|
||||
- [ ] 08-02-PLAN.md -- Search/filter toolbar with CategoryFilterDropdown on gear and planning tabs
|
||||
|
||||
### Phase 9: Weight Classification and Visualization
|
||||
**Goal**: Users can classify gear by role and visualize weight distribution in setups
|
||||
**Depends on**: Phase 7, Phase 8
|
||||
**Requirements**: CLAS-01, CLAS-02, CLAS-03, CLAS-04, VIZZ-01, VIZZ-02, VIZZ-03
|
||||
**Success Criteria** (what must be TRUE):
|
||||
1. User can classify each item within a setup as base weight, worn, or consumable, and the same item can have different classifications in different setups
|
||||
2. Setup detail view shows separate weight subtotals for base weight, worn weight, and consumable weight in addition to the overall total
|
||||
3. User can view a donut chart in a setup showing weight distribution, and toggle between category breakdown and classification breakdown
|
||||
4. User can hover chart segments to see the category/classification name, weight (in selected unit), and percentage
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 09-01-PLAN.md -- Classification vertical slice (schema, service, tests, API route, ClassificationBadge UI)
|
||||
- [ ] 09-02-PLAN.md -- WeightSummaryCard with subtotals, donut chart, pill toggle, and visual verification
|
||||
|
||||
## Progress
|
||||
|
||||
**Execution Order:** Phase 7 -> Phase 8 -> Phase 9
|
||||
|
||||
| Phase | Milestone | Plans Complete | Status | Completed |
|
||||
|-------|-----------|----------------|--------|-----------|
|
||||
| 1. Foundation and Collection | v1.0 | 4/4 | Complete | 2026-03-14 |
|
||||
| 2. Planning Threads | v1.0 | 3/3 | Complete | 2026-03-15 |
|
||||
| 3. Setups and Dashboard | v1.0 | 3/3 | Complete | 2026-03-15 |
|
||||
| 4. Database & Planning Fixes | v1.1 | 2/2 | Complete | 2026-03-15 |
|
||||
| 5. Image Handling | v1.1 | 2/2 | Complete | 2026-03-15 |
|
||||
| 6. Category Icons | v1.1 | 3/3 | Complete | 2026-03-15 |
|
||||
| 7. Weight Unit Selection | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
| 8. Search, Filter, and Candidate Status | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
| 9. Weight Classification and Visualization | v1.2 | 2/2 | Complete | 2026-03-16 |
|
||||
Reference in New Issue
Block a user