17dbfc6dc0
feat(01-02): design initial database schema migration
...
- 23 tables covering venue settings, chip sets, blind structures, payout structures,
buy-in configs, tournament templates, tournaments, players, tables, seating,
transactions, bubble prizes, audit trail, and operators
- All financial columns use INTEGER (int64 cents, never REAL/FLOAT)
- Audit trail append-only enforced by SQLite triggers (reject UPDATE except undone_by, reject DELETE)
- All tournament-specific tables reference tournament_id for multi-tournament support
- Comprehensive indexes on foreign keys and common query patterns
- Players table with UUID PK for cross-venue portability
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 03:31:01 +01:00
aa07c0270d
wip: 01-tournament-engine paused at security feedback (1/7 applied)
...
Applied security fix 1 (no default admin PIN in prod, first-run setup).
Fixes 2-7 remaining: WS auth, HTTP hardening, audit triggers, JWT
validation, NATS subject validation, CSV safety.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 03:17:46 +01:00
21ff95068e
docs(01): create Phase 1 plans (A-N) with research and feedback
...
14 plans in 6 waves covering all 68 requirements for the Tournament
Engine phase. Includes research (go-libsql, NATS JetStream, Svelte 5
runes, ICM complexity), plan verification (2 iterations), and user
feedback (hand-for-hand UX, SEAT-06 reword, re-entry semantics,
integration test, DKK defaults, JWT 7-day expiry, clock tap safety).
Wave structure:
1: A (scaffold), B (schema)
2: C (auth/audit), D (clock), E (templates), J (frontend scaffold)
3: F (financial), H (seating), M (layout shell)
4: G (player management)
5: I (tournament lifecycle)
6: K (overview/financials), L (players), N (tables/more)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 02:58:22 +01:00
5cdd7b0fa7
docs(01): research phase domain
2026-03-01 02:10:18 +01:00
0030d4d2c2
docs(01): capture phase context
2026-03-01 01:59:26 +01:00
aa38a14cb4
docs: save roadmap feedback for next session
2026-02-28 16:11:21 +01:00
19a66014e8
docs: apply requirements feedback (8 items — late reg, balancing confirm, sync templates, PIN rate limit, backup/recovery, display memory, CMS scope)
2026-02-28 16:08:56 +01:00
b5b799cbc8
docs: create roadmap (11 phases)
2026-02-28 16:08:33 +01:00
c846f8edd9
docs: define v1 requirements
2026-02-28 16:03:29 +01:00
ff6ff29af3
docs: address PROJECT.md gaps (platform identity, virtual Leaf, regional organizer, custom domains, business model, dealer portability)
2026-02-28 16:01:09 +01:00
27ee0a5813
docs: complete project research
2026-02-28 15:59:25 +01:00
aa48e52780
chore: update depth to comprehensive
2026-02-28 15:47:28 +01:00
f0d2f16877
docs: initialize project
2026-02-28 15:47:28 +01:00
49c837b0e1
chore: add project config
2026-02-28 15:45:53 +01:00
a254f79bd2
Initial docs/project description including financial models
2026-02-28 15:37:21 +01:00
