Threads an optional machine= kwarg through herdr_json/
herdr_diwan_workspace_id (default None, fully backward compatible),
reusing the exact focus-then-attach pattern cmd_bare already uses
locally, just against --machine <label> for the scripted focus call
and --remote <machine> for the actual interactive attach.
Verified: argparse wiring, the no-herdr-on-PATH dry-run path, and that
a bogus --machine label fails fast and cleanly (not a hang) rather than
attempting a real network connection -- confirms the warning-then-exec
fallback in cmd_remote is safe. Did not test an actual real remote
attach (no SSH path to any herdr server from this sandbox).
Reports no longer get an entry for routine mechanical steps (a plain
dispatch, a session closure Marc already asked for, a nudge, a pass
with nothing to triage) -- only for actual findings/decisions/problems.
Zero new entries in a tick run is now the normal case; PROTOCOL.md's
worked example replaced with entries that carry real information
instead of 'dispatched X'/'triaged N items' noise.
TICK.md step 3: a session whose Close diwan session is checked off now
gets genuinely torn down by the tick agent -- herdr tab close on its
DIWAN_ID's tab, :session: tag stripped from the heading, DIWAN_ID
property kept as a historical record. Resolves the 'retired-session
teardown' known gap from DESIGN.md (previously only reported, never
actually closed). Not yet verified against a real live tick run.
A report subheading's title is now the link to the heading it's about
(org [[target][description]] syntax, description = the short title),
instead of a separate :LINK: property in a properties drawer. Plain text
title when there's no single heading to link. Further links, if needed,
go inline in the signed body.
Removed AGENT_KIND/DIWAN_HARNESS and CLAUDE_PERMISSION_MODE/
DIWAN_PERMISSION_MODE; herdr_agent_start_args now hardcodes --kind pi and
always appends PI_APPROVE_FLAG. Motivated by a real live failure: Claude
Code blocks on an interactive first-run trust dialog in any content repo
it hasn't seen before, which herdr's real-pane dispatch can't answer
(agent_not_ready after a 30s timeout). pi has no such dialog and no
per-tool-call approval gate, so it was already the better fit for
diwan's unattended model -- confirmed live against a brand-new content
repo with zero blocking.
Updated PROTOCOL.md/DESIGN.md accordingly, replacing the harness-
agnosticism framing with an explicit pi-only statement, while leaving
TICK.md/DO.md untouched since neither ever mentioned a specific harness.
Contains only the generic diwan CLI and procedure docs (diwan, PROTOCOL.md,
TICK.md, DO.md, DESIGN.md). No personal notes, no content-repo-specific
AGENTS.md -- those now live in a separate content repo (e.g. diwan-dev-notes
for testing, ~/nc/org-agenda for the real thing), discovered at runtime via
git rev-parse --show-toplevel from wherever diwan is invoked.
History reset: this repo previously doubled as both diwan's own dev copy and
a throwaway test-content repo, with 48 commits of the two tangled together.
Starting fresh now that the split is done -- still v0/prototyping.