Refine encounter builder workflow and shared UI system

[Daren9m]

Summary

• restructure the encounter builder into a clear setup → review → act workflow
• separate calculated difficulty from actions so status no longer reads as a button
• move recipes, filters, map controls, exports, and print options into progressive disclosure
• place monster review before forecasting or live combat
• add shared semantic tokens, responsive workflow patterns, and a reusable UI style guide
• improve labels, focus restoration, touch targets, form submission, and print contrast

Why

The encounter builder had accumulated unrelated controls in the same surfaces and action rows. Primary actions, utilities, export formats, and state indicators carried similar visual weight, making the intended flow difficult to understand. The difficulty indicator between Run Battle and Edit Details was a particularly confusing example.

Impact

DMs now get a more deliberate encounter-building sequence with one clear primary action per decision surface. Shared buttons, headers, filters, status treatments, semantic tokens, and documented design rules also provide a consistent foundation for the rest of the toolkit.

Validation

• npm run typecheck
• npm run lint
• npm test — 670 tests passed
• npm run build — 16 static routes generated