html-confirm, HTML when there is something to SEE, chat when there is not

The narrow rule, not the blanket one. HTML is for reports and for anything the reader must LOOK at to decide. Ordinary text choices belong in chat, including the app's own option cards. An earlier blanket rule sent every confirmation point to an HTML page; it is retired.

The line to draw

Situation	Surface
The decision-maker must look at an image, design, storyboard, render, layout, cover, or any generated artifact to decide	HTML page, opened locally
The decision-maker is reacting to a report, audit, comparison, options-with-tradeoffs page, or status dashboard	HTML page (this is the house rule's territory anyway)
The decision needs per-item notes across many rows, or the answer may come across several sittings	HTML page with the review layer
Plain choice among a few text options	chat, option cards are fine
Session-start scoping, "which mailbox", "should I proceed", yes/no gates	chat
One-line clarification	chat, plain text