dcd4955bb7
- Confirm->Receive (A): after a single interactive SO confirm, receiving's action_confirm returns action_view_receiving() so the user lands straight on the Receive Parts screen (opt-out via fp_no_receiving_redirect context). - Lock recipe (1): recipe_id readonly on the WO form — stick to the order-entry recipe. - Hide spec (2): customer_spec_id invisible on the WO form. - Reset step (3): new fp.job.step.button_reset (operator-usable, audited) + an undo button next to Start. Resets to Ready, clears finish + sign-off, closes open timelogs, keeps start audit + move/CoC history. - Lock steps (4): steps list create=false delete=false (no Add a line / no trash) — steps come from the recipe, only skippable, never deleted. - Bake gate fix (5): _fp_missing_required_step_inputs now honours the node's collect_measurements master switch, matching the Record-Inputs wizard. collect_measurements=False + required prompts no longer blocks finish (wizard shows 0 rows, so the gate must too). Unblocks WO-30098 + 63 other affected nodes (bake steps). Deployed + verified on entech (-u jobs; bake finishes, reset done->ready, recipe readonly, spec hidden, steps locked, receiving redirect target OK). Co-Authored-By: Claude Opus 4.8 (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.