d9ae45ce9b
The existing 'state' field tracks wear (active/needs_strip/stripping/ retired). Sub 12b adds an orthogonal 'racking_state' (empty/loading/ loaded/in_use/awaiting_unrack/out_of_service) for the load lifecycle — a rack can be wear-active AND racking-loaded simultaneously. New fields: racking_state — operational lifecycle tag_ids (M2M) — fp.rack.tag chips on plant overview capacity_count — soft warn (distinct from existing 'capacity') current_job_step_id — compute, derived from latest fp.job.step.move current_tank_id — compute current_part_count — compute Form view picks up the new fields under Sub-12b group + a 'Current Use' panel that hides when racking_state is empty / out_of_service. The compute references fp.job.step.move which lands in Task 4 — the module won't load cleanly on entech until Tasks 4-5 ship; that's expected for batch deployment at the end. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>