Skip to content

Synchronize restoration facts across authored regions - #123

Merged
hoainho merged 1 commit into
mainfrom
task/p04-restoration-sync-20261005-a
Oct 5, 2026
Merged

hoainho merged 1 commit into
mainfrom
task/p04-restoration-sync-20261005-a

Conversation

@hoainho

@hoainho hoainho commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Scope

  • Initialize restoration state, partial/restored facts, and canonical aliases from authored/canonical world state.
  • Keep the canonical five-region set unchanged; persist noncanonical authored-region state locally and migrate legacy boolean-only saves.
  • Normalize events, quest consequences, checkpoint restore, save load, and import adoption; preserve safe authored route arrival and renderer tint behavior.
  • Document the static authored-collider boundary; no dynamic collision transitions added.

Verification

  • npm run typecheck: passed.
  • npm run build: passed (existing >500 kB chunk-size warning).
  • bun test: 557 passed, 0 failed.
  • Renderer browser smoke: PASS; no page errors.
  • Native IndexedDB smoke: 19 scenarios PASS; cleanup succeeded. Quota fault is synthetic; gameReady remains false.

Remaining acceptance

This PR addresses restoration state synchronization only. Issue #52 remains open: production runtime/assets and full acceptance are not established, and no restoration-conditioned collider transitions are authored. No production-readiness claim.

Refs #52

@hoainho
hoainho merged commit 0ef65af into main Oct 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant