v1.1.1

First published release. Covers everything since the v1.0.0 tag, which was never released, so the evaluation-surface work from 1.1.0 lands here too.

Evaluation surfaces

/forge:building no longer assumes every project is a web app.

It now resolves an evaluation surface up front (web, library, cli, service, native), inferred from the repo and confirmed with you. A new --surface flag skips the question. The surface flows into the contract, into the generator's verify_how vocabulary, and into the evaluator's tools and role prompt.

Only web needs a browser automation MCP server, and it is checked in the new Phase 0.5 preflight, before a worktree, a contract, or an issue comment exists. Previously a missing browser surfaced in Phase 6, after two opus negotiations and a full build. Preflight also adds the gh auth and remote check that /forge:planning had and /forge:building lacked.

The evaluator never runs the builders' tests

A guardrail the browser-only design never exposed. Builder-written tests encode the builder's understanding, so a green suite certifies whatever misunderstanding produced the bug. Those tests still run in Phase 5 as static verification. They do not count as evaluation. The evaluator writes its own scripts in harness/eval/, from the contract alone, having never read the implementation.

Documentation

• The PM/DEV altitude split is now explained in its own README section: what each altitude may say, and why planning is forbidden technical content.
• A banner, a Mermaid pipeline diagram that renders inline on GitHub, and a full pipeline reference.
• Credits for the two AI Engineer talks and the superpowers repo the workflow builds on.
• /forge:interview Phase 1 renamed from "Grill" to "Interview".

Known limitation

Only the web evaluation surface has actually been exercised end to end. library, cli, service, and native are untested prose.