v0.4.7

What's new in v0.4.7

• --accept-protected-failures works whatever order the plan lists its checks in (#406, #410). When a plan check runs the same command as a Formula baseline (for example go test ./...), the protected view skips it as covered. If an earlier check stopped the protected view before that baseline ran, the skipped check was recorded as not run without naming its baseline, so accepting a by-design failure was refused with observation 1 does not match the approved check. It now keeps the baseline's name, so the acceptance goes through. The rule that the record must name the baseline the plan gives it is unchanged, and a not-run record still never counts as delivery evidence. You no longer need to reorder the plan by hand.

Adapter protocol is unchanged (11). Labs on 0.4.6 need only a launcher rebind (forgecell init --lab DIR --rebind <harness>, then approve).

Verified on v0.4.6, and unchanged in this release: Claude Code, Codex, and Cursor (coding, with another harness planning) each run the whole loop.

---

Native Forgecell CLI for macOS and Linux (amd64/arm64), with per-artifact SHA-256 files, MIT LICENSE and dependency notices. End users do not need Node, Go or source-repository access.

This is a draft release for review, not automatic publication. The rendered installer pins this exact version and its v-prefixed tag at DanielNetzer/forgecell. Approve public visibility and exact-head Actions results before draft review and approved publication. Verify anonymous install, upgrade and rollback before switching the documented legacy endpoint.

Installer activation smoke-checks the version and preserves Lab data. forgecell rollback restores the previous validated release. Running tickets requires Git, authenticated gh and a configured coding harness.