jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Recover whole-game packed event conditions

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-15 22:38:13 -07:00
commit 5d779263d2
7 changed files with 414 additions and 117 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/runtime-rehost-plan.md
View file

@ -52,6 +52,11 @@ Implemented today:
through the same service path, and whole-game parity frontiers now report explicit unmapped
world-condition and world-descriptor buckets rather than falling back to the generic ordinary
or descriptor counts
- checked-in whole-game condition metadata now drives that same world-side condition batch too:
special-condition thresholds use the real special-condition label ids, economic-status thresholds
use the checked-in world label id, and candidate-availability thresholds now decode through the
recovered `%1 Avail.` template plus the packed candidate-name side string instead of fixture-only
placeholder ids
- checked-in whole-game grouped-descriptor metadata now drives the first real world-side effect
batch too: real special-condition and candidate-availability setter rows now decode and import
through the ordinary runtime path, while world-flag rows remain parity-only until keyed flag
@ -59,10 +64,10 @@ Implemented today:
That means the next implementation work is breadth, not bootstrap. The recommended next slice is
broader real grouped-descriptor and ordinary condition-id coverage beyond the current access,
whole-game, train, player, and numeric-threshold batches, with the whole-game frontier now
centered on still-unmapped world-flag families and any later state families that need stronger
checked-in descriptor or key recovery. Richer runtime ownership should still be added only where a
later descriptor or condition family needs more than the current event-owned roster.
whole-game, train, player, and numeric-threshold batches, with the world-side frontier now
centered primarily on still-unmapped world-flag families and any later state families that need
stronger checked-in descriptor or key recovery. Richer runtime ownership should still be added only
where a later descriptor or condition family needs more than the current event-owned roster.
## Why This Boundary