[Phase 3.2] PostgreSQL Schema for Accounts, ScannedCreatureInstance Offsets & Decks #12
Labels
No labels
area:backend-infra
area:ci
area:client
area:core
area:data
area:server
P0
P1
P2
status:backlog
status:in-progress
status:ready
status:review
type:chore
type:feature
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
john4064/Chaotic#12
Loading…
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?
Goal
Stand up idempotent PostgreSQL migrations (
deploy/sql/) and repository layer storing accounts, rolledScannedCreatureInstanceoffsets, and validated 5-deck loadouts.Metadata
deploy/sql/,.forgejo/workflows/db_migration.yml, DB repository module.rs<= 400 lines, test.rs<= 600 lines,mod.rs< 80 lines (AGENTS.mdSection 2.3)Acceptance Criteria
deploy/sql/) with CHECK constraints enforcingenergy_offset IN (-5, 0, 5)and discipline offsets in(-10, -5, 0, 5, 10).scripts/bug_hunter.pyPillar 3 (CREATE TABLEvs queries).postgres:16-alpinewithout swallowed DB errors.chaotic_core5-deck validator before persisting.