NilsBriggen 961fe8655a D1: AI Director (MVP) — grounded AI DM narration + no-auto-roll dice buttons
The first user-visible slice of the AI DM / AI Player "director": a new
/director page where the AI narrates the scene, voices NPCs/monsters, and runs
enemies — grounded entirely in the campaign's real party and active encounter,
and degrading to a deterministic narrator when no AI key is set.

Engine (pure, framework-free) in src/lib/assistant/director/:
- schema.ts: DeepSeek-tolerant directorTurnSchema (z.preprocess structural
  repair + z.coerce + .catch() enums + per-element safeParse-drop) → a single
  validated turn { narration, rollRequests[], actions[], suggestions[] }.
- context.ts: buildDirectorScene assembles a CLOSED roster from the active
  encounter (or the party) with deriveState badges — the only entities the
  director may name.
- prompt.ts: persona-aware system prompt (DM/player) leading with the
  systemConstraint; multi-turn message mapping from the transcript.
- engine.ts: runDirectorTurn + sanitizeTurn — the anti-hallucination gate that
  drops any action referencing an off-roster entity (and ungrounded
  addCombatant), mirroring the encounter advisor's candidate filter.
- fallback.ts: deterministic director that still surfaces roll buttons.

Hard rules, enforced:
- NEVER auto-roll: a roll fires only from RollRequestCard's onClick (rollAndShow).
  A unit test asserts the engine layer never imports the roll seam, making
  auto-roll structurally impossible.
- Approve-each: D1 is read-only (actions render as previews; the Apply bridge
  lands in D2). The director never writes game state.
- Always-on fallback: works with no API key.

Also: Dexie v18 `aiSessions` table + aiSessionsRepo (+ cascade delete), a small
directorStore, a Settings card, and the /director route + nav entry.

Verified in-app on the sample 5e campaign: grounded narration named the real
current combatant; on an enemy's turn a "Aller Rosk attack vs Pip Underbough"
roll card appeared with diceRolls UNCHANGED until the button was clicked, which
then fired exactly one roll and recorded the result back into the transcript.
381 unit tests green; lint clean (3 pre-existing); build OK.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-10 02:55:42 +02:00
2026-06-07 23:47:39 +02:00
2026-06-07 23:47:39 +02:00
2026-06-07 23:47:39 +02:00
2026-06-07 23:47:39 +02:00

TTRPG Manager

A local-first campaign manager for D&D 5e and Pathfinder 2e, built for both Game Masters and players. Runs entirely in the browser (installable as a PWA) — your data lives in IndexedDB on your device; no account, no server.

Features (MVP)

  • Campaigns — create per-system campaigns; deleting one cascades to all its data.
  • Characters — 5e/PF2e sheets with live derived stats: ability modifiers, proficiency, skills, saves, AC, initiative, HP (with damage/heal/temp). Autosaves.
  • Combat tracker — initiative order, round/turn tracking, conditions, HP, and add/remove/reorder mid-fight without ever corrupting whose turn it is.
  • Dice — full notation (2d6+3, 4d6kh3), advantage/disadvantage, seedable RNG, per-campaign roll history.
  • Compendium — searchable SRD bestiary, spells, and magic items. Add any monster straight into the open encounter.

Tech

  • React 19 + TypeScript (strict) + Vite
  • TanStack Router · Zustand · Zod · Dexie (IndexedDB) · Tailwind v4 · Fuse.js
  • Vitest (unit) + Playwright (e2e), PWA via vite-plugin-pwa

Architecture

src/
  lib/
    rules/        # game-system abstraction — 5e & pf2e behind one RulesSystem interface
    combat/       # pure, tested turn-order + HP engine
    dice/         # notation parser + roller
    db/           # Dexie schema + repositories (cascade deletes, validation on write)
    schemas/      # Zod entity schemas — every number rejects NaN/Infinity
    compendium/   # lazy SRD data loaders (code-split out of the main bundle)
  features/       # campaigns, characters, combat, dice, compendium (UI)
  components/ui/  # design-system primitives
  data/srd/       # SRD JSON (Open5e + MPMB); regenerate with scripts/fetch_data.py

The rules layer means features never branch on if (system === '5e'); they call the RulesSystem interface, so adding a system is a self-contained module.

Development

bun install
bun run dev          # dev server at http://localhost:5173
bun run test         # unit tests (vitest)
bun run test:e2e     # end-to-end (playwright)
bun run build        # typecheck + production build
bun run lint

Roadmap

Notes/journal, maps with fog of war, encounter/loot builders, a shared player view, PF2e compendium data, and an optional sync backend for real-time tables.

History

This is a from-scratch rebuild. The previous implementation (deleted) had ~135 documented bugs and no version control; its bug report is kept at docs/OLD_BUG_HUNT_REPORT.md as a record of failure modes designed against here (silent data loss, turn-order corruption, no cascade deletes, NaN inputs, dead Tauri integration). The SRD data and Python scrapers were preserved.

S
Description
No description provided
Readme 17 MiB
Languages
TypeScript 98.7%
CSS 0.6%
Python 0.5%
JavaScript 0.1%