chore(menu): promote Specifications + clarify misleading menu names

Specifications menu (urgent — workflow blocker for estimators):
- Moved from Configuration → Quality & Documents (manager-only) up
  to Plating → Quality (sequence 70). Now visible to estimator,
  supervisor, and manager.
- Renamed "Customer Specs" → "Specifications" — the seeded library
  includes industry standards (AMS, MIL, ASTM, BAC) not just
  customer-private specs.
- Action display name updated: "Customer Specifications" → "Specifications".
- Added action.help HTML so the empty-state placeholder explains
  the Specifications library purpose to first-time users.
- Old xmlid (menu_fp_config_customer_spec) preserved so existing
  links / breadcrumbs / search references continue to resolve.

Other clarifying renames:
- Safety: "JHSC" / "JHSC Meetings" → "H&S Committee (JHSC)" /
  "H&S Committee Meetings" — acronym was opaque to non-Canadian
  H&S folks.
- Operations: "Move Log" → "Parts & Rack Move Log" — generic name
  could be confused with chatter messages or stock moves.
- Configuration → Recipes & Steps: "Workflow States" →
  "Job Workflow Stages" — generic name; clarifies these are job
  state milestones (passed-stage tracking), not generic workflow.
- Compliance → General: child folder "Configuration" → "Reference
  Data" — three levels of "Configuration" nesting (Plating>Config
  vs Plating>Compliance>General>Config) was confusing.

No model / data changes. Pure menu metadata.

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

fusion_plating/fusion_plating_quality/__manifest__.py

@@ -5,7 +5,7 @@
 
 {
     'name': 'Fusion Plating — Quality (QMS)',
-    'version': '19.0.6.0.0',
+    'version': '19.0.6.1.0',
     'category': 'Manufacturing/Plating',
     'summary': 'Native QMS for plating shops: NCR, CAPA, calibration, AVL, FAIR, '
                'internal audits, customer specs, document control. CE + EE compatible.',

fusion_plating/fusion_plating_quality/views/fp_customer_spec_views.xml

@@ -91,10 +91,35 @@
     </record>
 
     <record id="action_fp_customer_spec" model="ir.actions.act_window">
-        <field name="name">Customer Specifications</field>
+        <field name="name">Specifications</field>
         <field name="res_model">fusion.plating.customer.spec</field>
         <field name="view_mode">list,form</field>
         <field name="search_view_id" ref="view_fp_customer_spec_search"/>
+        <field name="help" type="html">
+            <p class="o_view_nocontent_smiling_face">
+                Add your first specification
+            </p>
+            <p>
+                The Specifications library holds every standard your
+                customers cite on POs — industry standards (AMS 2404,
+                ASTM B733, MIL-C-26074), prime-specific codes (Boeing
+                BAC 5680, Lockheed LMS-3045), and your own internal
+                references.
+            </p>
+            <p>
+                When an estimator picks a Specification on a sale order
+                line, the certificate auto-fills with the spec's code
+                and revision (e.g. "AMS 2404 Rev D"). Aerospace flags
+                (Nadcap required, FAI required, AS9100 clauses) drive
+                workflow gates downstream.
+            </p>
+            <p>
+                Add a new Specification the moment a new code shows up
+                on a customer PO — there's no need to wait for a
+                manager. Set the document URL so the controlled copy
+                is one click away during audits.
+            </p>
+        </field>
     </record>
 
 </odoo>

fusion_plating/fusion_plating_quality/views/fp_menu.xml

@@ -68,11 +68,18 @@
               action="action_fp_cal_event"
               sequence="60"/>
 
+    <!-- Promote-Customer-Spec (Phase F) — Specifications is now central
+         to order entry (estimators add new BAC / AMS / customer codes
+         when they hit them). Moved out of Configuration (manager-only)
+         into Quality where the workflow lives. Single menu, accessible
+         to estimator/supervisor/manager via the Quality top-level.
+         Old xmlid kept so links / breadcrumbs / search references
+         continue to resolve. -->
     <menuitem id="menu_fp_config_customer_spec"
-              name="Customer Specs"
-              parent="fusion_plating.menu_fp_config_quality_docs"
+              name="Specifications"
+              parent="menu_fp_quality"
               action="action_fp_customer_spec"
-              sequence="10"/>
+              sequence="70"/>
 
     <menuitem id="menu_fp_config_avl"
               name="Approved Vendor List"