Upgrade New Fields

Old player data will not include newly added fields. Any time you add a field to a GraphQL type that maps to a persisted model (e.g., Hero), you must update the model upgrade path so legacy records load safely.

What to do when adding a new field:

• Make it optional in Partial types:

  • Update the Partial<Hero> (or equivalent) union in db/models/* to include the new key so old data can pass through the upgrader without compile errors.

• Provide a default in upgrade():

  • In the model's upgrade(data) function, initialize the new field with a sensible default. If the field is computed-only, set a conservative placeholder; the resolver should remain source of truth.

• Keep logic single-sourced:

  • For computed fields (derived from equipment, class, etc.), implement the logic in a helper or the GraphQL field resolver. Only set a default in upgrade() to satisfy typing; do not duplicate complex calculations.

• Regenerate code and validate:

  • Server: yarn --cwd proofofcombat-server generate
  • UI: ensure the server is running locally, then