lean-forge 2.0.0

Ask what matters. Build the least. Prove it ran.

lean-forge 2.0 is one Claude Code plugin that combines three ideas which usually pull against each other:

• SETTLE — a hook keeps file edits closed until the decisions a result depends on are answered. Questions come once, with a recommendation and a worked boundary example each, ending with "any other rule you hold?". Jev opens the gate at once for requests that already fix their own result (typos, renames, stated output).
• BUILD — Ponytail 4.5.0, vendored. Confirmed rules become tests first; then the smallest change that passes.
• PROVE / REPORT — Castra 0.9.1, vendored unchanged: per-file evidence ledger, execution contract, guardian for risky commands, release gate, checkpoints.

Measured (8 tasks, 36 hidden tests, Claude Opus 5, no other harness loaded)

	Hidden tests	Time	Cost
Castra + Ponytail	15/36	10 min	$3.79
lean-forge 2.0 (2 runs)	31/36 · 36/36	18 min	$5.2

• vs Castra + Ponytail: 2.2× accuracy (p < 0.001), no significant time difference (p = 0.07)
• 6 of the 8 missed tests came from two runs where the scripted user answered against its own intent file.

Benchmark, hidden tests, runner and per-run numbers are in bench/.

Install

/plugin marketplace add beyondworks/lean-forge
/plugin install lean-forge@lean-forge

Requires python3, node, git. Optional: TYPESAFE_API_KEY (environment variable or macOS keychain item) for Jev. If you already run Castra hooks or the Ponytail plugin, turn them off; lean-forge contains both.

Known limits

One small benchmark repository; large codebases and on-device verification were not benchmarked. The SETTLE gate watches the edit tools only; shell writes pass it. The Jev threshold (0.5) was set on 16 requests.

---

한국어 소개: README.ko.md