Changelog / v1.7.0 / 25 Sept 2026

Build edits verified at more than one size, and shared components that ask first

Build's Compare re-renders and verifies every edit on a second device or theme, an edit inside a shared component asks before it spreads, style edits land in the idiom your code already uses, and the Flows screen is hidden until its library ships populated.

Installers and signatures for v1.7.0

New

2
  • Compare verifies a Build edit at more than one size.

    Turn Compare on, pick a second device and/or the other theme — the choice is remembered per project — and every edit is re-rendered and verified there too. The stage shows the primary render beside each variant as scroll-linked tiles, sized in proportion to their devices. A variant that fails rolls the whole edit back and names itself as the cause, above its render.

  • Edits inside a shared component ask before they spread.

    When the selected element is defined in another file, the panel says "Defined in <file> · N on this screen" and asks whether the change is for all N. Yes changes the component itself and verifies every instance on screen, reporting how many it covered and which usage sites it could not render. An edit meant for one usage that reaches the others rolls back as a leak.

Improved

3
  • Build edits are written the way your code is written.

    A style edit lands in the element's own idiom — its Tailwind classes, its CSS-module or global stylesheet rule, its styled-components or emotion template, its StyleSheet entry — and never as a new inline style. An edit no codemod can make in that idiom stops with *Ask the agent*, which sends it to the project's agent as a verified turn.

  • One lint list.

    Build → Lint shows the last agent turn's kit checks beside the harness findings, in the same rows. Kit findings now carry a stable rule id (tells.spacing-off-scale) instead of a generic tells, so the verify list and the auto-fix prompt name the check that fired.

  • Agents are told the whole edit contract.

    apply_and_verify now describes scope: "definition" for changing a shared component, variants for extra device and theme renders, and where an LLM task's range may reach. propose_intents understands more plain requests — "more room", "rounder", "bold", "make it a row" — and says to write the intent directly when it can't.

Fixed

1
  • A vanished worktree comes back on Windows.

    When an isolated branch's worktree folder had been deleted, re-creating it failed with "could not create leading directories": the recorded path is spelled \\?\C:\…, which Git for Windows can't take. Worktree paths now reach Git in their plain form.

Removed

1
  • The Flows screen is hidden for now.

    Its library opened empty on every install: the flow packages the app ships were never copied into the store the screen reads. The top-bar button, Knowledge's *Open prototype* and *Save as flow* in a mobile project's share menu are gone until that is fixed. The accepted flow cards still reach agents through Knowledge, as before.