# Fable handoff prompt — CM Invoice rethink/fix pass
> Generated 2026-07-01 · paste EVERYTHING below the line into a brand-new Fable session.

---

Hey Fable. Saying hello, and I want you focused on the CM ("Centimeters" = C&M Collection) invoice repo, its MD files, the contacts, and everything we've discussed. Rethink it. Keep in mind what I actually need, see what's good vs not good here, broken vs not broken, and fix it. Do the super-duper thing you do well. Feel free to communicate with me and the bot as you go.

Here's the exact context so you don't rediscover it or misstep (this is a LIVE financial tool my widowed mother uses):

## What this is
CM_Invoice_System is my mother Rivka's wholesale-clothing invoicing tool (C&M Collection Intl LLC). She's a drained widow who works DIRECTLY in the sheet. Design test for every choice: "would this exhaust her?" If yes, cut it. Target: her whole daily cadence runs in ~6 clicks, unbreakable, without me.

## Read first (don't rediscover)
- `CM_Invoice_System/Code.js` (v3, ~5,530 lines) — the engine.
- `CM_Invoice_System/CM_FAMILIAR_REBUILD_PLAN.md` — the current plan + the LIVE STATUS block at top.
- `CM_Invoice_System/CM_MOM_SOP_EN_HE.md` — her bilingual daily SOP (her actual steps).
- `docs/MOM_INVOICE_BUILD_SPEC.md` + memory `project_mom_context.md` — the real stakes + her cadence.
- `outputs/2026-06-10_17-26_mockup_cm-invoice-familiar.html` — the APPROVED "looks like her old Excel" target (Fame #1158).
- `outputs/2026-06-30_15-16_action_cm-invoice-when-youre-back.html` — the current runbook.
- Run `cmProbe()` (headless diagnostic in Code.js) to read the LIVE Invoice_Entry tab state before changing anything.

## Live state (verified 2026-06-30 / 07-01)
- Live sheet = CM Invoice System_v2 (`1nMTEl_eYpAsQ774Qe0MNEcbib8Qgj2X6_9PfeZk32iI`), bound Apps Script `106wdSg6…`. REAL data: 90 customers, saved invoices, per-customer Drive folders. She has used it.
- **Tier 1 (familiar wording) is LIVE** — I ran Setup/Repair; the Invoice_Entry tab now shows ORDER FOR, Reference, Deposit/Balance, Comments, the 32–52 size grid, yellow input cells, Tax hidden, warning-only protections.
- **Tier 2 is PENDING a verified apply:** customer block → top-right, big plain NUMBER instead of the word "INVOICE", plain white styling instead of the navy chrome. The exact A11-remap lockstep is written in `CM_FAMILIAR_REBUILD_PLAN.md` §A.

## Locked decisions (don't relitigate)
Number = plain running number shown, smart `INV-…` code hidden (PDF filename only). Totals = Total / Deposit / Balance. Her wording (ORDER FOR / Reference). Customer block top-right. White-Excel styling.

## Mom's cadence
Works in the tab directly; types ONLY the yellow cells (blue/gray auto-fill). Enters per-size buckets (32–52) per style; Qty auto-sums. Orders are NOT Invoices (an order is committed-but-not-shipped). I handle chargebacks/short-pays, never her.

## Hard constraints — LIVE financial tool
1. **Rule 10:** verify any structural / number / totals change on a SACRIFICIAL test invoice first — `seedTestCustomers` → build one test invoice → confirm the number, the PDF, and the totals all tie out → `clearTestData` — BEFORE any real invoice. Never blind-push a primary-key or totals-math change.
2. **Fix the source** (`Code.js`), then apply via CM Admin → Setup/Repair, then verify. Don't hand-edit the live sheet.
3. **Deploy:** `clasp push` from `CM_Invoice_System/` (it's a nested git repo, self-managed) to bound script `106wdSg6…`; changes take effect when Setup/Repair runs. CM repo is clean at `5e2a45a`.
4. **Parallel sessions** run at the same time — rebase before pushing the workspace repo; commit only CM files; leave other sessions' uncommitted files alone (e.g. `ops-api/.gitignore`).

## "Super duper" = go past the cosmetic polish
Genuinely rethink the whole thing, not just Tier 2 styling:
- Is the invoice numbering right? (`INV-NNN-CUSTCODE` vs the 3 competing modes — FORMULA/GLOBAL/PER_CLIENT — pick ONE canonical and kill the drift.)
- Are Orders vs Invoices cleanly separated (two numbering streams, order → invoice conversion)?
- Is the buyer-facing PDF (`_buildPrintView`) clean and matching the approved mockup?
- Any bugs, dead code, half-built menus, stale docs, wrong/duplicate contacts, broken protections?
- Then get every fix verified-live. Leave it so she can run her full cadence without me.

## Communicate
- Text me: `powershell -File scripts/tg.ps1 -Source Fable -Title "..." -Message "..."` (use `\n` for newlines). (If `-Source Fable` isn't wired yet, use `-Source Code`.)
- Outputs → `outputs/` committed (portal-first).
- Before executing, give me a tight "here's what's solid / what's broken / what I'll do" so I see the plan first.

Go do the super-duper thing. Ask me only if you hit a real fork.