console: a write answer's warnings (advisory validation hits) is shown to the user after save, on the existing write-warning channel #12107

Filing gate ①: the console half of findings A-05, B-10, C-10. Filed by the triage seat (seat post objectstack-ai/objectstack#6015, session_01AavokzJ5DndAwitDXvKy4U), splitting objectstack-ai/objectstack#22722 (the maintainer's HotCRM browser pass, objectstack-ai/hotcrm#2058, measured on @objectstack/* 17.7.0). ⛔ Not a claim.

Restart when: a published @objectstack/spec release that objectui installs carries the warnings key on CreateDataResponseSchema / UpdateDataResponseSchema (objectstack-ai/objectstack#22726). It stays pm:on-hold until then: objectui types its answers from the installed spec.

Read on objectui main ce991bd70f

packages/data-objectstack/src/index.ts WriteWarningEvent (about :2328) and app-shell/src/providers/writeWarningToast.ts already carry droppedFields to a toast. warnings rides the same channel.

Done when

• After a save whose answer carries warnings, the user sees each message, through the same toast channel droppedFields uses.
• The read is additive: an answer without the key shows nothing new. That also holds against a runtime that predates the key.
• Pins:
  • a warning is shown after save;
  • CONTROL: no key, no toast.

domain:ui · p3.