P01: P5: crafting and collection

Go implementation tracking epic

Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.

Child tasks

• P01a: Recipe graph and missing-resource service
  • Merged prerequisites: I01c, F03b.
  • Acceptance: R10: known recipe/component data, quantity arithmetic, cycle/unknown handling; hand-calculated multi-level fixtures.
• P01b: Crafting planner UI
  • Merged prerequisites: P01a.
  • Acceptance: R10/R8: prerequisite tree and missing quantities, unknown requirements and snapshot age; keyboard and scale checks.
• P01c: Collection and mastery tracking
  • Merged prerequisites: I01b, F03b.
  • Acceptance: R10: only verified mastery fields or explicit user input; ownership distinct from mastery; unavailable status and provenance tested.
• P01d: Foundry timers if fields are proven
  • Merged prerequisites: P01b, F03b.
  • Acceptance: R10: only schedule with verified timing/state data; stale snapshots and clock changes tested. Otherwise record as deferred, not complete.

Workflow

See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.

All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.

Start with TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then choose a child task rather than implementing this epic as one PR. Check its listed prerequisites and acceptance criteria, including the required fixtures or provenance and snapshot checks. Done means each child passes, evidence and this checklist are updated, and any unproven optional work is explicitly deferred.