fix(update): the monitor is this workspace's exact command line; create/resume take the pane workspace's admission; refusal snapshots compare the registry by rows (Issue #72, review round 3)

- daemon.find_running matches `<bash> <reconcile.sh> --subscribe[ ...]`
  exactly instead of an unanchored, unescaped pgrep regex: another
  workspace's daemon (ws.a vs wsXa) or a process naming the path in an
  argument is no longer signalled by the update. update.sh re-checks which
  PIDs are still the monitor before SIGKILL.
- create and resume (spawn path) take the update admission of every
  installed workspace at or above the pane cwd, not only the control
  root's (lib.sh mam_update_admit_at, lib_py.update target-workspaces --cwd);
  the ~/.local/bin wrapper child drops all of them.
- tests: snapshot() skips the SQLite -wal/-shm and compares the DB by its
  rows (macOS keeps the sidecars and a read rewrites -shm); regression tests
  for the monitor match and for create/resume in another installed
  workspace (marker and lock wait); evidence line refs shifted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
GodopuandClaude Opus 5.5 committed 2026-10-28 02:28:55 +09:00
1 parent 454b77215f
commit cf1b693e85
9 files changed
+209 -32

No files matched your search

+10 -10
View File
@@ -11,7 +11,7 @@
"kind": "example",
"evidence": [
"multi-agent-mux-create/scripts/create_session.sh:99",
"multi-agent-mux-create/scripts/create_session.sh:359"
"multi-agent-mux-create/scripts/create_session.sh:360"
],
"mismatch": null,
"note": "HERDR_SESSION_NAME environment example"
@@ -67,7 +67,7 @@
"class": "c",
"kind": "example",
"evidence": [
"multi-agent-mux-create/scripts/create_session.sh:517-544"
"multi-agent-mux-create/scripts/create_session.sh:518-545"
],
"mismatch": null,
"note": "Output format: the row create_session.sh writes"
@@ -492,9 +492,9 @@
"multi-agent-mux-resume/scripts/resume_session.sh:133-144",
"multi-agent-mux-resume/scripts/resume_session.sh:147-170",
"multi-agent-mux-resume/scripts/resume_session.sh:188-213",
"multi-agent-mux-resume/scripts/resume_session.sh:265",
"multi-agent-mux-resume/scripts/resume_session.sh:269",
"multi-agent-mux-resume/scripts/resume_session.sh:275-278",
"multi-agent-mux-resume/scripts/resume_session.sh:266",
"multi-agent-mux-resume/scripts/resume_session.sh:270",
"multi-agent-mux-resume/scripts/resume_session.sh:276-279",
"lib_py/agents/adapters/claude.py:109"
],
"mismatch": [
@@ -561,8 +561,8 @@
"multi-agent-mux-create/scripts/create_session.sh:166-168",
"multi-agent-mux-create/scripts/create_session.sh:207",
"multi-agent-mux-create/scripts/create_session.sh:259-274",
"multi-agent-mux-create/scripts/create_session.sh:364-401",
"multi-agent-mux-create/scripts/create_session.sh:413-415"
"multi-agent-mux-create/scripts/create_session.sh:365-402",
"multi-agent-mux-create/scripts/create_session.sh:414-416"
],
"mismatch": [
"C1: an existing session is exit 1 in the doc, exit 3 in the script",
@@ -582,7 +582,7 @@
"base_sha": "f71be0f26fb8",
"class": "a",
"evidence": [
"multi-agent-mux-create/scripts/create_session.sh:489-607"
"multi-agent-mux-create/scripts/create_session.sh:490-608"
],
"mismatch": [],
"replacement": "bash .agents/skills/multi-agent-mux-create/scripts/create_session.sh --workspace <path> --agent <agent> --role <role>",
@@ -633,14 +633,14 @@
"other"
],
"passthrough": {
"4": "multi-agent-mux-create/scripts/create_session.sh:549"
"4": "multi-agent-mux-create/scripts/create_session.sh:550"
}
}
},
"prose_mismatches": [
"C4: create named a nonexistent `agent-sessions-yaml-edit` script; removed (create_session.sh writes the row)",
"C5: create's cmd_full table (claude = `claude`) disagreed with adapter spawn-spec; replaced by \"decided by spawn-spec\"",
"C6: create_session.sh header lists exit 4 \"YAML append failure\"; there is no literal `exit 4`, but the YAML write raises SystemExit(4) for a duplicate running row (create_session.sh:515) and it passes through, so 4 IS a real exit code (the plan assumed it was not)",
"C6: create_session.sh header lists exit 4 \"YAML append failure\"; there is no literal `exit 4`, but the YAML write raises SystemExit(4) for a duplicate running row (create_session.sh:516) and it passes through, so 4 IS a real exit code (the plan assumed it was not)",
"R6: resume's \"The script above re-passes them\" and \"as done in Workflow above\" pointed at the removed block; reworded (same for create's Verification note)",
"R7 (review 08e1f1b2): stop's table said exit 1 is always pre-stop; the registry update after the kill chain also raises SystemExit(1) (stop_session.sh:310) when the row disappeared"
],