Split 49 modules/suites into independent git repos; untrack from monorepo

Each top-level module/suite folder is now its own private repo on GitHub
(gsinghpal/<name>) and gitea (admin/<name>), with a fresh single initial
commit. The monorepo no longer tracks them (added to .gitignore + git rm
--cached); working-tree files are retained on disk and managed in their
own repos. The monorepo keeps shared root files (CLAUDE.md, docs/, scripts/,
tools/, AGENTS.md, WIP/obsolete dirs) and full history.

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

fusion_plating/fusion_plating_culture/README.md

@@ -1,53 +0,0 @@
-# Fusion Plating — Culture & Values
-
-Part of the Fusion Plating product family by Nexa Systems Inc.
-
-A configurable culture / values / fundamentals framework for plating and
-metal finishing shops. Each shop loads its own values — this module ships
-with no client-specific seed data.
-
-## What it gives you
-
-- **Value Sets** — a named collection of a shop's values (e.g. "Our Way",
-  "The 24 Fundamentals", "Core Behaviours"). A company can have several
-  sets, but usually one is marked as primary.
-- **Values** — individual fundamentals, core behaviours, or beliefs, each
-  with a short title, long-form description, stories/examples, icon, and
-  display number.
-- **Rotations** — a schedule that surfaces a "Fundamental of the
-  Day/Week/Month". The shop admin decides whether to enable an ir.cron
-  (none ships in this module) to advance rotations automatically.
-- **Recognitions** — peer shout-outs tied to a specific value. "I saw
-  Sarah living Value #3 today when she stayed late to finish a customer
-  order." Recognitions flow into an employee's Culture tab on their HR
-  record.
-
-## Installation
-
-1. Install `fusion_plating` (core) and `hr` first.
-2. Install `fusion_plating_culture`.
-3. Go to **Plating → Culture → Configuration → Value Sets** and create
-   your shop's set.
-4. Add values to that set.
-5. (Optional) Create a rotation schedule if you want a
-   fundamental-of-the-week rotation.
-
-## Design notes
-
-- **Not client-specific.** Nothing ships with Entech, Westin, or any
-  particular shop's language baked in. Each shop loads its own.
-- **Reuses core groups.** No new security groups — operator reads,
-  supervisor creates recognitions, manager configures value sets.
-- **Theme-aware.** SCSS uses Bootstrap CSS variables so kanban tiles and
-  recognition cards render cleanly in both light and dark mode.
-- **hr.employee extension uses `x_fc_` prefix** per the Fusion Central
-  field-naming convention for base Odoo model extensions.
-
-## Dependencies
-
-- `fusion_plating` — core
-- `hr` — for employee extension and recognition targeting
-
-## License
-
-OPL-1 (Odoo Proprietary License v1.0) — Copyright 2026 Nexa Systems Inc.