v1.1.0

FlowForge 1.1 — the public launch. The biggest release in FlowForge's history: 210 commits and ~120 pull requests since 1.0.6 — every one of them through the same gates FlowForge sells: blueprint before code, an independent GOLDEN review, green CI, and a founder merge. Built by FlowForge, on FlowForge.

Talk to your cockpit — the voice loop is closed

Push-to-talk (double-tap Ctrl), automatic transcription and submit, ACE speaks only its own attributed replies, and a barge-in stop that always works — plus a spoken summary of every substantive answer. The cockpit is now a conversation.

ForgePlay — from a plain-language idea to emitted tickets, zero hand-edits

Describe a feature; FlowForge runs requirements → blueprint → ratification and emits milestone-homed, dependency-ordered micro-tickets through one enforced chokepoint (EMIT ⟺ RATIFIED). The whole arc is regression-locked: a byte-level snapshot proves the flow never needs a manual file edit.

Tickets are now a vitrine

Every emitted ticket carries the full story: quoted requirements excerpts, SHA-pinned links to its blueprint, acceptance checkboxes, assignee, priority, size, dates, and a human-readable dependency list — beside the machine-readable trailer that drives wave ordering.

The Documents Drawer

Blueprints, ADRs, rendered doc archetypes, and play artifacts open in an in-cockpit drawer with search and breadcrumbs — on desktop they push straight into the preview pane.

Text that behaves like a modern editor

A shared text surface across ForgePlay and feature forms: clipboard parity (text and images), app-owned selection and copy, responsive sizing — identical on every adopted screen.

Multi-project isolation, sealed

Project A's workers can never surface in project B again: session lists are scoped at the source, project switching re-execs cleanly, and every launch is rooted in its own worktree. Verified live with a two-project switch drill.

Release discipline, self-applied

Deploy-from-main with semver enforcement, a staged release pipeline with a founder-controlled promote gate, self-driving merge readiness (verify → review → flip), a single honest auto-merge consent toggle, and merge attestation on every merge — auto or manual. This very release shipped through all of it.