ttrpg-initiative-tracker

189 Commits 6 Branches 5 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
david raistrick	9c90c1500c	feat(turn): D&D 5e death saves — success/fail tracking Old model broken: single deathSaves counter, 3=revive. No fails tracked, successes conflated with fails. DM couldn't model real death save outcomes. New model (D&D 5e): - deathSave(enc, id, type, n) — type='success'\|'fail', n=1\|2\|3 - Participant fields: deathSaves (successes), deathFails, isStable, isDying - 3 successes = stable (0hp unconscious, safe until healed) - 3 failures = dead (isDying, caller animates removal) - Toggling same pip = undo that pip - Returns { patch, log, status } — status: 'stable'\|'dead'\|'pending' isDying back-compat flag kept for App.js removal animation App.js: - UI split into green ✓ saves row + red ✕ fails row - Status badges: Stabilized (emerald) / Dying (red pulse) - handleDeathSaveChange(participantId, type, saveNumber) — new sig - makeParticipant init: deathFails + isStable defaults Data loss: old single-counter participants lose saves (feature didn't work, no real state to preserve). User confirmed acceptable. Tests: - turn.deathsave.test.js: RED-then-GREEN, 3-success stable, 3-fail dead, independent tracking, new signature - Updated 6 callers across characterization/combat/dead-skip/logging/scenario - Logs UI tests: new title selectors (Success N / Fail N) 243 tests green.	2026-07-04 17:56:14 -04:00
david raistrick	32b8dfd8a1	fix(turn): log addParticipants + updateParticipant (logging gaps) addParticipants + updateParticipant returned log:null → invisible in combat log. Contract test caught them. Now both return log:{ message, undo:{ participants }}. App.js handlers wired (handleAddAllCharacters, handleUpdateParticipant, handleInlineInitiative) — call logAction on logged mutations. Logging contract now complete: every mutating combat op produces a log entry. No gaps. turn.logging.test.js proves it. 238 tests green.	2026-07-04 17:25:22 -04:00
david raistrick	ab9f8fa2e7	fix(turn): log reorder + deathSave (BUG-7) reorderParticipants returned log:null → handler skipped logAction → drag invisible in combat log, no undo payload. Now returns log:{ message, undo:{ participants, turnOrderIds, currentTurnParticipantId }}. App.js handleDrop calls logAction on logged reorders. Found second gap: deathSave also returned null log (both branches). Fixed — message + undo (participants snapshot). Added logging contract test (turn.logging.test.js): - all mutating ops logged (start/next/pause/add/remove/toggle/hp/deathsave/ condition/reorder/end) - no-ops return null log (same-id, cross-init, cross-pointer blocks) - undo payloads valid + restore prior state - documents addParticipants + updateParticipant gaps (null log, intentional) 235 tests green.	2026-07-04 17:22:52 -04:00

Author

SHA1

Message

Date

david raistrick

9c90c1500c

feat(turn): D&D 5e death saves — success/fail tracking

Old model broken: single deathSaves counter, 3=revive. No fails tracked,
successes conflated with fails. DM couldn't model real death save outcomes.

New model (D&D 5e):
- deathSave(enc, id, type, n) — type='success'|'fail', n=1|2|3
- Participant fields: deathSaves (successes), deathFails, isStable, isDying
- 3 successes = stable (0hp unconscious, safe until healed)
- 3 failures = dead (isDying, caller animates removal)
- Toggling same pip = undo that pip
- Returns { patch, log, status } — status: 'stable'|'dead'|'pending'
  isDying back-compat flag kept for App.js removal animation

App.js:
- UI split into green ✓ saves row + red ✕ fails row
- Status badges: Stabilized (emerald) / Dying (red pulse)
- handleDeathSaveChange(participantId, type, saveNumber) — new sig
- makeParticipant init: deathFails + isStable defaults

Data loss: old single-counter participants lose saves (feature didn't work,
no real state to preserve). User confirmed acceptable.

Tests:
- turn.deathsave.test.js: RED-then-GREEN, 3-success stable, 3-fail dead,
  independent tracking, new signature
- Updated 6 callers across characterization/combat/dead-skip/logging/scenario
- Logs UI tests: new title selectors (Success N / Fail N)

243 tests green.

2026-07-04 17:56:14 -04:00

david raistrick

32b8dfd8a1

fix(turn): log addParticipants + updateParticipant (logging gaps)

addParticipants + updateParticipant returned log:null → invisible in
combat log. Contract test caught them. Now both return
log:{ message, undo:{ participants }}.

App.js handlers wired (handleAddAllCharacters, handleUpdateParticipant,
handleInlineInitiative) — call logAction on logged mutations.

Logging contract now complete: every mutating combat op produces a log
entry. No gaps. turn.logging.test.js proves it.

238 tests green.

2026-07-04 17:25:22 -04:00

david raistrick

ab9f8fa2e7

fix(turn): log reorder + deathSave (BUG-7)

reorderParticipants returned log:null → handler skipped logAction → drag
invisible in combat log, no undo payload. Now returns
log:{ message, undo:{ participants, turnOrderIds, currentTurnParticipantId }}.
App.js handleDrop calls logAction on logged reorders.

Found second gap: deathSave also returned null log (both branches).
Fixed — message + undo (participants snapshot).

Added logging contract test (turn.logging.test.js):
- all mutating ops logged (start/next/pause/add/remove/toggle/hp/deathsave/
  condition/reorder/end)
- no-ops return null log (same-id, cross-init, cross-pointer blocks)
- undo payloads valid + restore prior state
- documents addParticipants + updateParticipant gaps (null log, intentional)

235 tests green.

2026-07-04 17:22:52 -04:00