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_receiving/models/fp_receiving.py

@@ -108,12 +108,32 @@ class FpReceiving(models.Model):
             rec.received_date = fields.Datetime.now()
 
     def action_accept(self):
-        """Accept the receiving — parts match and condition is OK."""
+        """Accept the receiving — parts match and condition is OK.
+
+        Quantity-mismatch policy: if expected_qty != received_qty,
+        operators must use action_flag_discrepancy() instead. Managers
+        can override (the override is logged on chatter for audit).
+        """
+        is_manager = self.env.user.has_group(
+            'fusion_plating.group_fusion_plating_manager'
+        )
         for rec in self:
             if rec.state not in ('inspecting', 'resolved'):
                 raise UserError(_('Can only accept from Inspecting or Resolved state.'))
             if rec.unresolved_damage_count > 0:
                 raise UserError(_('Cannot accept — there are %d unresolved damage entries.') % rec.unresolved_damage_count)
+            qty_match = rec.expected_qty > 0 and rec.received_qty == rec.expected_qty
+            if not qty_match:
+                if not is_manager:
+                    raise UserError(_(
+                        'Cannot accept — quantity mismatch (expected %(exp)d, '
+                        'received %(rcv)d).\n\nUse "Flag Discrepancy" instead, '
+                        'or have a manager override.'
+                    ) % {'exp': rec.expected_qty, 'rcv': rec.received_qty})
+                rec.message_post(body=_(
+                    'Manager override: accepted with quantity mismatch '
+                    '(expected %(exp)d, received %(rcv)d).'
+                ) % {'exp': rec.expected_qty, 'rcv': rec.received_qty})
             rec.state = 'accepted'
             rec._update_so_receiving_status()
             rec.message_post(body=_('Parts accepted — quantity: %d, all checks passed.') % rec.received_qty)