docs: catch README and getting-started up with pharn-oss 6.20.2

[PrzemekGalarowicz]

What this changes

pharn-oss moved from 6.9.0 to 6.20.2 over its last 30 commits. The biggest change is a new eighth pipeline stage, /pharn-test, which runs between grill and build (6.17.0–6.20.0). Our docs still described seven stages. This PR updates README.md and docs/getting-started.md to match:

• Pipeline: adds test, so there are eight stages. The stage table gets a /pharn-test row, and /pharn-ship now runs stages 1-7. The /pharn-plan and /pharn-verify rows now mention the acceptance-criterion (AC) tests.
• New prerequisite: the test stage needs a test script whose reporter writes per-test JSON, configured through testResults in pharn.config.json. Without it, /pharn-loop ends with blocked: no-test-runner. The README's own create-next-app example runs into exactly this.
• Per-feature artifacts: adds AC-TESTS.md, AC-TESTS.lock.json, BRIEFING.md / LOOP.md, RUN-REPORT.md, cost.json and the *-report.json files.
• After install: documents the new require-loop-record.cjs Stop hook (6.12.0). A settings.json that was preserved, or created before 6.12.0, needs its entry copied in by hand.
• SPEC template: notes that /pharn-spec uses the project's own pharn.spec-template.md if present (6.14.0), and that the write guard blocks Claude Code's edit tools on that file.
• Fixes an older error: the docs said /pharn-loop keeps both human gates. It doesn't: the model approves its own spec, and the human decides after the run.
• docs/getting-started.md: "ten" installed commands becomes "eleven".

Type of change

• feat — new stack option, wizard step, or command capability
• fix — bug fix
• docs — docs-only change
• chore / refactor — tooling or internal restructure, no behavior change

Area(s) touched

docs

Checklist

• Read the existing file(s) before editing; followed the ESM .js-extension import convention.
• Updated the matching tests/*.test.ts when wizard behavior changed (n/a: no behavior change).
• Updated the relevant docs/ page; everything described is shipped upstream in pharn-oss 6.20.2.
• Preserved the security invariants in src/lib/validate.ts (n/a: no remote-input handling touched).

Quality gates

• npm run check: run in a clean clone after npm ci. format:check, lint, lint:md and typecheck pass. test has 5 failures in tests/init.test.ts / tests/update.test.ts that fail the same way on the unpatched base: the environment runs as root, so their permission-based failure injection never triggers. tests/docs-install-tables.test.ts passes.
• npm run build: not run (docs-only change).
• npm run test:coverage: not run; CI covers it.

Notes for the reviewer

• No CHANGELOG entry, following the recent README-only commits.
• Found but not fixed here (code, out of scope): re-running pharn init rebuilds pharn.config.json from scratch (src/steps/install-archetype.ts). That drops a user-added testResults block, which the new test stage depends on. add, update and remove keep it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XN3wDK2oR4TgcnPGZ6Fs9R

---

Generated by Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 7c4c4abf-bbf3-493c-a457-fd11bad88175

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}