see-ui

# see-ui — look at the page before you say it's done Layout and design failures are invisible to your normal loop: the DOM is valid, the CSS applied, the console silent — and the page is still broken to a human eye (a chart squashed into 5% of its width renders "successfully"). Code and logs cannot catch "technically correct but looks wrong". Pixels can, and you can read pixels. ## The command ```bash botference see <target> [label] [--viewport WxH]... [--basic-auth U:P] [--out DIR] ``` - `<target>`: a URL, a bare `:port` (localhost), a **local file path** (HTML, SVG — rendered via file://, no server needed: the way to verify charts, reports, and mockups you just wrote), or the NAME of a running `botference service` — its listening port is discovered from the live process, you never need to know it. - Never hand-roll rendering via ImageMagick/qlmanage/rsvg to check a chart — their SVG engines have artifacts Chrome does not; `see` is the trustworthy lane and works from your sandbox. - Default viewports: `390x844` (phone — real mobile layout, since responsive CSS answers to viewport width) and `1440x900` (desktop). - It prints `wrote: <path>.png` lines. **Read those images.** That is the entire point — do not run the command and skip looking. - Output defaults to `.botference/shots/` (gitignored by convention). ## Protocol 1. After ANY change that affects rendered UI, screenshot both default viewports and look at them before reporting the change as done...