forge 0.13.11

A stable patch release. This page covers what changed since 0.13.10 (PR #138). It fixes two spec-review packet bugs that showed up in a brownfield repo with many tracked images.

Spec review no longer crashes on a binary match

Reference resolution parsed the first git grep line as path:line:text. When the first match was a binary file, git printed Binary file <path> matches instead, and packet build crashed with a ValueError. A short backticked ref like rpm can match by chance inside a PNG.

• Symbols resolve against text files only (git grep -I): a spec never refers to bytes inside a binary file.
• Any other unexpected grep output raises an error naming the line, instead of failing on a bare unpack.
• The structural dependencies_read check shares the resolver, so a symbol claimed to live in a binary file now reads as not found.

Spec reviewers can open the hunting list

The packet named skills/brainstorming/design-anti-patterns.md relative to the plugin root. The reviewer runs in the repo under review, where that path doesn't exist, so reviewers skipped the hunting list without saying so. The packet now names it by absolute path under the plugin root.

Codex

No hooks/hooks.json change since 0.13.10, so Codex doesn't ask you to re-trust forge's hooks.

Install

claude plugin marketplace update forge
claude plugin update forge@forge        # or: claude plugin install forge@forge

Restart the session to apply. On Codex: codex plugin marketplace add forcetrainer/forge --ref forge--v0.13.11, then codex plugin add forge@forge.