drydock-cli 2.6.119__tar.gz → 2.6.121__tar.gz

drydock_cli-2.6.121/.claude/scheduled_tasks.lock

@@ -0,0 +1 @@
+{"sessionId":"62611415-bc7c-4c6e-9aff-0f2dfa34b91f","pid":1692407,"acquiredAt":1776330915282}

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: drydock-cli
-Version: 2.6.119
+Version: 2.6.121
 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.6.119 → drydock_cli-2.6.121}/drydock/core/agent_loop.py

@@ -1556,8 +1556,18 @@ class AgentLoop:
 
         if last.role == Role.user:
             content = str(last.content or "")
-            # System note / loop nudge → act immediately
-            if "[SYSTEM" in content:
+            # System note / loop nudge → act immediately.
+            # BUT only when the whole message is the note. _auto_route_task
+            # appends "[SYSTEM: PROJECT FILES ...]" AFTER the user's actual
+            # prompt ("sha1 hash\n\n[SYSTEM: ...]"), and turning thinking
+            # off on those caused the 2026-04-16 stress regression: Gemma 4
+            # returned empty responses for every prompt after the initial
+            # build, only recovering after /clear (which wiped the context
+            # including the project-file injection). Only strip thinking
+            # when the message STARTS with [SYSTEM: — i.e. it's a pure
+            # injection, not a user ask with context appended.
+            stripped = content.lstrip()
+            if stripped.startswith("[SYSTEM"):
                 return "off"
             # Real user message → full thinking (they're asking something new)
             return base

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/drydock/core/tools/builtins/write_file.py

@@ -393,17 +393,19 @@ class WriteFile(
         file_path, file_existed, content_bytes = self._prepare_and_validate_path(args)
 
         # Read-before-Write enforcement (Claude Code tool contract).
-        # Overwriting a file the model hasn't read this session is the
-        # root cause of the oscillation loop: model writes broken V1,
-        # gets syntax warning, writes broken V2, gets different warning,
-        # writes V1 again, etc. Forcing it to read first means it CAN
-        # see the current state and do targeted search_replace instead.
-        # Returned as a structured no-op result (not ToolError) so the
-        # model doesn't panic — per Claude Code pattern and per
-        # feedback_no_tool_errors_for_loop_detection.md.
+        # Only applies when overwrite=False — if the caller explicitly
+        # passed overwrite=True (the default), honor that intent and do
+        # the write. Blocking an explicit overwrite on "read it first"
+        # caused an infinite loop in the 2026-04-16 stress run: a stale
+        # 22-byte __init__.py from a prior test triggered the advisory,
+        # and the model kept retrying write_file with overwrite=True —
+        # each call returned bytes_written=0 with the same reminder,
+        # the model never escaped, and drydock eventually died from
+        # consecutive API errors. Per feedback_no_tool_errors_for_loop_detection.md
+        # the safety net must not become its own loop source.
         read_state = ctx.read_file_state if ctx else None
         path_key = str(file_path)
-        if file_existed and read_state is not None:
+        if file_existed and read_state is not None and not args.overwrite:
             prior = read_state.get(path_key)
             current_mtime = 0
             try:
@@ -422,7 +424,8 @@ class WriteFile(
                         "see the current contents, then either:\n"
                         "  • edit with search_replace for targeted changes, "
                         "or\n"
-                        "  • call write_file again to do a full rewrite.\n"
+                        "  • call write_file again with overwrite=true to "
+                        "do a full rewrite.\n"
                         "This write was NOT applied to disk.\n"
                         "</system-reminder>"
                     ),

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/pyproject.toml

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

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/scripts/deploy_to_github.sh

@@ -91,4 +91,18 @@ EOF
 # Push
 git push 2>&1 | grep -v "^remote:" || true
 
+# Tag the GitHub-side commit with vX.Y.Z if a version was passed.
+# Local tags point to local dev commits that don't exist on the remote
+# (we use rsync + Daily sync commits, so git history diverges), so local
+# tags can't be pushed — we tag the synthetic sync commit instead so
+# GitHub's Releases / tag view stays current. See learning 2026-04-16.
+RELEASE_VERSION="${1:-${RELEASE_VERSION:-}}"
+if [ -n "$RELEASE_VERSION" ]; then
+    git -c user.name="Drydock Deploy" -c user.email="deploy@drydock" \
+        tag -a "v$RELEASE_VERSION" -m "Release v$RELEASE_VERSION" 2>/dev/null || \
+        log "WARN: tag v$RELEASE_VERSION already exists on remote — skipping"
+    git push origin "v$RELEASE_VERSION" 2>&1 | grep -v "^remote:" || true
+    log "Tagged remote with v$RELEASE_VERSION"
+fi
+
 log "Deploy complete. $(git log --oneline -1)"

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/scripts/notify_release.py

@@ -8,6 +8,15 @@ BOT_TOKEN = "8488479213:AAGd2tMUrqc-Xse14IQ6yfoMudAAal7odio"
 CHAT_ID = 8431425848
 
 
+def _escape_markdown(text: str) -> str:
+    """Escape the Telegram legacy-Markdown special chars that commonly
+    appear in commit messages: _ * ` [ ]. Telegram's 400 Bad Request
+    response fires when these are unbalanced."""
+    for ch in ("_", "*", "`", "[", "]"):
+        text = text.replace(ch, f"\\{ch}")
+    return text
+
+
 def send_telegram(message: str, parse_mode: str = "Markdown"):
     url = f"https://api.telegram.org/bot{BOT_TOKEN}/sendMessage"
     params = {
@@ -21,6 +30,17 @@ def send_telegram(message: str, parse_mode: str = "Markdown"):
         urllib.request.urlopen(url, data, timeout=10)
     except Exception as e:
         print(f"Telegram send failed: {e}")
+        # Retry in plain text if Markdown parse failed — this fires when
+        # a commit message has unbalanced underscores from identifiers
+        # like `write_file` or `search_replace`.
+        if parse_mode:
+            fallback_params = {"chat_id": CHAT_ID, "text": message}
+            fallback_data = urllib.parse.urlencode(fallback_params).encode()
+            try:
+                urllib.request.urlopen(url, fallback_data, timeout=10)
+                print("Retried in plain text — delivered.")
+            except Exception as e2:
+                print(f"Plain-text retry also failed: {e2}")
 
 
 if __name__ == "__main__":

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/scripts/publish_to_pypi.sh

@@ -67,9 +67,12 @@ git commit -m "Bump version to $NEW_VERSION for PyPI release
 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>" 2>/dev/null || true
 
 # --- Deploy to GitHub too ---
+# Pass NEW_VERSION so deploy_to_github.sh can tag the synthetic sync
+# commit — local tags can't be pushed because our rsync + Daily-sync
+# approach means local and remote histories are disjoint.
 if [ -x "$DRYDOCK_SRC/scripts/deploy_to_github.sh" ]; then
     log "Deploying to GitHub..."
-    "$DRYDOCK_SRC/scripts/deploy_to_github.sh" 2>&1 || log "GitHub deploy failed (non-fatal)"
+    "$DRYDOCK_SRC/scripts/deploy_to_github.sh" "$NEW_VERSION" 2>&1 || log "GitHub deploy failed (non-fatal)"
 fi
 
 # --- Git tag ---
@@ -93,7 +96,32 @@ fi
 rm -rf "$TMPVENV"
 
 # --- Send Telegram notification ---
-COMMIT_MSG=$(git log --oneline -1 2>/dev/null | cut -d' ' -f2-)
+# Pull the most recent meaningful commit (skip version-bump and auto-release
+# commits so the summary actually describes what changed).
+COMMIT_MSG=$(git log --oneline -n 10 --pretty=format:'%s' 2>/dev/null \
+    | grep -vE '^(Bump version|v[0-9]+\.[0-9]+\.[0-9]+:|Daily sync|Auto-release)' \
+    | head -1)
+if [ -z "$COMMIT_MSG" ]; then
+    COMMIT_MSG=$(git log --oneline -1 2>/dev/null | cut -d' ' -f2-)
+fi
+
+# Append highest step reached by the most recent 2000-step stress run.
+# Helps the release note show progress: "last run got to 42/1658 before
+# the regression — this fix should push past it."
+LAST_STRESS_LOG=$(ls -1t /tmp/stress_2000_*.log 2>/dev/null | head -1)
+if [ -n "$LAST_STRESS_LOG" ]; then
+    STRESS_MAX=$(grep -oE '^\[ *[0-9]+/[0-9]+\]' "$LAST_STRESS_LOG" 2>/dev/null \
+        | tr -d '[] ' | awk -F/ '{print $1}' | sort -n | tail -1)
+    STRESS_TOTAL=$(grep -oE '^\[ *[0-9]+/[0-9]+\]' "$LAST_STRESS_LOG" 2>/dev/null \
+        | tr -d '[] ' | awk -F/ '{print $2}' | head -1)
+    if [ -n "$STRESS_MAX" ] && [ -n "$STRESS_TOTAL" ]; then
+        STRESS_LOG_NAME=$(basename "$LAST_STRESS_LOG")
+        COMMIT_MSG="${COMMIT_MSG}
+
+Previous stress run (${STRESS_LOG_NAME}) reached ${STRESS_MAX}/${STRESS_TOTAL} steps before stopping."
+    fi
+fi
+
 $PYTHON "$DRYDOCK_SRC/scripts/notify_release.py" "$NEW_VERSION" "$COMMIT_MSG" 2>/dev/null || true
 
 log "Published drydock-cli $NEW_VERSION to PyPI"

{drydock_cli-2.6.119 → drydock_cli-2.6.121}/uv.lock

@@ -326,7 +326,7 @@ wheels = [
 
 [[package]]
 name = "drydock-cli"
-version = "2.6.118"
+version = "2.6.120"
 source = { editable = "." }
 dependencies = [
     { name = "agent-client-protocol" },

drydock_cli-2.6.119/.claude/scheduled_tasks.lock

@@ -1 +0,0 @@
-{"sessionId":"facd51cc-fa47-4911-afc8-14485ae9caf3","pid":711220,"acquiredAt":1775966390914}