Pharn (@pharn_dev) header
Pharn (@pharn_dev) profile picture

Know if an agent's PR is safe to merge.

Poland
Joined May 2026
7.3.0 highlights from the 2026-11-03 review: - set-writes-scope.cjs --check runs at plan time - new CI gate: check:ship-record - REVIEW.md now floor-rendered (fenced, capped, injection-resistant) - trusted docs updated (LIMITS, THREAT-MODEL, ARCHITECTURE)
4
16
CLI 0.21 heads-up: - needs pharn-oss 7.21+ - flat layout is gone, re-run `pharn init` - teammates on 0.19.x: upgrade first Also: `pharn update` always checks upstream now, and one docs page lists every delete pharn makes and the check behind it. github.com/pharn-dev/pharn-o…
1
Not in the release, but measured today: a defect probe set. 6 plans/specs, one planted bug each. On 7.19.0: 10 of 12 runs caught it (2 runs per probe). 9 via findings scored on file anchors, 1 at the plan stage, which reads model text (advisory).
2
Routed stage agents are now requested at the effort you configure per stage, not just the model. Until now, `effort: high` never reached them. It's a request, not a guarantee: if the harness doesn't take the param, the stage still runs and says so.
5
A plan can't silently lose a file anymore. If the plan's ## Files list has an item the write guard can't scope (a glob, an empty line), the check fails and names it. Before, it was dropped quietly and surfaced mid-build as a denied write. Bit us 3 times.
6
Pharn OSS 7.22 + CLI 0.21.1 are out. pharn-oss now declares its own install: pharn-install.json lists all 614 files with a SHA-256 each. The CLI checks every hash before writing anything. New pharn-* surfaces no longer need a CLI release. npx @pharn-dev/pharn@latest update
1
8
Agents write diffs faster than people can review them. pharn-ci answers the cheap questions before a human opens the PR: Did the tests actually run the new code? Does the repo tell agents how to work in it? 0.5.0 is out. github.com/pharn-dev/pharn-c…
9
Pharn retweeted
Shipped 7.3.0. Less trust in the model. More in the trail. Plan-time scope checks. Floor-rendered reviews. Green ship records required for product changes.
1
3
15
Shipped 7.3.0. Less trust in the model. More in the trail. Plan-time scope checks. Floor-rendered reviews. Green ship records required for product changes.
1
3
15
PHARN 6.9.2. This week: loop-decision re-derivation, per-run token ledger, run reports, review assignment records, hardened write guards. Open source, Apache 2.0. npx @pharn-dev/pharn@latest init
1
122
/pharn-review now records which files each lens was given, and for every merged finding, whether a deterministic scanner stood behind it or none did. A review you can audit, not just read.
20
We grilled our own plan with PHARN. It claimed a "2–5%" speedup. The grill pointed out that the plan's own numbers give 1.5–4.5%. Then we decided not to ship it anyway: the gain was small and it carried a correctness risk. Measured, recorded, deferred.
1
47
Can't measure usage? PHARN's run report says UNAVAILABLE. Ledger left over from a previous run? It says STALE. Unknown is not zero, and old is not current.
19
PHARN 6.40: /pharn-regress and /pharn-verify now refuse to run gates when your node_modules doesn't match the lockfile. A green test run on drifted deps isn't evidence. The fix it names: npm ci.
1
13
PHARN 3.0.2. npx @pharn-dev/pharn status reports the installed skills version and drift. update re-fetches, add / remove manage capabilities. Skills version and installer version move independently, on purpose.
1
16
Before an unattended commit, PHARN now re-derives /pharn-loop's stop decision from the reports the record cites. A record that doesn't follow from its reports doesn't ship. The limit: re-derivable ≠ honest. A forged record with matching forged reports still passes.
1
8
13 grillers interrogate a plan before code exists. 22 lenses read code after it does. Every capability ships with eval cases. The floor refuses a capability whose declared rules aren't exercised by at least one eval.
1
14
npx @pharn-dev/pharn@latest init The installer reads your repo, resolves capabilities (ssr / backend / spa / lib), and prints the selected list with a reason per entry before writing anything. Node 20+. pharn.config.json pins the skills version and the exact installed commit.
1
1
20
New in PHARN: /pharn-loop and /pharn-ship now end with cost.json (machine-readable) and RUN-REPORT.md (human-readable). Tokens for this run only, not the session. Stored with the change. No prices baked in: you apply your own price list. pharn.dev
1
1
15
A guarantee must reduce to a non-LLM operation: hook decision, content hash, enum membership, regex match, exit code. Anything a model judges ships as advisory and is labeled that way in the artifact it lands in.
1
1
14