cloudagent-daemon 0.5.6__tar.gz → 0.5.7__tar.gz

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/CHANGELOG.md

@@ -4,6 +4,26 @@ All notable changes to the local daemon. Format follows
 [Keep a Changelog](https://keepachangelog.com/); versions are
 [PEP 440](https://peps.python.org/pep-0440/). Release with `scripts/release.sh`.
 
+## [0.5.7] — 2026-08-30
+
+### Fixed
+- A periodic (timer) wake no longer publishes its throwaway session as the
+  global lane. 0.5.6 closed `set_last_session_id` but not `write_last_spawn`,
+  which rewrites `last-spawn.json` wholesale — and `last_session_id()` reads
+  that file's `session_id` back as the global lane. A patrol therefore still
+  left its thread there, and the next wake without a conversation resumed it:
+  the same bleed 0.5.6 set out to remove, one door further along. Caught on a
+  live host, not in review — after upgrading, the tick correctly dropped
+  `--resume` and left the room's lane alone, but `last-spawn.json` still moved.
+
+### Notes
+- `read_analyze` already carried the owner's value through this call for the
+  same reason; periodic wakes now share that path. The spawn record still
+  captures the tick's rc/stderr, so operators lose no diagnostics.
+- Anyone who ran 0.5.6 should check `.meta/last-spawn.json`: if its
+  `session_id` points at a patrol session, setting it to `null` makes the next
+  conversation-less wake start clean.
+
 ## [0.5.6] — 2026-08-30
 
 ### Changed

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cloudagent-daemon
-Version: 0.5.6
+Version: 0.5.7
 Summary: Local daemon for cloudagent — bridges Claude Code, Codex, and Qoder CLI agents to the cloudagent backend.
 Project-URL: Homepage, https://cloudagent.chat
 Project-URL: Repository, https://codeup.aliyun.com/69bd0a4d29ad98af4065ce71/cloudagent

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "cloudagent-daemon"
-version = "0.5.6"
+version = "0.5.7"
 description = "Local daemon for cloudagent — bridges Claude Code, Codex, and Qoder CLI agents to the cloudagent backend."
 authors = [{name = "chaoyin", email = "tudoucyx@gmail.com"}]
 readme = "README.md"

cloudagent_daemon-0.5.7/src/cloudagent_daemon/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.5.7"

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/src/cloudagent_daemon/claude_runner.py

@@ -995,8 +995,13 @@ The daemon discards stdout — only the mcp tool call reaches the channel.
         # 的读取源(下次 resume 依据)。read_analyze 若把自己的 thread 写进去就会
         # 渗进 owner 的 full 会话,故这里保留 owner 轨原有 session_id(仍记录本次
         # 的 exit_code/stderr 供调试),read_analyze 的 thread 不落任何持久轨。
+        # A periodic wake is throwaway for the SAME reason: it resumed nothing,
+        # so recording its thread here would publish it as the global lane and
+        # the next wake without a conversation would resume the patrol.
         spawn_record_session = (
-            ws.last_session_id() if is_read_analyze else captured_session
+            ws.last_session_id()
+            if (is_read_analyze or is_periodic)
+            else captured_session
         )
         ws.write_last_spawn(rc, spawn_record_session, stderr_tail)
 

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/tests/unit/test_claude_runner.py

@@ -3930,6 +3930,33 @@ async def test_periodic_wake_leaves_the_rooms_lane_untouched(
     assert agent_ws.set_calls == []                 # nor did the global lane move
 
 
+async def test_periodic_wake_does_not_publish_itself_as_the_global_lane(
+    stateful_fake_claude, tmp_path
+):
+    """B — the global lane has TWO writers; a patrol may use neither.
+
+    ``set_last_session_id`` is the obvious one, but ``write_last_spawn``
+    rewrites last-spawn.json wholesale — and ``last_session_id()`` reads its
+    ``session_id`` back as the global lane. Blocking only the first still let
+    a patrol publish its throwaway thread, so the next wake with no
+    conversation resumed it. read_analyze already carried the owner's value
+    through here for exactly this reason; a periodic wake now does too.
+    """
+    mcp_cfg = tmp_path / "mcp.json"; mcp_cfg.write_text("{}")
+    agent_ws = FakeAgentWorkspace(mcp_path=mcp_cfg, last_session="owner_thread")
+    runner = _build_runner(
+        stateful_fake_claude([_claude_ok("patrol_thread")]),
+        FakeWorkspace(agent_ws),
+        FakeOutbound(),
+    )
+
+    await runner.run_one("agent-A", _reminder_payload(conversation_id="conv_room"))
+
+    assert agent_ws.write_last_spawn_calls, "the spawn record is still written"
+    recorded_session = agent_ws.write_last_spawn_calls[-1][1]
+    assert recorded_session == "owner_thread"   # NOT patrol_thread
+
+
 async def test_ordinary_wake_in_that_room_still_resumes_and_records(
     stateful_fake_claude, tmp_path
 ):

{cloudagent_daemon-0.5.6 → cloudagent_daemon-0.5.7}/uv.lock

@@ -122,7 +122,7 @@ wheels = [
 
 [[package]]
 name = "cloudagent-daemon"
-version = "0.5.6"
+version = "0.5.7"
 source = { editable = "." }
 dependencies = [
     { name = "h2" },

cloudagent_daemon-0.5.6/src/cloudagent_daemon/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.5.6"