dongarandClaude Opus 5.5
33d030590d
The reviewer is read-only (R3), so Gitea refuses it resolving a thread. Now each reply says whether it settles its thread, and a settled reply carries <!-- nisse-review: settled -->. nisse-dev, as the author, resolves every comment on that thread's line when it watches the PR, and doesn't take the settled reply as a point to answer. scripts/resolve_settled.py does the same for PRs made by hand. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
nisse-review
The Review Agent (Part R of the architecture): it reviews every pull request that is ready, in the repositories its Gitea account can read, and posts its review on the PR as a COMMENT review. It reads and comments; it never changes code, approves, or requests changes.
A thin application over nisse-core, with its own small scheduler:
config: its YAML configuration (nisse-review.example.yaml).state: its state store, and a review item (one per PR).scheduler: the duty (ready PRs), one review at a time, recovery after a crash.clones: each repository as a git clone kept between runs (the latest one), checked out at the PR's head and, when read, its base.reader: those trees, read-only, as the run's executor.review: one review run, and posting it.build,main: putting it together, and the access check at startup.
Bring-up on the development VM: scripts/review-bringup.sh.