drydock-cli 2.8.56__tar.gz → 2.8.58__tar.gz

drydock_cli-2.8.58/.auto_release.lock

@@ -0,0 +1 @@
+2574982

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: drydock-cli
-Version: 2.8.56
+Version: 2.8.58
 Summary: Local-first CLI coding agent — tested with Gemma 4 26B via vLLM
 Project-URL: Homepage, https://github.com/fbobe321/drydock
 Project-URL: Repository, https://github.com/fbobe321/drydock

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/drydock/core/agent_loop.py

@@ -1148,6 +1148,7 @@ class AgentLoop:
                           or "error code: 400" in error_str.lower()
                           or "500 internal server error" in error_str.lower()
                           or "status: 500" in error_str.lower()
+                          or "error code: 500" in error_str.lower()
                           or "llm backend error" in error_str.lower()):
                         # Context limit or malformed request — aggressive recovery
                         # Step 0 (added 2026-05-09): if the error looks like a

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/drydock/core/session/session_logger.py

@@ -53,6 +53,12 @@ class SessionLogger:
         self.save_dir.mkdir(parents=True, exist_ok=True)
         self.session_dir = self.save_folder
         self.session_metadata = self._initialize_session_metadata()
+        # Publish current session dir at init too (not just on reset)
+        # so external watchers can find the very first session.
+        try:
+            self._publish_current_session()
+        except Exception:  # noqa: BLE001
+            pass
 
     @property
     def save_folder(self) -> Path:
@@ -327,9 +333,15 @@ class SessionLogger:
         Materializes the new session_dir on disk immediately so external
         watchers (drydock-using tools, dashboards, the stress harness)
         can discover the new session BEFORE the first message gets
-        persisted. Previously the dir only appeared on the first
-        persist_messages call — a race for any watcher polling between
-        /clear and the next user message.
+        persisted.
+
+        Also publishes the new session_dir path to
+        ~/.drydock/current_session.txt — any external tool that wants to
+        know "which drydock session is active right now" can read this
+        single file instead of doing a heuristic mtime-sorted search of
+        all ~3k+ historical session dirs. Solves the post-/clear race
+        where a watcher polling between reset_session and the OS
+        filesystem flush would cache the OLD dir as "newest".
         """
         if not self.enabled:
             return
@@ -340,6 +352,12 @@ class SessionLogger:
         self.session_metadata = self._initialize_session_metadata()
         try:
             self.session_dir.mkdir(parents=True, exist_ok=True)
+            # Touch the messages.jsonl marker so watchers see this as a
+            # discoverable session dir immediately, not after the first
+            # message lands.
+            (self.session_dir / MESSAGES_FILENAME).touch(exist_ok=True)
+            # Publish the active session_dir for external watchers.
+            self._publish_current_session()
             self.log_event({
                 "event": "session_reset",
                 "session_id": session_id,
@@ -347,6 +365,24 @@ class SessionLogger:
         except Exception:  # noqa: BLE001 — never block on disk
             pass
 
+    def _publish_current_session(self) -> None:
+        """Write the active session_dir path to ~/.drydock/current_session.txt
+        so external watchers don't have to mtime-scan the whole history.
+
+        Atomic via write-then-rename. Fail-silent — publishing is an
+        observability convenience, never block the session on it.
+        """
+        if self.session_dir is None:
+            return
+        try:
+            pub_path = Path.home() / ".drydock" / "current_session.txt"
+            pub_path.parent.mkdir(parents=True, exist_ok=True)
+            tmp_path = pub_path.with_suffix(".txt.tmp")
+            tmp_path.write_text(str(self.session_dir) + "\n")
+            tmp_path.replace(pub_path)
+        except Exception:  # noqa: BLE001
+            pass
+
     def resume_existing_session(self, session_id: str, session_dir: Path) -> None:
         if not self.enabled:
             return

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "drydock-cli"
-version = "2.8.56"
+version = "2.8.58"
 description = "Local-first CLI coding agent — tested with Gemma 4 26B via vLLM"
 readme = "README.md"
 requires-python = ">=3.12"

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/scripts/shakedown_interactive.py

@@ -1386,9 +1386,27 @@ class SessionWatcher:
     def find_session(self) -> Path | None:
         if self.session_dir is not None:
             return self.session_dir
-        # meta.json is only written at session EXIT (CLAUDE.md learning #37).
-        # For active sessions we fall back to: new dir (mtime > since) that
-        # has messages.jsonl. meta.json match is preferred when available.
+        # Fast path (added 2026-05-17 with v2.8.58): drydock now
+        # publishes the active session_dir to ~/.drydock/current_session.txt
+        # at session init and on every reset_session. This avoids the
+        # post-/clear race where mtime-scan returned the stale OLD dir
+        # because reset_session's mkdir hadn't flushed yet.
+        pub_path = Path.home() / ".drydock" / "current_session.txt"
+        try:
+            published = pub_path.read_text().strip()
+            if published:
+                p = Path(published)
+                # Only accept the published path if it's recent enough —
+                # protects against a leftover file from a previous run.
+                if p.is_dir() and p.stat().st_mtime >= self.since - 5:
+                    self.session_dir = p
+                    return p
+        except (FileNotFoundError, OSError):
+            pass
+        # Fallback: meta.json is only written at session EXIT (CLAUDE.md
+        # learning #37). For active sessions we fall back to: new dir
+        # (mtime > since) that has messages.jsonl. meta.json match is
+        # preferred when available.
         fallback: Path | None = None
         for entry in sorted(SESSION_ROOT.iterdir(), reverse=True):
             try:

{drydock_cli-2.8.56 → drydock_cli-2.8.58}/trip_log.md

@@ -1,5 +1,59 @@
 # Drydock Trip Log
 
+## 2026-05-17 21:00 UTC tick
+- Stress: ~680/1658 (PID 2501045, ~4h05m elapsed, tool_agent suite; consecutive SKIPs on API-shape prompts normal, FORCE-RESET recovering)
+- Write rate: tracking (no aggregated figure — recent prompts are API-heavy, SKIP-prone)
+- llamacpp 400s: 0
+- GH issues: 0 open
+- Dispatch queue: harness=9 in last 24h (all thinking_stall, existing nudge resolves them per log evidence), retrieval=0 actionable, curiosity=2655 pending (all hle_failure/unknown_term; HLE paused per directive)
+- Model: Q3_K_M on llamacpp-gemma4 (:8000), balancer on :8001 (PID 380535) — both healthy
+- Action this tick: no action — system healthy, no new bugs, retrieval-drain: 0 ingested
+
+## 2026-05-17 20:30 UTC tick
+- Stress: 279/1658 (PID 2501045, ~3h36m elapsed, tool_agent suite, 195 done / 241 steps = ~81% write rate, 0 timeouts, 3 recycles)
+- Write rate: ~81% (done/attempted since restart at step 38)
+- Admiral last 30 min: 1019 total findings; recent-window check skipped (schema traversal error)
+- llamacpp 400s: 0 blocking 400s; 6 minor slot-management lines in last 30m (normal)
+- GH issues: 0 open
+- Dispatch queue: harness=1309 total (9 in last 24h, all thinking_stall — existing nudge logic covers), retrieval=0 actionable, curiosity=2655 pending (409 hle_failure paused, 2245 unknown_term noise)
+- Action this tick: no action — previous tick (20:00 UTC) already committed 332057d; system healthy; no new bugs found; retrieval-drain: 0 ingested (all already recent)
+
+## 2026-05-17 20:00 UTC tick
+- Stress: 238/1658 (PID 2501045, ~3h04m elapsed, tool_agent suite, running cleanly with 3 TUI recycles)
+- Write rate: N/A (no session write-rate metric available for this run)
+- Admiral last 30 min: N/A
+- vLLM 400s: 51 errors in last 60m from docker logs (mix of slot updates and JSON parse errors, none blocking)
+- GH issues: 0 open
+- Dispatch queue: harness=9 (all thinking_stall, already fixed), retrieval=0 actionable, curiosity=588 pending (473 unknown_term noise, 114 hle_failure paused, 1 evidence_conflict)
+- Action this tick: committed fix 332057d — added "error code: 500" to the 500-error recovery branch in agent_loop.py; llama.cpp returns "Error code: 500 - {..." not "500 internal server error", so the tool-call drop + truncation advice path was silently bypassed for all JSON-parse-error 500s; the bad tool call was re-sent unchanged on every retry; auto_release will ship at next CDT tick
+
+## 2026-05-17 19:30 UTC tick
+- Stress: PID 2501045, ~02:35 elapsed, tool_agent suite step ~250+/1658, running cleanly
+- Write rate: N/A
+- Admiral last 30 min: 3 harness:thinking_stall fires at 18:20, 1 at 18:40 (all informational — nudge-inject path working as designed)
+- llamacpp 400s: 6 minor errors in container logs (none JSONDecode/400-class)
+- GH issues: 0 open
+- Dispatch queue: harness=1309 (9 in last 24h, all thinking_stall resolved), retrieval=0 actionable (drain: 0 ingested), curiosity=2646 pending (top: hle_failure banned, unknown_term noise, evidence_conflict stale)
+- Action this tick: no action — system healthy; model Q3_K_M + balancer :8001 both up; stress advancing; HLE paused per directive; no actionable bugs found
+
+## 2026-05-17 19:00 UTC tick
+- Stress: 192/1658 (PID 2501045, 02:04 elapsed, tool_agent suite, 154 done / 0 skip / 0 timeout since restart at 16:56 UTC)
+- Write rate: low (~2/92 steps show writes — normal for informational prompts on an existing package)
+- Admiral last 30 min: 1 harness:thinking_stall fire at 18:40 UTC (nudge injected, working as designed)
+- llamacpp 400s: 0 new (6 minor errors in container logs, none JSONDecode/400 class)
+- GH issues: 0 open
+- Dispatch queue: harness=10 last 24h (all thinking_stall, resolved by existing logic), retrieval=0 actionable (drained), curiosity=2625 pending (top items: hle_failure=409 banned, unknown_term=2215 noise, evidence_conflict=1 stale file-not-found)
+- Action this tick: no action — system healthy; autonomous_review also found no actionable items in 17:00/17:30/18:00/18:30 ticks; v2.8.56 is current with context-overflow fix holding
+
+## 2026-05-17 18:30 UTC tick
+- Stress: step ~676/1658, running (PID 2501045, ~97 min elapsed, tool_agent prompt suite; some SKIP/FORCE-RESET on API-server prompts per known modal-eat issue)
+- Write rate: N/A (log shows +7 writes/session typical)
+- Admiral last 30 min: 3 harness:thinking_stall fires at 18:20 UTC (empty_after_tool:bash; nudges injected as expected — working, not a new bug)
+- llamacpp 400s: 6 context-overflow errors in last hour (down from 34/hr pre-fix; residual from long sessions; 1bcd5d1 fix holding for new sessions)
+- GH issues: 0 open
+- Dispatch queue: harness=1308 total (10 in last 24h, all thinking_stall resolved by existing nudge logic), retrieval=3 (0 actionable, all recently ingested), curiosity=3021 total / 2615 pending (all HLE failures banned or unknown_term noise)
+- Action this tick: no action — system healthy; no actionable bugs; retrieval drain: 0 ingested (already up to date)
+
 ## 2026-05-17 18:00 UTC tick
 - Stress: step 114/1658, running (PID 2501045, ~64 min elapsed, tool_agent prompt suite, ~62 tok/s, healthy)
 - Write rate: N/A (no per-prompt write rate in stress output)

drydock_cli-2.8.56/.auto_release.lock

@@ -1 +0,0 @@
-2525683