feat(fusion_repairs): Bundle 8 - rush service + emergency pricing + parts-ordered workflow

The grumpy-old-customer-with-broken-stairlift scenario. Four real workflows
the office faces every week, with comms baked in so the client never has to
call back asking for status.

NEW MODELS
- fusion.repair.emergency.charge (rate card)
  Per (category, tier) rate with per_tech_multiplier; 5 tiers
  (same_day / next_day / after_hours / weekend / holiday). Each category
  can have its own rates - bed motors need 2 techs, stairlift is single.
  Seeded with realistic Westin rates: stairlift same-day $250, weekend
  $450; porch lift same-day $300; bed same-day $175 with 0.6 multiplier
  (2-tech jobs frequent); powerchair same-day $200.

- fusion.repair.part.order (procurement-facing record)
  One per distinct part the tech needs from the manufacturer. Carries
  description + OEM # + manufacturer + quantity + photos + notes.
  4-state lifecycle: draft -> ordered -> received -> fitted (or
  cancelled). On state transitions:
    draft -> ordered:  email client "ordered, expected by X"
    ordered -> received: email client "arrived, scheduling return visit"
                         + auto-create follow-up dispatch task when ALL
                         outstanding parts on the repair have arrived.

REPAIR.ORDER EXTENSIONS
- Rush fields: x_fc_rush_requested, x_fc_rush_tier,
  x_fc_rush_techs_required, x_fc_rush_surcharge (computed via rate card),
  x_fc_rush_acknowledged_at + x_fc_rush_acknowledged_by_id (audit trail
  proving CS got verbal OK before charging).
- Parts-awaiting fields: x_fc_parts_awaiting + x_fc_parts_eta_date +
  x_fc_part_order_ids One2many + x_fc_part_order_count.

- New methods:
  * action_acknowledge_rush() - one-click "client agreed" with audit.
  * action_squeeze_into_today() - picks the lightest-loaded skilled tech,
    finds their first free 1-hour slot between 9am-6pm, schedules the
    task in it, sends:
      1) live bus.bus push to the tech (sticky notification in their
         web client - so they see it MID-SHIFT)
      2) rush-alert email (force_send=True - this can't wait in the queue)
      3) chatter post on the tech task itself
    Validates against fusion_tasks' time-conflict rule by passing
    force_schedule via context (intake.service honours it).
  * action_view_part_orders() - smart button.

WIZARD EXTENSIONS
- repair.intake.wizard:
  New rush_requested + rush_tier + rush_techs_required + rush_acknowledged
  controls. Live rush_surcharge_preview compute shows CS the price in
  real-time as they change category / tier / tech count. Yellow alert
  reminds CS to read the price to the client BEFORE submitting.

- repair.visit.report.wizard:
  New outcome radio: completed / parts_needed / rescheduled.
  When outcome=parts_needed, needs_parts_line_ids One2many appears for
  the tech to capture each part (description, OEM, manufacturer, qty,
  lead days, notes, photos). On submit each line creates a
  fusion.repair.part.order, the repair flips to x_fc_parts_awaiting=True
  with an ETA, and the client gets the "we found the problem, here's the
  plan" email immediately.

INTAKE SERVICE
- _create_dispatch_task now honours force_schedule (date + time_start +
  time_end) via context so squeeze + auto-redispatch don't crash on
  fusion_tasks' time-window validator.
- _create_single_repair carries rush_requested/tier/techs through to
  the new repair fields.

MAIL TEMPLATES (4 new)
- email_template_rush_tech_alert: red 4px accent, address + phone + the
  $surcharge - what the tech needs to know mid-shift.
- email_template_repair_awaiting_parts: amber accent, "we found the
  problem, parts ordered, return visit ~ETA, no action needed".
- email_template_parts_ordered: blue, per-part confirmation.
- email_template_parts_received: green, "arrived, office will call to
  confirm visit".

UI / NAVIGATION
- Backend wizard: rush controls + live surcharge preview + verbal-OK alert.
- repair.order form: new Rush / Parts notebook tab with all the fields
  + linked part orders list. Two new header buttons (Squeeze into
  Today / Client Agreed to Rush Price). Two new search filters
  (Rush, Awaiting Parts).
- Part Order form: statusbar with the 4 transitions + Cancel; notes +
  photos notebook tabs; full chatter for audit.
- Menus: 'Parts to Order' under root; 'Emergency Surcharges' under
  Configuration.

SECURITY
- 8 new ACL entries (emergency_charge user/manager; part_order
  user/dispatcher/manager/technician; visit_report partline for office
  and field tech). Office sees parts but only managers can edit
  emergency rates.

Verified end-to-end on local westin-v19 - all 4 scenarios green:
  S1 Same-day rush stairlift -> $250 surcharge, ack stamped, squeeze
     assigned garry@ at first free 1h slot today, alert email queued,
     chatter posted.
  S2 Next-day priority bed -> $0 surcharge (no rate seeded for bed
     next_day - office can configure), 4 emails queued (client + office).
  S3 2-tech weekend stairlift -> $675 (450 base + 0.5x base for 2nd tech).
  S4 Parts-needed visit-report -> 2 PART-#### records created, repair
     awaiting_parts=True, ETA=2026-06-06, office activity scheduled,
     client email sent. Marking part ordered -> client mail. Marking
     all parts received -> auto-dispatch follow-up + client mail.

Bumped to 19.0.1.9.1.

Co-authored-by: Cursor <cursoragent@cursor.com>

fusion_repairs/models/intake_service.py

@@ -70,6 +70,9 @@ class FusionRepairIntakeService(models.AbstractModel):
 
         equipment = payload.get('equipment_items') or [{}]
         quote_only = bool(payload.get('quote_only'))
+        rush_requested = bool(payload.get('rush_requested'))
+        rush_tier = payload.get('rush_tier') or False
+        rush_techs_required = int(payload.get('rush_techs_required') or 1)
         repairs = self.env['repair.order']
         for item in equipment:
             repair = self._create_single_repair(
@@ -79,6 +82,9 @@ class FusionRepairIntakeService(models.AbstractModel):
                 source=source,
                 item=item,
                 quote_only=quote_only,
+                rush_requested=rush_requested,
+                rush_tier=rush_tier,
+                rush_techs_required=rush_techs_required,
             )
             repairs |= repair
 
@@ -107,7 +113,9 @@ class FusionRepairIntakeService(models.AbstractModel):
     # ------------------------------------------------------------------
     @api.model
     def _create_single_repair(self, partner_id, intake_user, session_ref,
-                              source, item, quote_only=False):
+                              source, item, quote_only=False,
+                              rush_requested=False, rush_tier=False,
+                              rush_techs_required=1):
         Repair = self.env['repair.order']
         product_id = item.get('product_id')
 
@@ -123,6 +131,9 @@ class FusionRepairIntakeService(models.AbstractModel):
             'x_fc_urgency': item.get('urgency') or 'normal',
             'x_fc_issue_category': item.get('issue_category') or False,
             'x_fc_is_quote_only': bool(quote_only),
+            'x_fc_rush_requested': bool(rush_requested),
+            'x_fc_rush_tier': rush_tier or False,
+            'x_fc_rush_techs_required': rush_techs_required or 1,
             'internal_notes': self._wrap_internal_notes(item),
         }
         if product_id:
@@ -432,11 +443,17 @@ class FusionRepairIntakeService(models.AbstractModel):
                 'x_fc_repair_order_id': repair.id,
                 'description': repair.internal_notes or repair.name,
             }
+            # Bundle 8: allow squeeze / re-dispatch callers to inject a
+            # specific scheduled_date + time_start + time_end via context so
+            # fusion_tasks' conflict validator doesn't reject the create.
+            force_sched = self._context.get('force_schedule') or {}
+            if force_sched:
+                vals.update(force_sched)
             # technician_id is required AND constrained to x_fc_is_field_staff.
             # D2: prefer a tech whose x_fc_repair_skills covers this repair's
             # category. Falls back to ANY active field-staff user if no skilled
             # tech exists, then to the lowest-id field-staff user as a placeholder.
-            tech_id = self._pick_dispatch_technician(repair)
+            tech_id = self._context.get('force_tech_id') or self._pick_dispatch_technician(repair)
             if not tech_id:
                 _logger.warning(
                     'No field-staff user available - skipping auto-dispatch '