Brick 32: customer registry + folders + search — filing brick A

kerfmaster pin list · UI / workflow decisions

recordStates what the code does today. Auditable against the code — this is the only type that can go stale.

Content last changed 2026-09-02 — computed from the item itself, not typed.

Built 2026-09-02 (Jordan 'go ahead and record it... start building the build blocks'). The first brick of the jobs-home-filing ruling.

• Server: customers.json registry (GET/POST /api/customers — blank or case-insensitive-duplicate name refuses in honest words); POST /api/jobs/<id>/file binds customer + order_ref on job.json (annotation only, no stage record; unknown customer refuses; clearing removes). Order ref deliberately free text per the ruling.
• Home: jobs grouped under collapsible customer folders (collapse state per station, like theme/units; Unfiled first — it's the needs-attention pile); search box covers job name, id, customer name, order reference and EVERY program number on the record (onum/onums/pl_onums/cl_onums walked recursively) — typing 33291 finds the customer and job it belongs to, the severed-link fix; searching opens all folders and shows match counts. file… button on every row: pick or add a customer inline, type the order ref; the ref rides the row as a chip; an open job's topbar reads 'Customer · job name'.
• Sweep: 101 verify/test fixture jobs filed under 'KerfMaster internal tests'; b7787, nav209, ex2_dirty left unfiled for Aristide/Jordan to place (their data, not ours to seed).

Verified live over the public URL (Playwright): folders + counts, collapse persists, O-number search finds nav209 by 33291, file-and-search round trip, topbar prefix; verify's test customer removed after (registry discipline). Honest limits: workflow queues, rules/training, thumbnails, reorder fast path = the next bricks; 'who filed' awaits operator accounts.