docs: bring in the design handoff docs #200
No reviewers
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app!200
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/design-handoffs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Brings the two design handovers into the repo so the issues they generated
(#184, #199) point at something version-controlled rather than a path on one
laptop.
docs/design_handoff_jobs_flow/— the jobs board card, the detail sheet, thepickers, create, options and repeats, delete, the restricted sheets, and the
late state.
docs/design_handoff_calendar/— month, week, agenda, the day sheet, eventCRUD, and the visibility question settled in #187.
Both READMEs were reviewed against the server and carry their citations, so a
reader can check any claim against the code rather than take it on trust. The
.dc.htmlfiles are design references, not application code: static prototypeswith their own annotations and rejected alternatives.
support.jsis theruntime that opens them in a browser and is explicitly not for porting.
Stacked on #185 — merge that first.
🤖 Generated with Claude Code
Test report
Coverage: 26.7%
Updated by the check workflow · commit
5d5ef1af379d41ea250a73a94132ed73a94132ed5d5ef1af37