3d1b6e7ec5
Reported 2026-05-20: the receiving state machine had four states (draft → counted → staged → closed) where the middle pair was pure ceremony. Real-usage data on entech: state distribution: 14 draft, 4 closed (zero `staged` records) median dwell counted → staged: 11 seconds median dwell staged → closed: 4 minutes `staged` captured no fields, fired no gates, mapped to the same SO `x_fc_receiving_status='partial'` as `counted`. Pure click-through. Cleanup: - State Selection retains `staged` as `Staged (legacy)` so historical records remain readable; new transitions never write it. - statusbar_visible drops it from the chevron header. - action_mark_staged becomes a thin shim that advances counted → closed directly (any old button binding still works). - action_close now accepts `counted` as a valid source state (was previously only `staged` / legacy `accepted` / `resolved`). - View: "Stage for Racking" button removed. "Close" button renamed to "Close — Racking Confirmed" so the racking-crew confirmation meaning stays obvious. - _update_so_receiving_status mapping unchanged for legacy `staged` (still maps to partial) — only the comment block updated to describe the new canonical flow. Migration 19.0.3.20.0 advances any `staged` records to `closed` and syncs the linked SO's x_fc_receiving_status to `received` so downstream gates (job step start, mark_done qty check, cert creation) don't see a stale "partial" status. Module: fusion_plating_receiving 19.0.3.19.0 → 19.0.3.20.0. Tests: TestQtyReceivedPropagation updated — 5 tests dropped the action_mark_staged() call, walk draft → counted → closed directly. All 11 tests green (carrier 6 + propagation 5). Verified on entech: existing 14 draft + 4 closed records untouched. Direct draft → counted → closed transition works end-to-end on RCV-30041 (was the test target). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fusion_plating_jobs
Native plating job bridge — wires fp.job and fp.job.step (defined in
fusion_plating core, Phase 1 of the migration spec dated 2026-04-25)
into the rest of the Fusion Plating module family: configurator, portal,
logistics, quality, certificates, batches, KPI, notifications, reports.
Coexists with fusion_plating_bridge_mrp during the migration period.
The x_fc_use_native_jobs settings flag (default: False) toggles the
behaviour. When False, SO confirm continues to create mrp.production
records through bridge_mrp. When True, SO confirm creates fp.job
records here.
See docs/superpowers/specs/2026-04-25-fp-native-job-model-design.md
for full design rationale and §6 of the implementation plan for phase
breakdown.
Phase 6 — deferred items
Phase 6 originally scoped the full operator UI rewrite. With Tailscale SSH to entech currently unavailable we cannot live-test OWL/JS in the browser, so Phase 6 ships a lean version: the data-layer endpoints land now, the rendering UI lands later.
Deferred to post-cutover hardening:
- Plant Overview kanban over
fp.job.step— replacesfusion_plating_shopfloor'smrp.workorderkanban. - Tablet Station UI rewrite over
fp.job/fp.job.step. - Manager Dashboard rewrite.
- Process Tree OWL component — currently a stub:
/fp/jobs/process_treereturns the serialized recipe tree as JSON, but the OWL component to render it is not built.
Rationale: these are large OWL/JS components that need live in-browser
verification on entech. Under the migration's parallel-coexistence
strategy, operators continue using the existing shopfloor UI (bound to
mrp.workorder) until cutover. After cutover, the operator UI rewrite
becomes its own focused project — the data layer (fp.job,
fp.job.step, time logs, timestamps) is fully in place from
Phase 1–5.
Phase 6 — what shipped
/fp/job/<id>— scan-redirect controller. The fp.job sticker QR encodes this URL. Routes managers to thefp.jobform; routes operators to the same form for now (will swap to the process tree client action once the OWL component lands)./fp/jobs/process_tree— JSON-RPC endpoint that returns the recipe tree for a job, with each node tagged by its matchingfp.job.stepstate, ready for an OWL component to consume.