e37eab9f23
User reproduced on WH/JOB/00342: clicked Start on Incoming Inspection
while Contract Review was still in_progress. Sub 13 should have raised
UserError. It didn't. Both steps ended up in_progress.
Investigation:
$ grep "def button_start" fusion_plating_jobs/models/fp_job_step.py
88: def button_start(self): ← Sub 13 gate code
876: def button_start(self): ← Policy B + Sub 8 (older)
Two definitions of the same method in the same class. Python uses the
SECOND. My Sub 13 gate at line 88 was dead code from the moment it
landed. WH/JOB/00342's Contract Review and Incoming Inspection both
ran in_progress because the live button_start (line 876) only did
Policy B Contract Review auto-open and Sub 8 Racking auto-open — no
predecessor check.
Fix:
* Removed the duplicate button_start at line 88 (left a marker
comment so the next person doesn't redo this footgun)
* Merged the Sub 13 predecessor gate AND the receiving soft check
into the line-876 button_start so all four behaviours run from
one method:
1. Predecessor gate (raise UserError if blocking)
2. Contract Review auto-open (route to QA-005)
3. Racking auto-open (route to inspection)
4. super().button_start() + receiving check + serial promotion
Helpers _fp_should_block_predecessors / can_start / _compute_can_start
preserved (used by view + Move wizard too).
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.