bc7c771f20
Specifications menu (urgent — workflow blocker for estimators): - Moved from Configuration → Quality & Documents (manager-only) up to Plating → Quality (sequence 70). Now visible to estimator, supervisor, and manager. - Renamed "Customer Specs" → "Specifications" — the seeded library includes industry standards (AMS, MIL, ASTM, BAC) not just customer-private specs. - Action display name updated: "Customer Specifications" → "Specifications". - Added action.help HTML so the empty-state placeholder explains the Specifications library purpose to first-time users. - Old xmlid (menu_fp_config_customer_spec) preserved so existing links / breadcrumbs / search references continue to resolve. Other clarifying renames: - Safety: "JHSC" / "JHSC Meetings" → "H&S Committee (JHSC)" / "H&S Committee Meetings" — acronym was opaque to non-Canadian H&S folks. - Operations: "Move Log" → "Parts & Rack Move Log" — generic name could be confused with chatter messages or stock moves. - Configuration → Recipes & Steps: "Workflow States" → "Job Workflow Stages" — generic name; clarifies these are job state milestones (passed-stage tracking), not generic workflow. - Compliance → General: child folder "Configuration" → "Reference Data" — three levels of "Configuration" nesting (Plating>Config vs Plating>Compliance>General>Config) was confusing. No model / data changes. Pure menu metadata. 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.