[mforce]

Closes #54. Phase 1.1 slice (epic #14): "Mortality/culling + bird movement generation".

What

• BirdMovement — append-only ledger row: flock, date, type (Mortality/Cull/Adjustment), quantity (birds removed; Adjustment may be negative), note. Immutable — corrections are new rows, so no Version token.
• Submit generates mortality: SubmitDailyEntry writes a Mortality movement alongside egg lots in the same transaction — the existing submit Version race covers it (losing submit rolls back movement + lots together). Draft mortality is not a movement.
• Manual movements: POST /flocks/{id}/movements for Cull/Adjustment; manual Mortality rejected (would double-count at submit). Lifecycle gate reuses CanRecordProductionOn from F7: Flock management — edit/deplete/archive + Flocks screen #47 — depleted flocks accept backfill dated on/before depletion, archived accept nothing.
• Current counts: flock responses gain CurrentBirds = InitialCount − Σ quantities (one grouped query for lists). Flocks screen shows current count with initial alongside once they differ, plus a per-flock ledger panel with movement history and a cull/adjustment form.

Out of scope (per issue)

Transfers (houses phantom until Phase 2), auto-zero on deplete, feed/water.

Tests (+4 → 119)

Submit generates exactly one movement / zero-mortality days none / draft mortality not counted; cull + negative-adjustment math on get and list; validation (manual Mortality 400, zero qty, negative cull) and lifecycle gating (backfill OK, post-depletion 422, archived 422, unknown flock 404); parallel-submit race leaves exactly one movement.

Verification (chromium, real stack)

Submitted an entry with mortality 6 → Flocks screen 400→394; recorded a 10-bird cull → 384; −2 adjustment → 386. Ledger panel shows all three row types with signed quantities.

[mforce]

Review round: codex + pi

#	Source	Severity	Finding	Action
1	codex	P1	Upgrading an existing DB silently loses historical mortality — pre-feature submitted entries have no ledger rows, so CurrentBirds forgets past deaths permanently	Fixed — backfill in the follow-up migration inserts Mortality rows for existing non-Draft entries; verified against the dev DB (pre-feature entry gained a row, existing movement not duplicated) (fc46fdd)
2	pi	Medium	Generated Mortality rows carried no DailyEntryId — future manager-adjust/void flows can't find the ledger side of a corrected entry	Fixed — nullable FK back-reference set at submit; backfilled rows carry it too (fc46fdd)
3	codex + pi	P2/Low	Ledger fetch race: slow response for flock A renders under flock B's heading / clobbers post-write refresh	Fixed — responses apply only if their flock is still the open ledger (fc46fdd)
4	pi	Low	Submit path skipped the lifecycle gate — archived flock's leftover draft could still mint lots + mortality	Fixed — submit reuses CanRecordProductionOn(entry.Date); depleted-flock backfill drafts still submit (fc46fdd)
5	pi	Low	Append-only invariant unenforced at the repository seam	Fixed — Update/Remove throw NotSupportedException (fc46fdd)
6	pi	Low	Cull quantity input allowed negatives client-side	Fixed — min=1 when type is Cull; server validator was already the guarantee (fc46fdd)
7	pi	Low	No unique index on (Flock, Date, Mortality)	Deferred — the daily-entry natural-key unique index upstream is the invariant; revisit if backdated corrections ever loosen it
8	pi	Low	No bound on CurrentBirds going negative / above initial via adjustments	Deferred — display is honest about ledger contents; bounds enforcement belongs with the manager-adjust slice
9	pi	Low	RemovedByFlockAsync sums the whole tenant on every list	Deferred — flock counts are tiny; restrict to the page when flock lists actually page
10	pi	Low	Redundant standalone FlockId index (EF FK convention)	Skipped — EF-generated FK support index; harmless
11	pi	Low	Enum.Parse after validator is an implicit boundary	Skipped — same validated-parse pattern as grade endpoints

120 tests green after fixes (+1: archived-draft submit rejected / depleted backfill draft still submits; back-reference asserted in the submit test).