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-core
The shared library the Nisse agents sit on (Part L of the architecture). It never imports an agent. Packages follow the architecture's sections:
models(L9, L7):llm(the one client),catalogandprobe(what the models are),renderandrender_anthropic(request bodies from the log),context(fitting a request to its window, L6).log(L7, L6):canonical(the log's events),views(what each role is shown of the others).state(L8):store(an agent subclassesStateStorefor its own tables, roles and views),reconcile,worker,cancel,dump.knowledge(L10, L6.4):vault,memory.conversation(L5):transport,matrix.execution(L13):ssh(SSH to a tool VM);testing(a throwaway sshd for tests).authority(P3, P4, L4):actions(Action,Verdict, and static reading of shell commands, which each agent's fast-path rules build on;nisse-dev's are innisse_dev.loop.actions).loop(L2):driver(a driver run, with the agent's waiting tools and executor),tools(the control tools any agent offers),expert(ask_expert, L9). Each agent keeps its own scheduler.knowledgealso hashandlers: the vault and memory as control tools.config: the shared parts of an agent's configuration.- At the top, until each gains a second module:
gitea(the tracker and forge, L1),oplogandenvfile(L12).