Release: EPIC-03 Work Items & EPIC-12 Design System Bootstrap

[steilerDev]

Summary

Promotes beta to main containing two completed epics:

EPIC-03: Work Items Core CRUD & Properties (#3)

All 8 stories completed — full work item management with CRUD, status tracking, tag assignment, dependencies, and detail views.

EPIC-12: Design System Bootstrap (#115)

Story	PR	Description
12.1 (#116)	#121	Design Token System — 3-layer CSS custom properties
12.2 (#117)	#122	Brand Identity — Logo component and SVG favicon
12.3 (#118)	#123	CSS Module Migration — ~476 hardcoded colors → tokens
12.4 (#119)	#124	Dark Mode — Light/Dark/System toggle with persistence
12.5 (#120)	#125	Style Guide Documentation — Wiki page and README
Refinement	#126	Semantic token fixes, dark palette Layer 1, ThemeContext cleanup

---

UAT Validation: EPIC-12 Design System

Scenario 1: Design Tokens

• Open DevTools → Elements → html → verify CSS custom properties on :root

Scenario 2: Zero Hardcoded Colors

• grep -rn '#[0-9a-fA-F]' client/src/**/*.module.css returns zero results

Scenario 3: Logo and Favicon

• Cornerstone logo (keystone/arch) visible at top of sidebar
• Favicon visible in browser tab

Scenario 4: Light Mode

• App displays with white/light backgrounds, dark text, visible buttons/badges

Scenario 5: Dark Mode Toggle

• Sidebar click theme toggle: cycles Light, Dark, System
• Dark mode: dark navy backgrounds, light text, all elements readable
• Status/role badges distinguishable in dark mode

Scenario 6: Theme Persistence

• Set to Dark, refresh page, still Dark

Scenario 7: System Preference

• Set to System, follows OS dark/light mode

Scenario 8: Login Page

• Dark mode applies to /login page

Scenario 9: Quality Gates

• All tests pass, lint clean, typecheck clean, build succeeds

Test plan

• All unit/integration tests pass (1072 tests across 53 suites)
• CI green on all PRs
• Security reviews completed
• Code reviews completed (product-architect, security-engineer)
• Manual UAT validation per scenarios above

[github-actions]

🎉 This PR is included in version 1.8.0-beta.12 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[steilerDev]

[uat-validator]

EPIC-03 UAT Validation Overview

Summary

Total UAT Scenarios: 462 across 8 stories

Story	Title	Scenarios	Verification
3.1	Work Items Database Schema & Migration	30	Automated
3.2	Work Items CRUD API	44	Automated
3.3	Tag Management API & UI	42	Automated + Manual
3.4	Work Item Notes & Subtasks API	51	Automated
3.5	Work Items List Page	57	Automated + Manual
3.6	Work Item Detail & Edit Page	58	Automated + Manual
3.7	Work Item Dependencies API & UI	41	Automated + Manual
3.8	Keyboard Shortcuts for Work Items	40	Manual

Verification Method Breakdown:

• Automated (Integration Tests): ~303 scenarios
• Both (E2E and Manual): ~111 scenarios
• Manual Only: ~48 scenarios

Automated Test Results

• 947 tests across 44 test suites — all passing
• 95%+ unit test coverage on all new code
• All quality gates pass: lint, typecheck, format:check, build, npm audit

Manual Validation Steps

The following manual validation walkthrough covers the key user-facing scenarios. Start the application and log in as an admin user.

Prerequisites

1. Start the application: docker compose up -d or npm run dev
2. Log in as admin user
3. Ensure at least one other user exists for assignment testing

Walkthrough

Detailed UAT scenarios for each story are posted in the comments below.

[steilerDev]

[uat-validator]

Stories 3.1 & 3.2 — Database Schema & CRUD API

Story 3.1 — Work Items Database Schema & Migration (#87)

All 30 scenarios are automated via integration tests.

Manual Verification Steps

1. Run npm run db:migrate on a fresh database
2. Verify no errors in migration output
3. Confirm tables exist: work_items, tags, work_item_tags, work_item_notes, work_item_subtasks, work_item_dependencies

Key Scenarios

• UAT-3.1-01: Migration applies successfully on fresh DB
• UAT-3.1-02: All 6 work item tables created
• UAT-3.1-03 through 3.1-08: Each table has correct columns and types
• UAT-3.1-09: Required indexes exist (status, assigned_user, created_at, etc.)
• UAT-3.1-10 through 3.1-16: Foreign key cascades work correctly (deleting work item cascades to notes/subtasks/tags, deleting user sets assigned_user to NULL)
• UAT-3.1-17 through 3.1-21: CHECK constraints enforce valid status and dependency type values
• UAT-3.1-22 through 3.1-24: Unique constraints on tag names, composite PKs on junction tables
• UAT-3.1-25 through 3.1-27: Shared TypeScript types available (WorkItem, WorkItemStatus, Tag, etc.)
• UAT-3.1-29: Migration is idempotent

---

Story 3.2 — Work Items CRUD API (#88)

All 44 scenarios are automated via integration tests.

Manual Verification Steps (via API or UI)

1. Create: POST /api/work-items with title only → verify 201 with defaults
2. Create with all fields: Include description, status, dates, duration, constraints, assignedUserId, tagIds → verify all values returned
3. List: GET /api/work-items → verify pagination (25 per page default), filtering by status/user/tag, search by title/description, sorting
4. Get: GET /api/work-items/:id → verify complete detail with nested tags, notes, subtasks, dependencies
5. Update: PATCH /api/work-items/:id → verify partial updates work
6. Delete: DELETE /api/work-items/:id → verify cascading deletion of notes, subtasks, tag associations

Key Scenarios

• UAT-3.2-01 through 3.2-02: Create with minimum/all fields
• UAT-3.2-03 through 3.2-10: Validation errors (empty title, invalid status, date constraints, non-existent references)
• UAT-3.2-12 through 3.2-22: List with pagination, filtering (status, user, tag), search, sorting
• UAT-3.2-24 through 3.2-26: Get single item with nested objects, 404 handling
• UAT-3.2-27 through 3.2-33: Partial updates, assignment changes, date validation
• UAT-3.2-34 through 3.2-36: Delete with cascading behavior
• UAT-3.2-40 through 3.2-41: Response format uses camelCase, user summaries exclude sensitive fields
• UAT-3.2-42 through 3.2-44: Edge cases (long descriptions, out-of-range pages, case-insensitive search)

[steilerDev]

[uat-validator]

Stories 3.3 & 3.4 — Tags, Notes & Subtasks

Story 3.3 — Tag Management API & UI (#89)

42 scenarios — automated + manual validation needed for UI.

Manual Validation Steps

1. Navigate to Tags management page (accessible from sidebar or settings)
2. Create a tag: Click "New Tag", enter name "Electrical", pick color #FF5733 → verify tag appears in list
3. Create tag without color: Create tag "Plumbing" with no color → verify default styling
4. Edit tag: Click edit on "Electrical", change name to "Electrical Work" → verify update
5. Delete tag: Delete a tag → verify confirmation dialog, tag removed from list
6. Tag in work item create form: Go to /work-items/new, verify tag picker shows all tags
7. Inline tag creation: In the tag picker, type a new tag name and create it inline → verify it appears immediately
8. Tag display: Create a work item with tags → verify colored pills in list and detail views
9. Duplicate prevention: Try creating a tag with existing name → verify 409 error displayed

Key Scenarios

• UAT-3.3-01 through 3.3-07: Tag CRUD API with validation
• UAT-3.3-08 through 3.3-11: List tags (alphabetical sort, empty state)
• UAT-3.3-12 through 3.3-20: Update and delete with cascading behavior
• UAT-3.3-21 through 3.3-26: Tag management UI (list, create, edit, delete, inline validation)
• UAT-3.3-27 through 3.3-29: Tag display in work items (colored pills, default style)
• UAT-3.3-30 through 3.3-34: Inline tag assignment in work item forms (selection, creation, keyboard accessible)
• UAT-3.3-38 through 3.3-42: Edge cases (delete in-use tag confirmation, name trimming, color validation)

---

Story 3.4 — Work Item Notes & Subtasks API (#90)

All 51 scenarios are automated via integration tests.

Manual Verification Steps (via API)

1. Create note: POST /api/work-items/:id/notes with content → verify 201, createdBy auto-set
2. List notes: GET /api/work-items/:id/notes → verify sorted newest first
3. Update note: Author can update, non-author member gets 403, admin can update any
4. Delete note: Same authorization rules as update
5. Create subtask: POST /api/work-items/:id/subtasks → verify auto sort-order assignment
6. Toggle completion: PATCH subtask with isCompleted: true
7. Reorder subtasks: PATCH /api/work-items/:id/subtasks/reorder with ALL subtask IDs → verify new order
8. Partial reorder rejected: Send subset of IDs → verify 400 error

Key Scenarios

• UAT-3.4-01 through 3.4-06: Note creation with validation and auto-attribution
• UAT-3.4-07 through 3.4-10: Note listing (newest first, empty state)
• UAT-3.4-11 through 3.4-21: Note update/delete with author/admin authorization
• UAT-3.4-22 through 3.4-28: Subtask creation with auto sort-order
• UAT-3.4-29 through 3.4-41: Subtask listing, update, delete
• UAT-3.4-42 through 3.4-46: Reorder requiring ALL subtask IDs (partial reorder rejected)
• UAT-3.4-49 through 3.4-51: Edge cases (deleted user notes, sort order gaps, special characters)

[steilerDev]

[uat-validator]

Stories 3.5 & 3.6 — Frontend List & Detail Pages

Story 3.5 — Work Items List Page (#91)

57 scenarios — automated + manual validation for UI interactions.

Manual Validation Steps

1. Navigate: Click "Work Items" in sidebar → verify /work-items page loads
2. Empty state: If no work items exist, verify friendly empty state with CTA to create
3. Create work item: Click "New Work Item" → verify navigation to /work-items/new
4. List display (desktop): Resize to >1024px → verify table layout with columns: title, status, assigned user, dates, tags
5. List display (mobile): Resize to <1024px → verify card layout
6. Status badges: Verify color coding — gray (not started), yellow (in progress), green (completed), red (blocked)
7. Tags: Verify colored pills displayed on work items
8. Search: Type in search box → verify list filters by title/description, case-insensitive
9. Filter by status: Select status filter → verify only matching items shown
10. Filter by assigned user: Select user filter → verify filtering works
11. Filter by tag: Select tag filter → verify filtering
12. Multiple filters: Combine status + tag filter → verify AND logic
13. Sort: Click column headers → verify ascending/descending toggle
14. Pagination: Create >25 work items → verify pagination controls appear, page navigation works
15. Click work item: Click a row → verify navigation to /work-items/:id
16. Delete from list: Use delete action → verify confirmation dialog, item removed without full page reload
17. Responsive: Test on mobile viewport → verify touch targets ≥44px, no horizontal scroll

Key Scenarios

• UAT-3.5-01 through 3.5-02: Navigation and sidebar link
• UAT-3.5-03 through 3.5-09: List display (table/card layouts, status badges, tags, assigned user)
• UAT-3.5-10 through 3.5-15: Search (title, description, case-insensitive, debounced)
• UAT-3.5-16 through 3.5-24: Filters (status multi-select, user dropdown, tag multi-select, AND logic)
• UAT-3.5-25 through 3.5-28: Sort controls (multiple fields, toggle direction)
• UAT-3.5-29 through 3.5-32: Pagination (controls appear when needed, total count)
• UAT-3.5-33 through 3.5-40: Actions (new, click to detail, delete with confirmation)
• UAT-3.5-41 through 3.5-43: Empty states (no items, no search results)
• UAT-3.5-44 through 3.5-47: Loading and error states
• UAT-3.5-53 through 3.5-57: Responsive design and edge cases

---

Story 3.6 — Work Item Detail, Edit & Create Pages (#92)

58 scenarios — automated + manual validation for UI interactions.

Manual Validation Steps

1. Navigate to detail: Click a work item from list → verify /work-items/:id
2. Title display: Verify title displayed prominently as heading
3. Description: Verify description shown (or "No description" placeholder)
4. Status badge: Verify color-coded status
5. Dates: Verify start/end dates in human-readable format
6. Duration: Verify duration displayed (e.g., "30 days")
7. Constraints: Verify start-after/start-before dates displayed
8. Assigned user: Verify user name shown (or "Unassigned")
9. Tags section: Verify tags as colored pills
10. Add tag: Click to add a tag → verify tag picker, select tag, verify update
11. Create tag inline: In tag picker, create new tag → verify it's added immediately
12. Remove tag: Remove a tag → verify removal
13. Notes section: Verify notes displayed (newest first)
14. Add note: Type and submit a note → verify it appears
15. Edit own note: Click edit on your note → verify inline editing works
16. Delete own note: Delete your note → verify removal
17. Subtasks section: Verify subtasks displayed as checklist
18. Add subtask: Add a new subtask → verify it appears
19. Toggle subtask: Check/uncheck → verify completion state
20. Edit subtask: Edit title inline → verify update
21. Delete subtask: Delete subtask → verify removal
22. Dependencies section: Verify predecessors and successors lists
23. Inline edit title: Click title → edit → save → verify update
24. Inline edit description: Click description → edit → save
25. Change status: Use dropdown to change status → verify update
26. Change assigned user: Update assignment → verify
27. Edit dates: Change dates → verify validation (start < end)
28. Delete work item: Click delete → verify confirmation → verify redirect to list
29. Create page: Navigate to /work-items/new → fill form → submit → verify redirect to detail
30. Validation: Submit with empty title → verify error message
31. 404 handling: Navigate to /work-items/nonexistent → verify error with back link
32. Responsive: Test on mobile → verify single-column layout

Key Scenarios

• UAT-3.6-01 through 3.6-03: Navigation and 404 handling
• UAT-3.6-04 through 3.6-12: Detail view basic properties
• UAT-3.6-13 through 3.6-16: Tag management on detail page
• UAT-3.6-17 through 3.6-24: Notes with author-based authorization
• UAT-3.6-25 through 3.6-30: Subtasks with completion and reordering
• UAT-3.6-31 through 3.6-40: Inline editing for all properties
• UAT-3.6-41 through 3.6-45: Create form with validation
• UAT-3.6-46 through 3.6-49: Delete with confirmation
• UAT-3.6-52 through 3.6-58: Responsive design and edge cases

[steilerDev]

[uat-validator]

Stories 3.7 & 3.8 — Dependencies & Keyboard Shortcuts

Story 3.7 — Work Item Dependencies API & UI (#93)

41 scenarios — automated + manual validation for UI.

Manual Validation Steps

1. View dependencies: Open a work item detail page → verify "Dependencies" section with Predecessors and Successors subsections
2. Empty state: Verify "No predecessors" and "No successors" messages when none exist
3. Add predecessor: Click "Add Predecessor" → search for a work item → select dependency type → submit → verify it appears in predecessors list
4. Add successor: Click "Add Successor" → same workflow → verify in successors list
5. Dependency type display: Verify human-readable labels (e.g., "Finish-to-Start" not "finish_to_start")
6. Click dependency link: Click a predecessor/successor name → verify navigation to that work item
7. Remove dependency: Click remove on a dependency → verify confirmation → verify removal
8. Circular dependency: Try to create A→B→A cycle → verify clear error message "CIRCULAR_DEPENDENCY"
9. Self-reference: Try to add a work item as its own dependency → verify error
10. Duplicate: Try to add same dependency twice → verify 409 error
11. Cascading delete: Delete a work item that has dependencies → verify dependencies cleaned up

Key Scenarios

• UAT-3.7-01 through 3.7-02: Create dependency with default/explicit types
• UAT-3.7-03 through 3.7-09: Validations (non-existent items, self-reference, duplicates, circular detection)
• UAT-3.7-10 through 3.7-13: Get dependencies (predecessors + successors with work item objects)
• UAT-3.7-14 through 3.7-16: Delete dependency
• UAT-3.7-17 through 3.7-22: UI display (clickable links, dependency types, empty states)
• UAT-3.7-23 through 3.7-29: UI add dependency (searchable dropdown, type selection, circular error display)
• UAT-3.7-30 through 3.7-33: UI remove dependency (confirmation dialog)
• UAT-3.7-36 through 3.7-37: All 4 dependency types (FS, SS, FF, SF)
• UAT-3.7-38 through 3.7-41: Edge cases (complex cycles, cascading delete, many dependencies)

---

Story 3.8 — Keyboard Shortcuts for Work Items (#94)

40 scenarios — primarily manual validation.

Manual Validation Steps

List Page (/work-items)

1. Press n: Verify navigation to /work-items/new
2. Press /: Verify search input gets focus
3. Press ↓: Verify first work item row gets highlighted/selected
4. Press ↓/↑: Verify selection moves through list
5. Press Enter: Verify selected work item opens
6. Press Escape: Verify selection cleared
7. Focus an input, press n: Verify shortcut is NOT triggered (typing works normally)

Detail Page (/work-items/:id)

8. Press e: Verify first editable field (title) enters edit mode
9. Press Escape: Verify edit cancelled
10. Press Delete or Backspace: Verify delete confirmation dialog appears
11. Focus an input, press Delete: Verify shortcut NOT triggered

Help Overlay

12. Press ?: Verify keyboard shortcuts help overlay opens
13. Verify overlay content: Lists all available shortcuts for current page
14. Press ? again: Verify overlay closes (toggle)
15. Press Escape: Verify overlay closes

Modifier Key Guards

16. Press Ctrl+N: Verify shortcut NOT triggered (browser default)
17. Press Cmd+N (Mac): Verify shortcut NOT triggered
18. Press Shift+N: Verify shortcut NOT triggered (typing uppercase)

Cross-Browser

19. Test shortcuts in Chrome, Firefox, Safari, Edge (if available)

Key Scenarios

• UAT-3.8-01 through 3.8-09: List page shortcuts (n, /, arrows, Enter)
• UAT-3.8-10: Input focus suppresses shortcuts
• UAT-3.8-11 through 3.8-15: Detail page shortcuts (e, Delete/Backspace)
• UAT-3.8-16 through 3.8-19: Escape key behavior
• UAT-3.8-20 through 3.8-25: Help overlay (? toggle, content, Escape to close)
• UAT-3.8-26 through 3.8-29: Cross-browser compatibility
• UAT-3.8-30 through 3.8-32: Disabled states (modal open, input focused, select open)
• UAT-3.8-33 through 3.8-35: Reusable useKeyboardShortcuts hook
• UAT-3.8-36 through 3.8-40: Edge cases (modifier keys, rapid presses, keyboard layouts)

[github-actions]

🎉 This PR is included in version 1.8.0-beta.13 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.14 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.15 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.18 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.19 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.20 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.21 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.22 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.23 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.24 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.25 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.26 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.27 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.28 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0-beta.29 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀