1d0d4afdbf
Three cascading bugs caused DOD-00153/WO-30061 to confirm with zero steps (and DOD-00150 to keep masking/bake even with overrides): 1. _is_node_included() in fp_job._generate_steps_from_recipe consulted the per-job override_map ONLY when node.opt_in_out was 'opt_in' or 'opt_out'. Default is 'disabled' (mandatory), so overrides on mandatory recipe nodes (Masking, De-Masking, Oven baking) were silently ignored. Fix: consult override_map FIRST — explicit per-job override always wins, regardless of node's opt_in_out value. 2. fp.direct.order.line.recipe_choice_ids didn't include the wizard's material_process recipe (Express Orders order-level recipe), so the line's process_variant_id domain rejected propagation. Added a 4th tier to the compute that pulls the order's header recipe in. 3. sale_order._fp_resolve_recipe_for_line fell back from line picker to part.default_process_id with nothing between. Added Express header recipe (self.x_fc_material_process) as a 2nd-priority fallback — catches cases where G3 propagation failed to reach the line but the SO header has the recipe set. Also fixed an unrelated G4 bug: _FP_PART_SYNC_FIELDS mapped process_variant_id → 'default_process_variant_id' which doesn't exist. Real field is 'default_process_id' (singular). Cleaned up DOD-00153/WO-30061 manually: backfilled line + job.recipe_id, regenerated steps with overrides respected. 8 steps now visible, masking/bake correctly omitted.
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.