dongarandClaude Opus 5.5 33d030590d nisse-review marks a reply that settles its thread; the PR's author resolves it ...

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

2026-10-19 22:06:56 +00:00

..

benchmark.py

M7.2: share the loop's parts

2026-10-13 21:31:29 +00:00

bringup-repo.sh

M7.1: extract nisse-core

2026-10-13 18:37:01 +00:00

bringup.sh

nisse-core: group modules into packages by architecture section

2026-10-13 21:16:09 +00:00

check.sh

Add the end-to-end test, run after each milestone (M1.6)

2026-10-02 22:59:13 +00:00

ci-sshd.sh

nisse-core: group modules into packages by architecture section

2026-10-13 21:16:09 +00:00

classifier-evals.py

nisse-core: group modules into packages by architecture section

2026-10-13 21:16:09 +00:00

e2e-cleanup.sh

M7.1: extract nisse-core

2026-10-13 18:37:01 +00:00

e2e.sh

CI runs nisse-review's live test

2026-10-16 20:25:54 +00:00

evaluate_model.sh

M2.8: switch over to the new loop

2026-10-08 03:12:58 +00:00

probe_context.py

M7.2: share the loop's parts

2026-10-13 21:31:29 +00:00

resolve_settled.py

nisse-review marks a reply that settles its thread; the PR's author resolves it

2026-10-19 22:06:56 +00:00

review-bringup.sh

Development Plan: every agent is its own container image

2026-10-19 13:16:07 +00:00