Otto workbook and anomaly reports

2026.10.27-otto-classeur-et-signalements-slack · 2026-10-27

Delivered build : 148f9576e2ec7a40c3c881555281ca781d0567c0

Changes

• Otto now reads the note attached to the context before creating the workbook and proposes row titles (titreLigne) and values (saisir) in a single pass. The banner stays visible at confirmation, the zod schema validation error message is clearer, and the response says "proposed on screen" rather than wrongly claiming "entered".
• Each report posts to a third-party team messaging channel (best effort) with the last ten minutes of logs: console errors, failed requests and visited pages (client), plus 4xx and 5xx errors on user requests (server). Tokens, email addresses and query parameters are redacted. Migration 20261217600000: jsonb logs column on bug_reports.

Known limitations

• Application deployed on multiple server containers: each server keeps its buffer in local memory. The client buffer covers only fetchJSON requests, not multipart imports, fetchBlob or notifications. The messaging channel call has not been tested with a real webhook or in an end-to-end browser test. The Otto graph likely shows a single bar (one column, four rows) without visual verification. Reports are visible in the support channel support team.