Builds replayable combat logs with first-class undo/redo, unified verification tooling, fast indexed log queries, and stricter CI.

feat(combat): add first-class undo and redo controls

Add undo and redo controls to the combat UI so the DM can recover from recent
actions without leaving the encounter view.

Undo and redo operate on the current encounter's combat history. Empty stacks
produce clear feedback instead of failing silently. Redo order follows normal
stack behavior after multiple undos.

This makes combat history actionable during play, not just visible in the log.

feat(logs): make combat logs replayable

Replace plain combat log messages with structured combat events that can be
used by the UI, exported as JSON, replayed, and verified.

Each new log entry records the action type, encounter identity, participant
identity, a small action delta, undo intent, and a turn snapshot. Download and
copy now export the event stream as JSON so a saved combat log is useful for
offline analysis and debugging.

Legacy logs remain viewable, but new logs use the structured event format.

feat(logs): make undo and redo transactional

Apply undo and redo as single storage operations so the encounter state and log
state cannot drift apart.

Server storage applies the encounter update and the log undone flag inside one
SQLite transaction. Firebase storage uses a batch write for the same behavior.
The storage contract now includes undo/redo semantics.

This replaces fragile multi-write undo behavior where a failure could update
the encounter without marking the log, or mark the log without updating the
encounter.

feat(combat): add unified replay and verification tool

Add one combat CLI for replaying live combat and verifying combat logs.

Replay drives the live backend through the same shared combat logic used by the
app, writes a JSON event log to an explicit output path, and automatically
verifies the result. Verification checks for DM-visible combat problems such as
skipped turns, double actions, bad round changes, and unexpected turn order
changes.

The tool uses the same JSON event stream produced by log downloads, supports
verbose turn output, and handles Ctrl-C by ending the encounter, writing the
partial log, and verifying what was captured.

fix(perf): keep long combat logging fast

Remove the combat-time log query bottleneck that made long replays slow as log
volume grew.

Combat controls no longer subscribe to the log collection just to keep undo and
redo state warm. Undo and redo now query the latest matching encounter log only
when clicked. Server collection queries support exact filters, ordering,
limits, and offsets, and SQLite indexes keep latest-log and per-encounter log
lookups fast.

Also fix duplicate WebSocket handler registration so realtime updates do not
double-fire under write load.

fix(turns): make toggle active a status change

Make toggle active a roster/status edit instead of a turn advance.

Deactivating the current participant no longer passes the turn or increments
the round. The current turn stays where it is until the DM explicitly clicks
Next Turn, and Next Turn skips inactive participants during normal rotation.

This matches the initiative design: slot order is stable, toggle active does
not move participants, and round changes only come from explicit turn advance.

chore(ci): make warnings and hangs fail fast

Tighten test and build checks so failures are visible instead of noisy or
silent.

Builds run with CI enabled so warnings fail production builds. The full test
command runs app, shared, and server suites with hard timeouts so hangs fail
quickly. Static eslint coverage fails on warnings as well as errors.

Tests were updated around the new async combat logging flow, structured log
events, transactional undo, replay verification, and toggle-active semantics.

TODO.md

@@ -4,6 +4,50 @@ Backlog of bugs + long-term items. Milestones live in REWORK_PLAN.md.
 
 ## Open
 
+### TEST GAP: current branch changes need focused coverage
+- Storage `where()` contract: firebase + server adapters should honor `[where('encounterPath','==',x), orderBy('ts','desc'), limit(n)]`.
+- Server SQL query test: `where + orderBy + limit` should return latest logs for one encounter only.
+- Undo/redo stack order: undo A3 then A2, redo must replay A2 first, then A3.
+- Combat controls should not subscribe to logs while mounted; undo/redo should query logs only on click.
+- Unified CLI smoke: `node scripts/combat.js verify <fixture.json>` returns CLEAN on known-good log.
+- Unified CLI replay smoke: `node scripts/combat.js replay ... --out tmp/x.json` writes JSON array and auto-verifies.
+- Ctrl-C replay behavior: SIGINT during replay should end encounter, clear active display, write partial log, run verify.
+- SQLite schema/index test: `idx_docs_parent_ts` and `idx_docs_parent_encounter_ts` exist for server DB.
+
+### confirm warnings treated as error = fail in all tests, build pipeline, linters, everything. again.
+
+### BUG: addParticipants (batch add) does not slot by initiative
+- shared/turn.js addParticipants appends `[...existing, ...new]`, no slotIndexForInit.
+- Violates INIT doc: "Add = insert into slot by initiative."
+- Single addParticipant slots correct. Batch (add-all-chars) appends.
+- Pre-start batch add = wrong order. Post-start worse.
+
+### BUG: nextTurn throws on solo combatant
+- nextActiveAfter loop `for step=1; step<n` skips when n=1 → {nextId:null}.
+- nextTurn throws "Could not determine next participant."
+- Solo active combat cannot pass turn.
+
+### BUG: reorderParticipants cross-pointer drag = silent no-op
+- Cross-pointer drag returns encounter unchanged, no log, no toast.
+- DM drags across current turn → nothing happens, no feedback.
+
+### BUG: addParticipant undo missing currentTurnParticipantId when started
+- undo saves participants + conditional turnOrderIds, no currentTurnParticipantId.
+- Pointer can misalign on undo if added near pointer region.
+
+### BUG: computeTurnOrderAfterRemoval isActive uses find() not boolean
+- `isActive = id => updatedParticipants.find(p => p.id === id && p.isActive)`
+- Returns participant obj (truthy) not boolean. Works by accident, fragile.
+
+### BUG: select campaign during active combat = screen flicker, no action
+- In active encounter, click different campaign → flicker, no nav, no end.
+- Either block (toast: end encounter first) or auto-end current + switch.
+- Decide UX before fix.
+
+
+### death saves feature - dead PCs should not get removed from initiative! DAMMIT!
+
+
 ### FEAT: clarify "Is NPC" in add-participant
 - Ambiguous label. May expand work based on what NPC means here (ally? monster?
   display-only? skip in turn order?). Clarify intent before UX changes.