Why it exists
A demanding game can reward attention, memory, patience, and curiosity. The surrounding tool should respect the player: quick lookup, keyboard operation, screen-reader structure, readable contrast, enlarged text, flexible layouts, low-bandwidth delivery, and source attribution are foundations.
Public catalog facts remain separate from private player activity. Uncertainty should remain visible instead of being polished into false authority.
What is live
The service publishes searchable and browsable views for equipment, spells, quests, recipes, people, places, crafting, travel, and planning. Its read-only public catalog API serves JSON, NDJSON, and XML for community tools.
The live service now renders its complete HTML surface through Sandwich Hime: 47 document families, 106 generated components, ordinary Go builds, and the old renderer retained as rollback.
Where it is going
The direction is a trustworthy player companion: make acquisition, travel, comparison, and planning decisions easier while keeping evidence and source history reviewable. Private synchronization and experimental client tooling remain gated until privacy, policy, compatibility, and human-acceptance evidence earns broader use.
Behind the migration
The mechanical template conversion was calmer than expected. Most of the work belonged where I wanted it: differential evidence, failure paths, rollback, deployment, and measuring the limits of what I could honestly claim.