drydock-cli 2.8.49__tar.gz → 2.8.50__tar.gz

drydock_cli-2.8.50/.auto_release.lock

@@ -0,0 +1 @@
+2480262

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/CLAUDE.md

@@ -43,57 +43,61 @@ Drydock is a local CLI coding agent (fork of mistral-vibe, Apache 2.0).
 - **370 PRDs** at /data3/drydock_test_projects/ — the benchmark suite
 - **Current version:** v2.8.27 on PyPI (auto-released every 6h from `main`)
 - **Active continuous loops:** stress harness (hourly), autonomous_review
-  (30-min), classify_pulse (10-min), telegram_bot keepalive (2-min),
-  hle_babysitter (hourly @ :45 — 10-Q HLE batch per tick, see
-  HLE_PRD §"Continuous HLE evaluation"), **hle_burndown daemon** (back-to-back
-  batches, runs as background process via `scripts/hle_burndown.sh start`;
-  keepalive cron at `*/15` resurrects if it dies). Both HLE loops share
-  `/tmp/hle_continuous.pid` — whichever owns the lock keeps it; the other
-  exits/skips. Anything new the operator adds should not run at :00 or
-  :30 (autonomous_review owns those).
-
-## Current plan (2026-05-14)
-
-Three vectors moving in parallel. Each has a queue of concrete fixes
-tracked as TaskCreate items; the high-level shape is:
-
-1. **HLE** — keep pushing the floor up from 6.7% on Math. The
-   `scripts/hle_babysitter.sh` cron runs 10-Q Math batches every hour.
-   Open work: rotate categories beyond Math; build a multi-batch
-   aggregator (`scripts/hle_aggregate.py`); produce a clean Q3 vs Q4
-   stall-rate comparison once 30+ Q3 Math attempts have accumulated;
-   verify the gemma4.md tool-inventory change (e47cc4e) actually
-   lifted math/count/memory/verify call rates.
-
-2. **GraphRAG** — the auto-prefetch hook is shipping good chunks on
-   trivia but not on hard symbolic Math. Two concrete moves: lower
+  (30-min), classify_pulse (10-min), telegram_bot keepalive (2-min).
+  HLE eval loops were removed 2026-05-17 per operator directive — see
+  the "NO CUSTOM EVAL HARNESSES" rule below.
+- 🚨 **NO CUSTOM EVAL HARNESSES (2026-05-17).** The user has banned
+  bespoke evaluation infrastructure (HLE eval scripts, burndown
+  daemons, batch runners, judge-prompt pipelines, telemetry-aggregator
+  cron jobs, etc.). Even when such a harness drives the real TUI via
+  pexpect, the *concept* tempts the agent to fix harness-specific
+  issues (timeout tuning, env-var-gated behaviour, judge edge cases)
+  that don't help real users. Improving drydock comes from USING
+  drydock interactively as a real user does — the operator notices
+  pain, the agent fixes the pain. If you need a regression check,
+  write a unit test against the drydock library. If you need a
+  benchmark, run prompts through the TUI by hand and observe. Do
+  NOT spin up background eval daemons. Archived scripts at
+  `scripts/_archived_eval_harness/` — leave them archived.
+
+## Current plan (2026-05-17)
+
+Focus is on **TUI experience** — the operator uses drydock interactively;
+the agent fixes what the operator hits. No HLE eval loops, no custom
+benchmark daemons (see the "NO CUSTOM EVAL HARNESSES" rule above).
+
+1. **TUI bugs the operator notices in real use** — error recovery
+   paths, slash commands, tool reliability. Recent ships: /undo,
+   /back, /goal, vision (--mmproj), recovery meta-fix.
+
+2. **GraphRAG** — the auto-prefetch hook ships good chunks on trivia
+   but not on hard symbolic Math. Two concrete moves: lower
    `QUALITY_THRESHOLD` (currently 8.0 in `agent_loop.py:3391`) once
-   we know the real score distribution, and add an arxiv-corpus
-   fallback (`/data3/arxiv_corpus/graphrag.sqlite`) when the primary
-   index returns nothing above threshold.
+   we know the real score distribution, and the arxiv-corpus
+   fallback (`/data3/arxiv_corpus/graphrag.sqlite`) is wired.
 
 3. **Deep Noir** — sidecar/hooks/capture/train all coded; the
    `apply_chat_template` API-drift fix shipped 2026-05-14 (f02aa4b).
-   Real blocker for v1 vectors: contrastive-pair extraction is
-   currently broken — admiral records full UUIDs (e.g.
-   `5b55aacd-3606-4656-ad4b-eacf86506eda`) but session dirs are named
-   `session_<date>_<time>_<short_uuid>` where the `short_uuid` is the
-   first 8 chars of the SESSION's own UUID, not admiral's recorded
-   one. `extract_pairs._find_session_dir` matches on session_dir name
-   endswith(admiral_short) which only succeeds for the rare case
-   where both happen to match. Yield on `empty_after_tool:bash`:
-   2 / 88 derailed sessions found. Needs a real mapping layer
-   (meta.json → admiral) or admiral has to be fixed to record the
-   short hash used by session dirs.
+   Contrastive-pair extraction was fixed by **706f226 (2026-05-10)**:
+   admiral now records the live `agent_loop.session_id` (which IS the
+   short hash used by session dirs), and `extract_pairs._find_session_dir`
+   builds a `{meta.session_id → dir}` map from the on-disk
+   meta.json files. Both pieces work.
+   Real remaining issue: **admiral_state.json has ~3000 pre-fix
+   findings (recorded 2026-04-19 to 2026-05-10) whose UUIDs are
+   phantom — they don't resolve to any on-disk session_dir**.
+   `extract_pairs` correctly yields only the post-fix findings (~20
+   sessions across all categories as of 2026-05-17). The training
+   set will fill in as new findings accumulate. Pre-fix findings
+   are unrecoverable; consider GC'ing them out of admiral_state.json
+   so future audits aren't misleading.
 
 Operator controls for the continuous loops:
 
 ```bash
-touch /data3/drydock/.pause_hle_babysitter           # pause hourly HLE cron
-touch /data3/drydock/.pause_hle_burndown             # pause back-to-back burndown daemon
-touch /data3/drydock/.pause_hle_burndown_keepalive   # disable burndown auto-resurrection
 touch /data3/drydock_test_projects/.pause_watchdog
 touch /data3/drydock/.pause_auto_release             # pause 6h PyPI publish
+touch /data3/drydock/.pause_stress                   # pause stress harness restarts
 ```
 
 ## Build & Test

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/PKG-INFO

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

@@ -1369,7 +1369,8 @@ class AgentLoop:
                     prev_tool_name = assistant_msg.tool_calls[-1].function.name if assistant_msg.tool_calls[-1].function else None
             _readonly_tools = {"read_file", "grep", "glob", "ls", "pwd",
                                "ralph_repo_index", "ralph_file_summary",
-                               "retrieve", "search_files", "lsp"}
+                               "retrieve", "search_files", "lsp",
+                               "web_search", "web_fetch"}
             _write_tools = {"write_file", "search_replace"}
             _prev_was_read = prev_tool_name in _readonly_tools
             _prev_was_write = prev_tool_name in _write_tools
@@ -1471,10 +1472,12 @@ class AgentLoop:
                     )
                 elif _prev_was_read:
                     _tool_name_str = prev_tool_name or "read_file"
+                    _generic_suffix = os.environ.get("DRYDOCK_STOP_NOW_SUFFIX", "")
                     note = (
                         f"You called {_tool_name_str} but produced no output. "
-                        f"Now use write_file, search_replace, or bash "
-                        f"to make changes — do NOT call {_tool_name_str} again."
+                        f"Now respond in text — write your answer or make changes. "
+                        f"Do NOT call {_tool_name_str} again."
+                        + (f" {_generic_suffix}" if _generic_suffix else "")
                     )
                 elif _prev_write_success:
                     note = (
@@ -1534,11 +1537,12 @@ class AgentLoop:
                     )
                 elif _prev_was_read:
                     _tool_name_str = prev_tool_name or "read_file"
+                    _generic_suffix = os.environ.get("DRYDOCK_STOP_NOW_SUFFIX", "")
                     note = (
                         f"You sent an empty response after calling {_tool_name_str}. "
-                        f"Call write_file or search_replace NOW to apply "
-                        f"what you read — OR state in one sentence why you "
-                        f"cannot proceed. Do NOT call {_tool_name_str} again."
+                        f"Respond in text now — write your answer or apply what you read. "
+                        f"Do NOT call {_tool_name_str} again."
+                        + (f" {_generic_suffix}" if _generic_suffix else "")
                     )
                 elif _prev_was_write:
                     _tool_name_str = prev_tool_name or "write_file"
@@ -1589,11 +1593,12 @@ class AgentLoop:
                     )
                 elif prev_tool_name in _readonly_tools:
                     _tool_name_str = prev_tool_name or "read_file"
+                    _generic_suffix = os.environ.get("DRYDOCK_STOP_NOW_SUFFIX", "")
                     note = (
                         f"THIRD empty response after {_tool_name_str}. "
-                        "Stop reading — call write_file or search_replace NOW to apply "
-                        "the change, or respond in text explaining why you cannot proceed. "
+                        "Stop — respond in text with your analysis or best answer. "
                         f"Do NOT call {_tool_name_str} again."
+                        + (f" {_generic_suffix}" if _generic_suffix else "")
                     )
                 elif _prev_was_write:
                     _tool_name_str = prev_tool_name or "write_file"
@@ -3642,9 +3647,23 @@ class AgentLoop:
         # corpus at /data3/arxiv_corpus/graphrag.sqlite (1.18M chunks)
         # has much better recall. The fallback path is operator-tunable
         # via DRYDOCK_GRAPHRAG_FALLBACK_DB; set to empty to disable.
-        primary_db = os.environ.get("DRYDOCK_GRAPHRAG_DB") or str(
-            Path.home() / ".drydock" / "graphrag.sqlite"
-        )
+        # Primary DB selection mirrors retrieve._resolve_db_path so the
+        # auto-prefetch and the model-issued retrieve calls always agree
+        # on which corpus to search:
+        #   1. DRYDOCK_GRAPHRAG_DB env override
+        #   2. <cwd>/.drydock/graphrag.sqlite (per-project index)
+        #   3. ~/.drydock/graphrag.sqlite (home fallback)
+        # Without #2, a user with a populated home DB never saw their
+        # own project's chunks because home always won.
+        env_db = os.environ.get("DRYDOCK_GRAPHRAG_DB")
+        if env_db:
+            primary_db = env_db
+        else:
+            project_db = Path.cwd() / ".drydock" / "graphrag.sqlite"
+            if project_db.is_file():
+                primary_db = str(project_db)
+            else:
+                primary_db = str(Path.home() / ".drydock" / "graphrag.sqlite")
         fallback_default = "/data3/arxiv_corpus/graphrag.sqlite"
         fallback_db_raw = os.environ.get(
             "DRYDOCK_GRAPHRAG_FALLBACK_DB", fallback_default

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/drydock/core/tools/builtins/retrieve.py

@@ -78,6 +78,15 @@ def _resolve_db_path(arg: str) -> Path:
     project_db = Path.cwd() / ".drydock" / "graphrag.sqlite"
     if project_db.is_file():
         return project_db
+    # If we're inside a real project that doesn't yet have its own index,
+    # PREFER to create a per-project index over falling back to the home
+    # index (which is contaminated with other projects' content and
+    # answers wrong queries about THIS project). The home index is only
+    # the right answer for ad-hoc use outside any project — e.g. when
+    # the user runs drydock from their home dir.
+    cwd = Path.cwd()
+    if _looks_like_project(cwd):
+        return project_db  # will be auto-ingested by Retrieve.run
     return Path.home() / ".drydock" / "graphrag.sqlite"
 
 

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/pyproject.toml

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

drydock_cli-2.8.50/scripts/_archived_eval_harness/README.md

@@ -0,0 +1,38 @@
+# Archived 2026-05-17 — DO NOT RESURRECT
+
+These scripts implemented a custom HLE eval harness that drove drydock
+via pexpect. The infrastructure was technically TUI-based (it spawned
+the real `drydock` binary), but the user objected to the entire
+*concept* of building bespoke evaluation infrastructure on the side:
+
+> "STOP trying to create custom harnesses for evals. Improving drydock
+>  is what matters. And using drydock can't be headless, you have to
+>  actually use it like the user would."
+
+The principle: **drydock improvements should come from USING drydock
+as a real user would** — interactively, with the user noticing pain
+points and the agent fixing them. A custom eval harness:
+
+  1. Tempts the agent to fix harness-specific issues (timeout tuning,
+     env-var-gated behavior, judge-prompt edge cases) that don't help
+     real users.
+  2. Introduces operational overhead (cron jobs, keepalive daemons,
+     telemetry pipelines) that's parallel to the actual product.
+  3. Distracts from the headline goal: make drydock better at what
+     real users do, not at what an eval suite measures.
+
+If you (future Claude) are tempted to build a new HLE-style eval
+harness, STOP. Read `~/.claude/projects/-data3-drydock/memory/
+feedback_no_custom_eval_harness.md` first. The user has been very
+clear on this and will push back hard.
+
+What to do instead:
+  - Use the drydock TUI yourself (or watch the user use it) to find
+    real bugs.
+  - Read open GH issues at fbobe321/drydock for user-reported pain.
+  - Fix things that affect interactive UX: error recovery, slash
+    commands, tool reliability.
+  - If you really need a regression-style check, write a unit test
+    against the drydock library — not a long-running eval daemon.
+
+Files preserved here for git history continuity; do not run them.

drydock_cli-2.8.49/scripts/hle_eval.py → drydock_cli-2.8.50/scripts/_archived_eval_harness/hle_eval.py.deprecated

@@ -65,7 +65,7 @@ HF_TOKEN_FILE = Path.home() / ".config" / "drydock" / "hf_token"
 # Coding-style PRDs in shakedown allow 600s for harder steps; QA should be
 # faster since there's no file-writing iteration, but Gemma 4 thinking can
 # still chew through several minutes on a hard question.
-QUESTION_TIMEOUT = 480  # 8 min per question
+QUESTION_TIMEOUT = 600  # 10 min per question — 480s left 3/196 recent cases killed mid-generation
 IDLE_GRACE = 8.0        # seconds of no new messages before declaring done
 
 

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/trip_log.md

@@ -1,5 +1,86 @@
 # Drydock Trip Log
 
+## 2026-05-17 15:30 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2465533 engineering batch, slot 59, ~51 min elapsed), lifetime 115/848 = 13.6% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.3%, Chem 8.7%); babysitter skipping correctly while burndown active
+- Write rate: N/A (stress paused)
+- Admiral last 30 min: not checked (stress paused)
+- vLLM 400s: 0 observed
+- GH issues: 0 open
+- Dispatch queue: harness=7 (all thinking_stall from 2026-05-15, already addressed by recent commits), retrieval=3 (0 actionable — all already ingested), steering=0, curiosity=2546 pending (top 3 are hle_failure/no-FINAL-ANSWER pattern, covered by commits a9f16ae/4909542/d500234)
+- retrieval-drain: 0 projects ingested (nothing new)
+- Model: Q3_K_M via llama.cpp :8000 healthy; balancer :8001 healthy
+- Action this tick: no action — healthy; recent 24h commits are actively addressing HLE stall/FINAL-ANSWER pattern; curiosity top items already covered
+
+## 2026-05-17 14:30 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2452616 chemistry batch in progress), lifetime 115/841 = 13.7% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.3%, Chem 8.7%, Other 18.2%, Engineering 4.7%, Hum/SS 14.3%); latest batch chemistry 1/10
+- Write rate: N/A (stress paused)
+- vLLM 400s: 0; llamacpp-gemma4 healthy; balancer on :8001 healthy
+- GH issues: 0 open
+- Dispatch queue: harness=7 (all thinking_stall, stale pre-fix), retrieval=3 (nothing actionable), curiosity=2934 total/2525 pending/406 consumed
+- Action this tick: committed fix a9f16ae (addresses curiosity:01c0f4dc34d97142, :fbe7b3456bdbb0ca, :4ffd02384a890963) — stall-retry _prev_was_read notes at attempts 0 and 1 now append DRYDOCK_STOP_NOW_SUFFIX ("FINAL ANSWER: <answer>") which 4909542 only did for attempt 2; also neutralized coding-task wording ("write_file, search_replace") to context-neutral ("respond in text — write your answer or make changes"). No-op for coding sessions (suffix unset by default).
+
+## 2026-05-17 14:00 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2452616, slot 58 chemistry), lifetime 114/837 = 13.6% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.3%, Chem 7.8%); recent batch Physics 20%
+- Write rate: N/A (stress paused)
+- Admiral last 30 min: N/A
+- vLLM 400s: 0; llamacpp-gemma4 healthy (25h uptime)
+- GH issues: 0 open
+- Dispatch queue: harness=1305 total (8 in last 24h, thinking_stall, already addressed by v2.8.47+), retrieval=3 (nothing actionable), curiosity=2931 total (2524 pending, 403 consumed)
+- Action this tick: consumed curiosity acf1a1892044a747 (thinking-budget timeout case — addressed by 2973dd1 QUESTION_TIMEOUT 480→600s). Investigated ongoing empty-pred failures in physics batch (3 questions produced pred='' in run_1779013132 after FINAL ANSWER fixes) — these are hard-QA questions where model likely times out during inference before producing output; pattern requires deeper session log analysis, leaving for next autonomous_review tick.
+
+## 2026-05-17 13:30 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 1742185, 3+ days elapsed), lifetime 114/832 = 13.7% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.3%, Chem 8.5%); recent batches: Humanities 30%, Physics 20%, Physics 10%
+- Write rate: N/A (stress paused)
+- vLLM 400s: 0 in last 30min (llamacpp-gemma4 Q3_K_M healthy on :8000, balancer :8001 up)
+- GH issues: 0 open
+- Dispatch queue: harness=8 (all historical thinking_stall, resolved v2.8.47), retrieval=3 (all recently ingested, 0 actionable), curiosity=2513 pending (409 hle_failure, 2107 unknown_term)
+- Action this tick: consumed 3 stale hle_failure curiosity items (da424f73, 5c2ad87e, 4f4de190 — empty:no_final_answer cases addressed by d500234/4909542 stall-retry FINAL ANSWER suffix fixes); observed 1 new empty:no_response at 601s in Humanities batch (poetry question) — non-streaming HTTP timeout still hitting first-turn for some questions; no code change this tick as system otherwise healthy and autonomous_review just completed 13:00Z tick
+
+## 2026-05-17 13:00 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2440503, 27min elapsed), lifetime 112/825 = 13.6% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.3%, Chem 8.5%); recent batches variable (0-50%)
+- Write rate: N/A (stress paused)
+- Admiral last 30 min: N/A (stress paused)
+- vLLM 400s: N/A (llamacpp container, not vLLM)
+- GH issues: 0 open
+- Dispatch queue: harness=8 (all historical, thinking_stall resolved v2.8.47), retrieval=3 (all already ingested), curiosity=2504 pending
+- Action this tick: consumed 3 stale pre-fix curiosity items (FINAL ANSWER + timeout artifacts addressed by d500234/4909542/2973dd1); no new bugs found; autonomous_review running concurrently at 13:00Z
+
+## 2026-05-17 12:30 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running slot 56 (PID 2425424, 69min elapsed, physics batch — Q10 in progress), lifetime 111/821 = 13.5% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 8.5%, Chem 8.5%, Other unchanged)
+- Write rate: N/A (stress paused)
+- vLLM 400s: 0 in last 30min, llamacpp-gemma4 healthy (Q3_K_M)
+- GH issues: 0 open
+- Dispatch queue: harness=8 (all stale thinking_stall, resolved v2.8.47); retrieval=0 actionable (3 entries, all recently ingested); curiosity=2488 pending — consumed 3 stale hle_failure artifacts (532e9d22, 77d0d52, 44f4d505 — hard theoretical questions: Tate-graph/μ-fixpoint, DomSet complexity, SU(N) structure constants; model capability gap, not addressable by prompt rules)
+- 12:00Z autonomous_review tick hit $1 USD budget cap and exited early (exit=1)
+- Action this tick: no code change — system nominal; consumed 3 curiosity items; retrieval drain 0 new ingestions
+
+## 2026-05-17 12:00 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2425424, physics batch in progress), lifetime 110/817 = 13.5% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 7.5%, Chem 8.5%, Other 18.2%)
+- Write rate: N/A (stress paused)
+- Admiral: autonomous_review tick started at 12:00Z
+- vLLM 400s: 0 in last 30min, model healthy
+- GH issues: 0 open
+- Dispatch queue: harness=9 (all thinking_stall, stale from 2026-05-16); retrieval=0 actionable; curiosity=2488 pending (hle_failure=407, unknown_term=2081)
+- Action this tick: committed fix — QUESTION_TIMEOUT 480→600s in hle_eval.py; all 3 recent empty:no_final_answer cases elapsed exactly at deadline (model killed mid-generation); retrieval drain: 0 actionable; curiosity top item (threshold-sig scheme) marked consumed (42e0bdf8)
+
+## 2026-05-17 11:30 UTC tick
+- Stress: PAUSED (.pause_stress sentinel active)
+- HLE burndown: running (PID 2425424, 08:50 elapsed, physics slot 56 active), lifetime 109/813 = 13.4% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Physics 6.3%, Chem 8.5%, Other 18.2%)
+- Write rate: N/A (stress paused)
+- Admiral last 30 min: autonomous_review tick started at 11:30Z
+- vLLM 400s: 3 matches in docker grep (benign — reasoning-budget activation noise, Q3_K_M healthy, 23376 tok prompt for physics slot)
+- GH issues: 0 open
+- Dispatch queue: harness=9 (all stale, thinking_stall resolved by v2.8.47); retrieval=0 actionable; curiosity=2478 pending (top 3 are today's physics no_response failures — spinor/scalar field + Z-boson EW + virial series; model timed out at 480s with msg_count=1; not addressable by prompt changes)
+- Retrieval drain: 0 projects (3 queue entries, all already ingested)
+- Action this tick: no code change — system nominal; harness:thinking_stall pattern confirmed stale (last dispatch evidence says "fully resolved by v2.8.47"); top curiosity items are empty:no_response physics timeouts where model never starts within 480s, distinct from the empty:no_final_answer cases targeted by recent FINAL ANSWER suffix commits
+
 ## 2026-05-17 10:30 UTC tick
 - Stress: PAUSED (.pause_stress sentinel active)
 - HLE burndown: running (PID 2412661, physics batch active, 12min elapsed), lifetime 108/803 = 13.4% (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%, Chem 8.5%, Other 18.2%)
@@ -7365,3 +7446,13 @@ restarted, cron self-match bug fixed in this same session).
 - Previous batch (23:52 UTC, 10 Math questions): 0/10 — all 480s timeouts on hard questions (fuzzy logic, semilattice functors, Boolean prime implicants); model outputs show reasoning fragments not clean FINAL ANSWER — capability gap, not a drydock bug
 - Current batch (01:13 UTC): 2/4 correct so far (chess Q1 YES exact, Cauchy Q3 YES fuzzy) after recent stall-retry fixes; still running
 - Action this tick: consumed curiosity:982cd07192229b9e (LSH-threshold model-used-tools-but-no-FINAL-ANSWER — addressed by 23f65dc + e20fb7b stall-retry guards); no code fix committed — system healthy, recent fixes still being evaluated by burndown daemon
+
+## 2026-05-17 11:00 UTC tick
+- Stress: paused via .pause_stress sentinel (expected)
+- Write rate: N/A (stress paused)
+- Admiral last 30 min: N/A
+- vLLM 400s: 10 (within llamacpp normal range, no errors logged)
+- GH issues: 0 open
+- Dispatch queue: harness=9 (all stale thinking_stall, addressed by v2.8.47+v2.8.48), retrieval=0 actionable, curiosity=2468 pending (402 hle_failure, 2066 unknown_term)
+- HLE: lifetime 13.5% across 809 questions (Math 17.8%, CS/AI 6.8%, Bio/Med 13.2%); burndown daemon running (PID 2412661, physics batch)
+- Action this tick: committed fix (4909542) — readonly-tool stall-retry note was saying "call write_file or search_replace NOW" (wrong for HLE) and omitting DRYDOCK_STOP_NOW_SUFFIX; fixed to say "respond in text with analysis/best answer" and append the FINAL ANSWER suffix; consumed curiosity:87cf3274e4ba6912

{drydock_cli-2.8.49 → drydock_cli-2.8.50}/uv.lock

@@ -326,7 +326,7 @@ wheels = [
 
 [[package]]
 name = "drydock-cli"
-version = "2.8.42"
+version = "2.8.49"
 source = { editable = "." }
 dependencies = [
     { name = "agent-client-protocol" },
@@ -347,6 +347,7 @@ dependencies = [
     { name = "pydantic-settings" },
     { name = "pypdf" },
     { name = "pyperclip" },
+    { name = "pytholog" },
     { name = "pyyaml" },
     { name = "rich" },
     { name = "textual" },
@@ -400,6 +401,7 @@ requires-dist = [
     { name = "pydantic-settings", specifier = ">=2.12.0" },
     { name = "pypdf", specifier = ">=4.0.0" },
     { name = "pyperclip", specifier = ">=1.11.0" },
+    { name = "pytholog", specifier = ">=2.4.1" },
     { name = "pyyaml", specifier = ">=6.0.0" },
     { name = "rich", specifier = ">=14.0.0" },
     { name = "textual", specifier = ">=7.4.0" },
@@ -1422,6 +1424,18 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/ca/31/d4e37e9e550c2b92a9cbc2e4d0b7420a27224968580b5a447f420847c975/pytest_xdist-3.8.0-py3-none-any.whl", hash = "sha256:202ca578cfeb7370784a8c33d6d05bc6e13b4f25b5053c30a152269fd10f0b88", size = 46396, upload-time = "2025-07-01T13:30:56.632Z" },
 ]
 
+[[package]]
+name = "pytholog"
+version = "2.4.1"
+source = { registry = "https://pypi.org/simple" }
+dependencies = [
+    { name = "more-itertools" },
+]
+sdist = { url = "https://files.pythonhosted.org/packages/01/87/cffd13adb88483ac677ad2d3bbde3156790cf71db8e9436ac66c2fb8ede9/pytholog-2.4.1.tar.gz", hash = "sha256:ef9b379dd21f755ee5e097e80ce1475e5581eb07d014157e1a76295faeded39f", size = 24680, upload-time = "2020-11-16T02:28:11.867Z" }
+wheels = [
+    { url = "https://files.pythonhosted.org/packages/6f/d2/f432427a58986ce8ea9f9d2ac6b35dd9657e523dcc562048c19491b4980b/pytholog-2.4.1-py3-none-any.whl", hash = "sha256:b726af28476df5935d8561ce964b7f7e1ba17e9d070b8c9b3da3fe993458893d", size = 16630, upload-time = "2020-11-16T02:28:10.243Z" },
+]
+
 [[package]]
 name = "python-dateutil"
 version = "2.9.0.post0"

drydock_cli-2.8.49/.auto_release.lock

@@ -1 +0,0 @@
-2420795