0600b87a29
Reported 2026-05-20: clicking "Issue Cert" on a job opened the wizard with a banner saying "Fischerscope file or readings needed — fill it in below before confirming", but the list view only showed status toggles (Needs Thickness / Is Ready). No upload affordance was visible. Operators had to know they could click a list row to expand into a hidden detail form where the upload field lived. The wizard model already had the file field, the .docx parser (_fp_parse_fischerscope_docx), and the @onchange that prefills readings — only the view was hiding it. Fix: promote the file upload into the list as its own editable binary column, alongside the existing Needs Thickness toggle. Operator now sees: Reference │ Type │ Customer │ Needs Thickness │ Fischerscope File (PDF or .docx) │ Parsed │ Ready Drop the file → onchange fires → readings + parsed summary populate in-row. Click "Confirm & Issue" to commit. The per-line expanded form is preserved (still accessible via row click) as a "details" panel for editing individual readings after upload — but the primary upload action is now in the list row where the operator's eyes are. Module: fusion_plating_jobs 19.0.10.15.0 → 19.0.10.16.0. 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.