Split the two existing card decks into separate activities #2
Labels
No labels
priority/high
priority/low
priority/medium
type/feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ben/career-values-cards#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Model 'activities' as first-class entities instead of two hard-coded tabs.
Scope
activity(title, instructions, columns, cards) and per-useractivity session/assignment holding placements, notes, flags.Acceptance
Handoff context: the app is being prepared so a counselling practice can self-host it (see README and docs/self-hosting.md). Today the app has no auth by design, two hard-coded decks in
shared/cards.json, three fixed columns, and Fastify + SQLite + SSE sync (docs/api.md).Filed during handoff prep (README and docs/self-hosting.md in
c133282). No implementation yet. Recommended order: #2 (activities data model + migration) before #1 (RBAC), pending the maintainer's confirmation.Done in
7a4378cand deployed to career.tealmaker.com on 2026-10-13.Decisions (maintainer):
What landed:
user_versionmigration runner with a VACUUM INTO backup and a frozen seed; it aborts on unmapped cards.activities,activity_columns,activity_cardsandsession_activitiestables.?v=2); legacy routes keep their old shapes until #1.Verification:
Review: High tier, first round 3/3 (codex/deepseek/qwen), plus two delta rounds. Archived-card UI leftovers are deferred to #5 (see the comment there).