feat(jobs): Phase 6 — Plant Overview kanban + Manager Dashboard

Two operator-facing client actions for the native job model.

Plant Overview: kanban with columns = fp.work.centre, cards = active
fp.job.step rows (ready/in_progress/paused). Drag a card to a different
column to reassign the step's work_centre_id; click to open the step
form. Backend: /fp/jobs/plant_overview returns columns with cards;
/fp/jobs/plant_overview/move_card reassigns work_centre.

Manager Dashboard: list of in-flight fp.job rows with progress bars,
deadline (overdue highlight), current_step / current_location, and a
priority side-bar (rush=red, high=orange, normal=blue, low=grey). Click
a row to open the job form. State-count pills filter by state. Backend:
/fp/jobs/manager_dashboard returns rows + state counts.

Both menu entries land inside the existing 'Plating Jobs (Native)'
submenu under the Plating app (manager-only). The menu items are
defined in this module rather than in fusion_plating core, because
the action xmlids they reference aren't loaded yet at the time the
core menu file is parsed (fusion_plating_jobs depends on core, not
the other way round).

Manifest 19.0.2.2.0 → 19.0.2.3.0. Three new SCSS, three new JS,
three new XML files registered in web.assets_backend.

Verified on entech: module loaded clean, all 41 fusion_plating_jobs
tests pass, asset bundle regenerates without errors, both menus and
both client actions registered in ir_ui_menu / ir_act_client.

Part of: native job model migration (spec 2026-04-25)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fusion_plating/fusion_plating_jobs/views/job_overview_actions.xml

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<odoo>
+    <!--
+        Phase 6 — operator-facing client actions for the native job model.
+
+        Plant Overview kanban:   columns = fp.work.centre, cards = fp.job.step
+        Manager Dashboard:       list of in-flight fp.job rows, by state
+
+        Menu items live here (not in fusion_plating core's fp_jobs_menu.xml)
+        because the action records they reference are defined in this
+        module — and fusion_plating_jobs is loaded AFTER core, so the
+        XML ids don't exist yet at the time core's menu file is parsed.
+    -->
+    <record id="action_job_plant_overview" model="ir.actions.client">
+        <field name="name">Plant Overview (Native)</field>
+        <field name="tag">fp_job_plant_overview</field>
+    </record>
+
+    <record id="action_job_manager_dashboard" model="ir.actions.client">
+        <field name="name">Manager Dashboard (Native)</field>
+        <field name="tag">fp_job_manager_dashboard</field>
+    </record>
+
+    <menuitem id="menu_fp_jobs_plant_overview"
+              name="Plant Overview (Native)"
+              parent="fusion_plating.menu_fp_jobs_native_root"
+              action="action_job_plant_overview"
+              sequence="5"/>
+
+    <menuitem id="menu_fp_jobs_manager_dashboard"
+              name="Manager Dashboard (Native)"
+              parent="fusion_plating.menu_fp_jobs_native_root"
+              action="action_job_manager_dashboard"
+              sequence="7"/>
+</odoo>