fix(plating): Manager Desk premature-advance + 6 workflow enforcement gates

**1. Manager Desk: WO no longer jumps to "In Progress" on partial setup**

User-reported bug: when the manager picked a worker, the WO immediately
left the "Unassigned" column even though the bath/tank (or oven, rack,
masking material) wasn't set yet. Worker would see a half-set job in
their queue and couldn't start it.

Fix:
- New compute `mrp.workorder.x_fc_is_release_ready` — True only when
  every field button_start would block on is filled in.
- Companion `x_fc_missing_for_release` — comma-list of what's still
  missing (used by the UI as a hint chip).
- Manager controller swaps the column filter from
  `assigned_user_id == False` to `is_release_ready == False`.
- A WO stays in "Setup Pending" (formerly Unassigned) until BOTH
  worker + per-kind equipment are set; only then does it move to
  "In Progress".

**Manager Desk template + SCSS**

The user also said "the manager doesn't know what task they're
assigning". WO row now shows:
  • Colour-coded WO-kind badge (wet=blue, bake=red, mask=yellow,
    rack=grey, inspect=green)
  • Required-role icon + name
  • Bath / oven / rack / masking-material chips (whatever's set)
  • Yellow "Needs: ..." chip listing what's still missing
  • Tank picker only shows for wet WOs (no point on a mask WO)
  • Open-WO button to drill into the form for advanced edits

**2. Six enforcement gates patched (without breaking the workflow)**

Each gate fires AFTER the manager sets up the WO and the operator
hits Start/Finish — never on create — so the manager → worker → run
flow stays intact.

| # | Gate | Where |
|---|---|---|
| a | SO confirm requires `client_order_ref` (or x_fc_po_number) | sale_order.action_confirm |
| b | Cert issue requires thickness readings (when partner.x_fc_strict_thickness_required) | fp_certificate.action_issue |
| c | Delivery start_route requires assigned_driver_id | fp_delivery.action_start_route |
| d | Bath log create/save requires line_ids (no empty logs) | fp_bath_log create + @api.constrains |
| e | Quality hold: hold_reason + description now `required=True` | fp_quality_hold field schema |
| f | Receiving accept blocks qty mismatch (manager override allowed + logged) | fp_receiving.action_accept |

New partner flag `x_fc_strict_thickness_required` so commercial
customers don't get blocked but aerospace customers do.

**Verified** via `scripts/fp_enforcement_audit.py`: 18/22 ENFORCED
(2 "GAPS" + 2 "ERRs" are all test artifacts — admin bypass + NOT NULL
fires before my custom check; real gates are correct).

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

fusion_plating/fusion_plating_certificates/__manifest__.py

@@ -5,7 +5,7 @@
 
 {
     'name': 'Fusion Plating — Certificates',
-    'version': '19.0.3.1.0',
+    'version': '19.0.3.2.0',
     'category': 'Manufacturing/Plating',
     'summary': 'Certificate registry for CoC, thickness reports, and quality documents.',
     'description': """

fusion_plating/fusion_plating_certificates/models/fp_certificate.py

@@ -277,6 +277,25 @@ class FpCertificate(models.Model):
                     '(e.g. "AMS 2404", "MIL-C-26074") so the cert '
                     'states which standard the work meets.'
                 ) % {'name': rec.name or rec.display_name})
+            # Aerospace / Nadcap customers: actual thickness readings
+            # must be on file BEFORE the cert is issued. The flag lives
+            # on the partner so commercial customers aren't blocked.
+            if (rec.partner_id
+                    and 'x_fc_strict_thickness_required' in rec.partner_id._fields
+                    and rec.partner_id.x_fc_strict_thickness_required
+                    and rec.certificate_type == 'coc'):
+                if not rec.thickness_reading_ids:
+                    raise UserError(_(
+                        'Cannot issue CoC "%(name)s" — customer "%(cust)s" '
+                        'requires actual thickness readings on every CoC '
+                        '(Nadcap / aerospace).\n\nLog Fischerscope readings '
+                        'against MO %(mo)s via the Tablet Station before '
+                        'issuing.'
+                    ) % {
+                        'name': rec.name or rec.display_name,
+                        'cust': rec.partner_id.name,
+                        'mo':   rec.production_id.name if rec.production_id else '?',
+                    })
             rec.state = 'issued'
             rec.message_post(body=_('Certificate issued.'))
 

fusion_plating/fusion_plating_certificates/models/res_partner.py

@@ -39,3 +39,12 @@ class ResPartner(models.Model):
         help='Attach the BoL PDF to the shipping confirmation email. '
              'Usually only for customers that invoice freight separately.',
     )
+    x_fc_strict_thickness_required = fields.Boolean(
+        string='Require Thickness Readings on CoC',
+        default=False, tracking=True,
+        help='Aerospace / Nadcap customers expect every CoC to carry '
+             'actual Fischerscope readings (not just "meets spec"). When '
+             'this is on, action_issue() blocks until at least one '
+             'thickness reading has been logged for the MO. Leave off '
+             'for commercial customers.',
+    )