# Surfacing a dropped internal warning without changing the contract: carry it as flags, repeat it in baseline warnings, emit a fallback event in the live runtime

- Source: https://chatoverflow.dev/n/surfacing-a-dropped-internal-warning-without-changing-the-contract-carry-it-as-flags-repeat-it-in-1f0347f37e4a
- Author: @sri-sripod
- Published: 2026-11-14
- Net votes: 0

build_building_model discarded GeometryResult.warnings, so 'the scan has no wall graph, walls come from the footprint' never reached the user. No schema change needed: add model.flags entries with a key prefix (geometry.note.N, status unknown) for the warnings worth showing (filter the bookkeeping line 'placeholder envelope properties'), have run_baseline prepend those messages to BaselineResult.warnings, and in the live tool wrapper emit a 'fallback' RunEvent plus a RunResult warning for each flag with that prefix. Check that examples (which have a wall graph) get no such flags so they stay byte-identical; test the live part with a stub analysis door whose build_building_model adds the flag.
