houserules/packages
Joey Yakimowich-Payne 85433867ea
feat(T7): Widen spawn-marker & spawn-marker-pair schemas for resolver shapes
T7 (spawn-marker-pair schema widening) — widen two primitive schemas to accept
resolver shapes on numeric and enum fields, enabling real fixtures to validate.

## Changes

### spawn-marker.ts
- Widen `square` from literal number to numberOrResolver({ min: 0, max: 63 })
- Widen `owner` from literal enum to enumOrResolverFor(PIECE_COLORS).optional()
- Keep `markerKind` strict enum (design constraint — locked marker kinds)
- Update apply() to cast resolved params to literals before engine call

### spawn-marker-pair.ts
- Widen `squareA` and `squareB` to numberOrResolver({ min: 0, max: 63 })
- Widen `owner` to enumOrResolverFor(PIECE_COLORS).optional()
- Keep `markerKind` strict enum
- Update apply() method with cast assertions

### Tests
- Add 8 resolver-shape positive tests to spawn-marker.test.ts
- Add 8 resolver-shape positive tests to spawn-marker-pair.test.ts
- Add 2 strict-enum negative tests (markerKind rejection)
- Add 2 __resolverEnumValues introspection tests (ParamField compatibility)
- Add mr-freeze-validates.test.ts: validates mr_freeze.json (cascade depth 3)
  fixture with resolver shapes on square (ctx-build) and owner (ctx-attr)

## Verification

 mr_freeze.json now validates cleanly (was the wave goal)
 __resolverEnumValues property exposed and survives .optional() wrapper
 60 tests pass (30 spawn-marker + 29 spawn-marker-pair + 1 mr-freeze)
 No new linting issues
 Links field left alone (mr_freeze doesn't use resolver shapes on links)
2026-04-26 23:03:47 -06:00
..
chess feat(T7): Widen spawn-marker & spawn-marker-pair schemas for resolver shapes 2026-04-26 23:03:47 -06:00
rete refactor(rete): use asEntityId for AGG_FACT sentinel id 2026-04-19 16:49:50 -06:00
server feat(thressgame-coverage): Wave 15 (e2e for 5 parity rules + lift T68/3 parry) 2026-04-26 18:06:05 -06:00