feat(jobs): Sub 13 sequential step enforcement + Sub 12e v3 wizard

Two coherent feature drops shipping together because their fp_job_step
edits overlap. Both target operator workflow correctness.

## Sub 13 — Sequential step enforcement (recipe + per-step)

Background:
  Investigation on WH/JOB/00339 showed operators starting Incoming
  Inspection while Contract Review was still in_progress. Audit:
  98.7% of recipe operations system-wide had requires_predecessor_done
  = false (the legacy per-step opt-in defaults off, recipe authors
  rarely tick the box).

Architecture:
  Recipe-level toggle + per-step opt-out (Option A from /investigate).
  * fusion.plating.process.node.enforce_sequential — Boolean on the
    recipe root. Default True. When True, every operation under this
    recipe waits for earlier-sequence steps to finish before it can
    start.
  * fusion.plating.process.node.parallel_start — Boolean on operation
    nodes. When True, this step bypasses the sequential gate (e.g.
    paperwork or QA review that runs alongside production).
  * Mirrored on fp.step.template (parallel_start) so library steps
    carry the flag into snapshots.
  * fp.job.enforce_sequential — related from recipe_id. Snapshotted
    at job creation so a recipe author flipping the recipe's flag
    AFTER job generation does NOT change behaviour mid-run.
  * fp.job.step.parallel_start — related from recipe_node_id.
  * Decision matrix (encapsulated in
    fp.job.step._fp_should_block_predecessors):
        recipe.enforce_sequential | step.parallel_start | step.req_pred_done | block?
        --------------------------|---------------------|--------------------|------
                 True             |       False         |        any         |  YES
                 True             |       True          |        any         |   no
                 False            |        any          |       True         |  YES
                 False            |        any          |       False        |   no
  * Manager bypass via context fp_skip_predecessor_check=True (existing).

Runtime gates:
  * fp.job.step.button_start — calls _fp_should_block_predecessors;
    raises UserError naming the blocking earlier step(s).
  * fp.job.step.can_start — computed Boolean for view-side disable.
  * Move wizard predecessor check
    (fusion_plating_shopfloor/controllers/move_controller.py) — uses
    the same helper so tablet + backend behave identically.

UI surface:
  * Recipe form (fp_process_node_views.xml) — enforce_sequential
    toggle on recipe root, parallel_start checkbox on operations.
  * Step template form — parallel_start checkbox.
  * Simple Recipe Editor (inline library form) — Parallel Start
    checkbox + legacy flag demoted with muted styling + supervisor
    group gate.
  * Recipe Tree Editor (properties panel) — both flags exposed,
    only-show on the right node_type.
  * Controllers updated to allowlist + payload the new fields.

Migration:
  fusion_plating/migrations/19.0.18.12.0/post-migrate.py — sets
  enforce_sequential = TRUE on every existing recipe-root node.
  Idempotent. User confirmed dev-stage data, so retroactive flip
  is safe (no production jobs to disrupt).

Tests:
  TestSequentialEnforcement (10 tests) covering:
    * sequential mode blocks out-of-order start
    * first step always startable
    * predecessor finish/skip unlocks next
    * parallel_start opts out of gate
    * free-flow mode bypasses gate
    * legacy requires_predecessor_done still honoured in free-flow
    * manager bypass via context
    * can_start compute reflects state correctly
    * library template parallel_start snapshots into recipe-node

## Sub 12e — Record Inputs Wizard v3 (card layout, dark-mode aware)

Background:
  v2 wizard was a 17-column wide editable table. Operators got lost
  finding which value column applied to their row's type, horizontal
  scroll required on tablets, composite types crammed into one row.

New layout:
  * Each measurement renders as a stacked card (CSS Grid + display
    transformation on the existing list widget — preserves inline
    editing, no JS rewrite).
  * Card header: prompt name (large, bold) + type/unit pills.
  * Card body: ONLY the value widget for this row's type
    (number / boolean / date / text / photo / multi-point / panel).
  * Composite types (multi-point thickness 5x reading + avg, bath
    panel 4 fields) get inline sub-grid inside the card.
  * Empty state ("no measurement prompts") with friendly CTA.

Dark mode:
  * SCSS branches at compile time on $o-webclient-color-scheme
    (per fusion-plating/CLAUDE.md note).
  * Tokens: 7 surface colours + 4 ink levels with light/dark hex
    pairs, all behind var(--fp-*) custom properties for per-deploy
    override.
  * Registered in BOTH web.assets_backend AND web.assets_web_dark
    so each bundle compiles its own palette.

Tablet polish:
  @media (max-width: 900px) — collapse meta below prompt + bump
  numeric input min-height to 56px.

Defensive:
  * v2 view kept in the XML file (instant rollback by changing one
    view_id ref).
  * `:has(.o_invisible_modifier)` rule drops empty cells out of the
    grid so Odoo's invisible="..." doesn't punch holes in layout.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating/migrations/19.0.18.12.0/post-migrate.py

@@ -0,0 +1,70 @@
+# -*- coding: utf-8 -*-
+# Copyright 2026 Nexa Systems Inc.
+# License OPL-1 (Odoo Proprietary License v1.0)
+# Part of the Fusion Plating product family.
+"""
+Migration 19.0.18.12.0 — Sub 13 sequential step enforcement.
+
+Background:
+  The legacy per-step `requires_predecessor_done` opt-in defaulted to
+  False, so 98.7% of operations system-wide had no enforcement and
+  operators were able to start arbitrary steps out of order (e.g. job
+  WH/JOB/00339 — Incoming Inspection ran while Contract Review was
+  still in progress).
+
+This migration:
+  * Sets `enforce_sequential = True` on every existing recipe-root
+    node so the new default behaviour kicks in immediately on upgrade.
+    Existing per-step `requires_predecessor_done` flags are preserved
+    and continue to work for any recipe whose author opts back into
+    free-flow mode (sets enforce_sequential = False).
+
+Idempotent — safe to re-run.
+"""
+
+import logging
+
+_logger = logging.getLogger(__name__)
+
+
+def migrate(cr, version):
+    if not version:
+        return  # Brand new install — defaults already correct.
+
+    _logger.info(
+        '[migration 19.0.18.12.0] Promoting all existing recipes to '
+        'enforce_sequential=True (Sub 13 — sequential step enforcement).'
+    )
+
+    # Direct SQL — avoids loading the ORM at this stage and is fast.
+    # We intentionally only flip nodes that are CURRENTLY False; nodes
+    # already set True (or set by a manual install of a newer version)
+    # are skipped so the operation is clean to re-run.
+    cr.execute("""
+        UPDATE fusion_plating_process_node
+           SET enforce_sequential = TRUE
+         WHERE node_type = 'recipe'
+           AND (enforce_sequential IS NULL OR enforce_sequential = FALSE)
+    """)
+    flipped = cr.rowcount
+    _logger.info(
+        '[migration 19.0.18.12.0] enforce_sequential flipped to True '
+        'on %d existing recipe(s).', flipped,
+    )
+
+    # Audit chatter on each affected recipe so the change is visible
+    # to recipe authors (they get a notification on their next visit).
+    if flipped:
+        cr.execute("""
+            SELECT id, name FROM fusion_plating_process_node
+             WHERE node_type = 'recipe' AND enforce_sequential = TRUE
+        """)
+        recipes = cr.fetchall()
+        _logger.info(
+            '[migration 19.0.18.12.0] %d recipe(s) now Sequential by default. '
+            'Affected recipes: %s',
+            len(recipes),
+            ', '.join(name for _, name in recipes[:20]) + (
+                ', ...' if len(recipes) > 20 else ''
+            ),
+        )