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

The failure this skill exists to prevent runs in both directions. Asking someone to choose between sixteen images inside a chat message is unusable. Building a whole HTML page so someone can answer "A or B" is friction dressed up as service.

The line to draw

Situation	Surface
They must look at an image, design, storyboard, render, layout, cover, or any generated artifact to decide	HTML page, opened locally
They are reacting to a report, audit, comparison, options-with-tradeoffs page, or status dashboard	HTML page
The decision needs per-item notes across many rows, or may be answered across several sittings	HTML page with a review layer
A plain choice among a few text options	chat, option cards are fine
Session-start scoping, "should I proceed", yes/no gates	chat
A one-line clarification	chat, plain text