feat: custom systems record their setup answers, and the health model…

[over2take]

… shapes the starter sheet

A system's core section answers the setup questions: the health model (one pool, two tracks, damage types, harm levels, wound count, hit locations or none) with its settings, how characters advance, the system's common dice and its distance unit. Initiative on or off stays a part. Every answer is checked, each problem reported with where it is.

The health model shapes the starter sheet a system has before its GM designs one: two tracks put the first on the token and the second on the sheet, harm levels give a line per slot with the penalty as its hint, and so on. A system that answers nothing gets the same starter sheet it always had, byte for byte. How each model takes damage in play comes in its own piece.

Summary

Test plan

• Tested locally
• Tests pass

Pre-merge checklist

Code quality:

• Code follows project style
• No breaking changes (or clearly documented)
• No console errors or warnings

Version & Release:

• Version bumped? If releasing to users, update:
  • frontend/package.json version
  • docker-compose.yml APP_VERSION
  • CHANGELOG.md with release notes
• GitHub Actions will auto-tag Docker images with the new version

Before merging to main:

• All tests passing
• PR reviewed and approved
• Branch is up to date with main
• No merge conflicts

Related issues