docs(plating): flag fusion_plating_culture as do-not-auto-install

Future sessions shouldn't silently re-install retired modules during
install/upgrade sweeps. Added an explicit "Retired / Do-Not-Install
Modules" section with guardrails:

- Don't include in -i / -u sequences
- Don't add as a depends target
- Don't re-sync to entech /mnt/extra-addons/custom/
- Don't recommend installing without user confirmation

Covers the two modules currently in this state:
- fusion_plating_culture (code in repo, uninstalled on entech)
- fusion_plating_sensors (fully removed, absorbed into fusion_iot)

Also struck-through the "| 80 | Culture | ..." menu row and added a
retired tag to the module-list tree so at-a-glance scans don't
suggest it's a live part of the menu hierarchy.

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

fusion_plating/CLAUDE.md

@@ -25,7 +25,7 @@ fusion_plating_cgp/                 — Controlled Goods Program
 fusion_plating_safety/              — SDS, WHMIS, JHSC
 fusion_plating_quality/             — QMS (NCR, CAPA, calibration)
 fusion_plating_logistics/           — Pickup & delivery, chain of custody
-fusion_plating_culture/             — Values / fundamentals
+fusion_plating_culture/             — Values / fundamentals (⚠️ RETIRED — do NOT auto-install)
 fusion_plating_bridge_mrp/          — MRP integration (recipe→WO, portal job, work order priorities)
 fusion_plating_bridge_sign/         — Digital signatures
 fusion_plating_bridge_quality/      — Quality bridge
@@ -56,13 +56,26 @@ The Plating app (`menu_fp_root`, seq 46) has these top-level menus:
 | 60 | Aerospace | fusion_plating_aerospace | AS9100, Nadcap, Counterfeit, Config Items, Risk |
 | 65 | Nuclear | fusion_plating_nuclear | Program, ITP, 10CFR21, Pedigree, CNSC |
 | 70 | CGP | fusion_plating_cgp | Registration, AI, PSA, Visitors, Goods, Shipments, Security, Access Log |
-| 80 | Culture | fusion_plating_culture | Values, Recognitions |
+| ~~80~~ | ~~Culture~~ | ~~fusion_plating_culture~~ | ~~Values, Recognitions~~ **— RETIRED, uninstalled on entech, code kept in repo only** |
 | 90 | Configuration | fusion_plating (core) + many | Facilities, Work Centres, Process Categories/Types, Bath Params, Stations, Ovens, Invoice Strategy, Account Holds, Training Types, Chemicals, Notification Templates/Log, Calibration, Specs, AVL, Value Sets/Rotations, N299 Levels, Vehicles |
 
 **Field Service** (`fusion_tasks`) also has its own standalone root app (seq 45) with Map View, Tasks, Calendar, Configuration. The same task actions are also accessible under Plating > Logistics.
 
 **Key rule**: Sales menu is unified in `fusion_plating_configurator`. Portal module adds Quote Requests + Portal Jobs as children (referencing `fusion_plating_configurator.menu_fp_sales`). Do NOT create a separate Sales menu in portal.
 
+## Retired / Do-Not-Install Modules
+
+These modules have **source code in this repo** but are **intentionally NOT installed on entech** (the client's live Odoo). Do not:
+- Include them in any `-i` or `-u` sequence that installs modules automatically.
+- Add them as a `depends` target from any other Fusion Plating module.
+- Re-sync their folders to `/mnt/extra-addons/custom/` on entech.
+- Recommend installing them to the user without explicit confirmation.
+
+| Module | State on entech | Retired because | What to do if revisiting |
+|--------|-----------------|-----------------|--------------------------|
+| `fusion_plating_culture` | `state=uninstalled`, dir removed from entech disk | Soft people-ops feature (peer kudos / "Fundamental of the Week"); zero data entered; not a client priority. Top-level "Culture" menu confused operators. | Ask the client whether they want it before reinstalling. If yes: re-sync folder + `-i fusion_plating_culture` + seed a value set. |
+| `fusion_plating_sensors` | deleted entirely (not in repo anymore) | Duplicated `fusion_plating_iot`'s scope but with no working alerting logic. Its valuables (sensor_type taxonomy, dashboard, location flexibility) were ported into `fusion_iot/fusion_plating_iot/`. | N/A — gone. Any new sensor work goes in `fusion_iot/fusion_plating_iot/`. |
+
 ## Critical Rules — Odoo 19
 1. **NEVER code from memory** — Read reference files from the server first.
 2. **Backend OWL**: `static template`, `static props = ["*"]`, standalone `rpc()` from `@web/core/network/rpc`. NOT `useService("rpc")`.