harn: Command for Claude Code

Run a final-polish pass on the current PR or feature branch before it lands.

The goal is the state a senior reviewer would land without comments. The sweep is targeted at the recurring issues this repo accumulates between "the feature works" and "the PR is landable" — not a generic code review.

Phase 0 — identify the work

git status --short
git rev-parse --abbrev-ref HEAD
git log --oneline origin/main..HEAD
gh pr view --json number,state,headRefName,mergeStateStatus 2>/dev/null

If gh pr view returns a PR, you are in PR mode. Otherwise branch mode — skip rebase/CI phases and go straight to the review sweep.

Always read the full diff before touching anything: git diff origin/main...HEAD. In PR mode, also read existing review comments — sometimes the easiest finding is one a reviewer already left.

Phase 1 — rebase on origin/main (PR mode only)

git fetch origin main
git rebase origin/main

Conflict rules in this repo:

• CHANGELOG.md: keep both sides; preserve the top heading.
• docs/theme/harn-keywords.js: regenerate with make gen-highlight.
• docs/src/language-spec.md: regenerate via the pre-commit hook (edit spec/HARN_SPEC.md instead).
• Cargo.lock: resolve from the merged manifests, then run make setup-rust.
• Any file where both sides reformatted: take one side then run the appropriate formatter (make fmt, make fmt-harn, portal lint).

Then git push --force-with-lease. Never bare --force.

Phase 2 — drive CI to green (PR mode only)

gh pr checks
gh run list --branch "$(git branch --show-current)" --limit 5
gh run view <run-id> --log-failed   # for each failure

Address every failure comprehensively — no continue-on-error papering, no silenced asserts. Common categories:

• Format / clippy / lint: make fmt, make lint, make lint-harn, make fmt-harn. Commit the fixes.
• Test failure: reproduce locally with make test-one and the HARN_TEST_ONE_NAME and HARN_TEST_ONE_PACKAGE variables, then fix the root cause. Use make test-affected when the failure spans a changed crate.
• Conformance: ./scripts/harn_bin.sh -- test conformance --filter <name>. If .expected needs an update for an intentional behavior change, do it explicitly.
• Portal / VS Code / tree-sitter: run the relevant npm run portal:lint|build|test / (cd tree-sitter-harn && npm test).
• Drift checks (check-language-spec, check-highlight, check-trigger-quickref): re-run the generators and commit the outputs.
• make lint-test-patterns: see Phase 3.2.
• check-docs-snippets: a .harn snippet in docs no longer parses; fix the snippet, not the parser.