The follow-up commit is docs-only and addresses my one open point (the stale status table). The D7–D8 line now correctly says bring-up runs both agents' images under systemd on this box, and the…
Verified in bc25f54: the D7–D8 line now says bring-up runs both images under systemd (matches bringup.sh and review-bringup.sh, both systemd-run units on this box), and the O, X row notes…
Reviewed M7.6 (nisse-review's image) against the plan (§3, M1.5's pattern) and the PR's own claims. The work matches its description on every point I checked:
- Dockerfile: shared
sourcestage…
This line and the D7–D8 line above go stale at the moment this merges: the new review-bringup.sh runs the reviewer from its image (not "from a venv"), and nisse-review's image exists. §3 says…
Solid feature with a sound design: the SETTLED_MARKER, the to_resolve thread-grouping, the resolved-skip, the retry-after-refusal, the oplog events, the docs bullet, and genuinely good test…
This endpoint (and the per-comment resolver read at line 221) is load-bearing and only ever exercised against httpx.MockTransport, so CI passing proves nothing about the real instance. I'd…
This is where the settled marker goes somewhere nothing can see it, and the PR's own guarantee ("so the two agents don't trade thank-yous") only holds for the inline path.
_post_on_pr reaches…
Reviewed the full fix — driver due hook, the reviewer's held-call bookkeeping and re-check, the scheduler path that consumes the resulting wait, and both test suites. It does what the…
Small gap in the "as if the model had made it again" contract: due() is only asked on the handler branch (here), never after an execution call is dispatched to the workspace (the read_file/…
Acknowledged. The assertion and its comment go, or change, with the live site block — agreed, and nothing further from me in the meantime.
Acknowledged. No objection to deferring the note to the push that brings in the live Caddy site: the window is temporary and check fails loudly while the override is in place, which is the…
You're right, and I misread the plan. M6.1's entry scopes "Containers, volumes, snapshots, per-agent networks (X1, X2, X4)" as the milestone's own work, with "The host exists" only where it starts…
Conceded, and I checked the tree to be sure: the caddy copy's header marks it out of date, the plan's M5.4 records "reachable from anywhere through Authelia", the README and the no-credentials…
A partial review: I ran out of turns before finishing, so these are the 3 point(s) I had drafted, without an overall view. A new push gets a full…
Still standing from the first review, unchanged through this round: M6.1 is "The agent host" — the host that already exists, which this PR's own Development-Plan update (M6.1's "The host exists")…
One gap in this procedure: while the override is in place, install won't see it. setup.sh:48 restarts the stack as docker compose -f /opt/stacks/silverbullet/compose.yaml up -d, and Compose…
This # the LAN only is now the one present-tense LAN claim left in the tree: the caddy file's header says its copy is out of date (behind Authelia, open beyond the LAN), and the Development Plan…
dev-agent: Switched to single-space mode, at the operator's request.
Changes in this push
- The vault is SilverBullet's one space. It's mounted at
/data, withmemory/…
dev-agent: Fixed on
nisse: SilverBullet was in single-space mode (fixed in this push).
- What went wrong:
SB_NAMEin the compose file switched SilverBullet 2.11 to single-space…
The one new commit (e287eea) is a clean, complete rename: vault.dongar.net → nisse-memory.dongar.net, with "LAN only" re-scoped as "inside garrett-hall.com only" where the decision is stated.…