Make persistence crop fixture-readiness prove crop loss

[Ustice]

Original status: new GitHub issue
Parent: #17
Requires QA: true
Doc only: false
Agent level: Medium
Role: worker
Dependencies: #64 (sequenced prerequisite for the shared fixture-readiness command branch and first readiness gate)
Write scope: src/Wildfire.Timberborn/**, tests/Wildfire.Core.Tests/**, docs/TEST_PLAN.md, docs/qa-tooling.md

---

Make persistence crop fixture-readiness prove crop loss

Goal

Make qa-fixture-readiness crop truthfully prove crop-specific loss for #17 before the persistence save/reload matrix runs.

Parent Context

This is split out of #17. The fully combined #17 retry at 3fd1aa48 reached fixture commands, but crop readiness did not produce killed_crops or yield_lost tokens.

Evidence: #17 (comment)

Requirements

• qa-fixture-readiness crop must either produce last_delta_consumer_crop_burn_killed_crops>0 or last_delta_consumer_crop_burn_yield_lost>0, or fail clearly as setup/tool failure.
• Do not count generic heat deltas, burn-damage counters, or queued crop target evidence as sufficient without crop-specific loss.
• Preserve host-agnostic core boundaries; Timberborn remains the adapter.
• Do not change stored-goods or tainted-washout readiness in this ticket except where unavoidable for shared plumbing.

Verification

• Run git diff --check.
• Run focused deterministic tests for crop fixture readiness and crop burn consequence counters.
• Run focused dotnet test coverage for the changed command bridge/runtime/crop path.
• bun run typecheck if TypeScript changes.
• Live QA should later rerun only the qa-fixture-readiness crop gate before Validate World Consequence Persistence #17 resumes the full readiness matrix.

Role

• Worker.
• Follow kanban/roles/worker.md.

[Ustice]

Coordinator dependency cleanup: this child ticket should not be treated as ready in parallel with #64. It remains a child of parent #17, but its active prerequisite is #64 because #64 owns the first shared qa-fixture-readiness command slice and stored-goods readiness gate. Moving status:ready -> status:blocked until #64 is accepted/live-verified or the dependency is deliberately removed.

[Ustice]

Coordinator reclassification, 2026-05-30: moving from legacy status:blocked to status:waiting-for-dependency. This child readiness gate should wait on #64, which owns the first shared fixture-readiness command slice and stored-goods readiness gate. Reassess once #64 is accepted and live-verified, or if the dependency is deliberately removed.

[Ustice]

Coordinator dependency correction, 2026-05-30: the prior wait on #64 was a sequencing/branch-coordination choice, not a true product dependency. #64 implementation is accepted and its remaining blocker is live Timberborn environment, so this crop readiness worker slice can proceed from the current fixture-readiness branch/stack without waiting for #64 live QA. Moving to status:ready. Parent #17 still waits for #64, #65, and #66 readiness gates before persistence-matrix QA.