stata-code 0.4.0__tar.gz → 0.5.0__tar.gz

{stata_code-0.4.0 → stata_code-0.5.0}/.gitignore

@@ -223,3 +223,16 @@ log-files/
 *.smcl
 *.dta
 !tests/fixtures/*.dta
+
+# macOS
+.DS_Store
+**/.DS_Store
+
+# VS Code workspace settings (contain user-machine absolute paths)
+.vscode/
+
+# Claude Code scratch (worktrees, transcripts)
+.claude/
+
+# Demo / scratch notebooks (real tests live under tests/)
+demo-tests/*.ipynb

{stata_code-0.4.0 → stata_code-0.5.0}/CHANGELOG.md

@@ -4,6 +4,45 @@ All notable changes to `stata-code` are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the project adheres
 to semver-major.minor for the result schema (see `SCHEMA.md` §6).
 
+## [0.5.0] — 2026-05-08
+
+### Added
+
+- **Bundled Jupyter kernel logos.** `stata-code-kernel install --user`
+  now copies `stata_code/kernel/assets/{logo-32x32.png,logo-64x64.png,
+  logo-svg.svg}` into the kernelspec source dir before
+  `KernelSpecManager().install_kernel_spec` runs. VS Code's Jupyter
+  extension filters out kernelspecs that lack logo files, so prior
+  releases were invisible in its kernel picker; v0.5 fixes that without
+  affecting JupyterLab or classic Jupyter (which both already worked).
+- **TestPyPI publishing step in `release.yml`.** Tag `v*` now publishes
+  to TestPyPI (via OIDC trusted publishing, environment `testpypi`)
+  before publishing to PyPI proper. `continue-on-error: true` keeps
+  PyPI + GitHub Release on the happy path even when TestPyPI is
+  misconfigured. Setup mirrors the PyPI trusted publisher and is
+  documented in [CLAUDE.md](CLAUDE.md).
+
+### Changed
+
+- **`stata_run` tool description and README** clarify the boundary
+  between non-mutating execution and the optional agent "fix and
+  rerun" repair loop. The tool itself never rewrites your `.do` file
+  — but the submitted Stata code can still produce logs, graphs, and
+  output files as usual. Repair loops require explicit user opt-in;
+  failed runs are diagnostics first, not automatic rewrite permission.
+- **VSCode MCP-client handshake version aligned to 0.5.0** (was a
+  stale 0.3.2 since the v0.3.2 release).
+
+### Fixed
+
+- **`install_kernel` no longer `.resolve()`s `sys.executable`.** On
+  macOS Homebrew venvs (and other layouts that use a `python` symlink
+  outside the venv's `bin/` to a Cellar-style real interpreter),
+  resolving the symlink pointed Jupyter at an interpreter that
+  couldn't import `stata_code`. The kernelspec now keeps the
+  unresolved `sys.executable`, so the venv's `python` (with
+  `stata_code` on its `sys.path`) launches the kernel.
+
 ## [0.4.0] — 2026-05-07
 
 ### Added

{stata_code-0.4.0 → stata_code-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stata-code
-Version: 0.4.0
+Version: 0.5.0
 Summary: Agent-native Stata bridge — one core, multiple frontends (MCP, Jupyter, VSCode)
 Project-URL: Homepage, https://github.com/brycewang-stanford/stata-code
 Project-URL: Repository, https://github.com/brycewang-stanford/stata-code
@@ -59,7 +59,12 @@ Description-Content-Type: text/markdown
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**Status: v0.2 (May 2026)** — the core, MCP server, and Jupyter kernel work end-to-end against Stata 18 MP. Current test suite: 144 passing tests (88 no-Stata unit tests + 56 real-Stata integration tests). License: **MIT**.
+**Status: v0.5 (May 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. Current test suite: 218 passing tests across schema, runner, MCP, kernel, and ref-store modules. License: **MIT**.
+
+Two workflows v0.5 explicitly supports for end users:
+
+- **Run Stata code from a Jupyter notebook.** `pip install "stata-code[kernel]"` + `stata-code-kernel install --user` registers a **Stata** kernel that the Jupyter Notebook UI, JupyterLab, and the VS Code Jupyter extension all pick up by name. Cells render Stata logs, graphs, and warnings inline (the kernel logo bundled in v0.5 makes it appear in VS Code's kernel picker too). See [As a Jupyter Kernel](#as-a-jupyter-kernel).
+- **Optional agent "fix and rerun" loop.** `stata_run` returns typed `error.kind/line/context` plus `suggestions` on every failure. By default Claude Code only reports diagnostics — but if you explicitly say "fix this and rerun until it passes", the agent uses the same fields to edit your `.do` file and re-call `stata_run` until the run is green. The repair loop is **opt-in**: failed runs are diagnostics first, not automatic rewrite permission. See [Error Recovery in Agent Workflows](#error-recovery-in-agent-workflows).
 
 ---
 
@@ -156,6 +161,15 @@ claude mcp add stata-code --scope project -- stata-code-mcp
 
 Then launch `claude` and type `/mcp` to confirm `stata-code` shows up with its 8 tools (`stata_run`, `stata_info`, `get_log`, `get_graph`, `get_matrix`, `list_sessions`, `cancel_session`, `reset_session`).
 
+#### Error Recovery in Agent Workflows
+
+`stata_run` does not rewrite the source `.do` file or change code on its own. It executes the submitted Stata code, so that code may still create logs, graphs, tables, or other outputs as usual. When Stata fails, `stata_run` returns typed diagnostics (`error.kind`, `error.message`, `error.line`, `error.context`) plus best-effort `suggestions`. That supports two distinct Claude Code workflows:
+
+- For "run this do-file" or "verify this code", Claude can report the failure and suggested next steps without changing source files.
+- For "fix this and rerun until it passes", Claude can use the same structured error fields to edit the `.do` file, call `stata_run` again, and iterate.
+
+If you want the repair loop, say so explicitly. Otherwise, treat failed runs as diagnostics first, not as automatic permission to rewrite code.
+
 #### `uvx` (no global pip install)
 
 If you prefer not to `pip install stata-code` globally, run it ephemerally through [`uv`](https://github.com/astral-sh/uv):
@@ -314,7 +328,7 @@ stata_code/
 
 ## Roadmap
 
-### Done (v0.2 — May 2026)
+### Done (through v0.5 — May 2026)
 
 - v1.0 result schema ([SCHEMA.md](SCHEMA.md))
 - `pystata`-based runner with native-typed `r()`, `e()`, and matrices
@@ -347,7 +361,7 @@ See [SCHEMA.md §7](SCHEMA.md) for explicitly out-of-scope items.
 
 ```bash
 pip install -e ".[dev,mcp,kernel]"
-pytest                              # full suite (144 tests)
+pytest                              # full suite (218 tests)
 pytest -m "not stata_required"      # CI subset; no Stata needed
 pytest -m "stata_required" -v       # Stata-only integration tests
 ```
@@ -402,7 +416,12 @@ The Stata tooling landscape that this project builds on and learns from is surve
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**当前状态：v0.2（2026 年 5 月）** —— core、MCP server 和 Jupyter kernel 已经可以在 Stata 18 MP 上端到端运行。当前测试：144 passing（88 个不需要 Stata 的单元测试 + 56 个真实 Stata 集成测试）。许可证：**MIT**。
+**当前状态：v0.5（2026 年 5 月）** —— core、MCP server、Jupyter kernel、VS Code 扩展都已经在 Stata 18 MP 上端到端跑通。测试套件：218 个 passing tests，覆盖 schema、runner、MCP、kernel 和 ref-store。许可证：**MIT**。
+
+v0.5 明确支持的两种用户工作流：
+
+- **在 Jupyter notebook 里跑 Stata 代码。** `pip install "stata-code[kernel]"` + `stata-code-kernel install --user` 会注册一个名为 **Stata** 的 kernel，Jupyter Notebook、JupyterLab、以及 VS Code 的 Jupyter 扩展都能在 kernel 选择器里看到它。Cell 里直接写 Stata 命令，日志、图形和警告会内联渲染（v0.5 把 kernel logo 一起打包进 PyPI wheel，VS Code 的 Jupyter kernel picker 也能正常显示）。详见下文 [作为 Jupyter kernel](#作为-jupyter-kernel)。
+- **可选的 agent「修复并重跑」循环。** `stata_run` 在每次失败时都会返回结构化的 `error.kind/line/context` 和 `suggestions`。默认情况下 Claude Code 只把它当作诊断信息上报；但如果你明确说「帮我修到跑通」「修复并反复运行直到成功」，agent 就会用同一组字段去改 `.do` 文件、再调 `stata_run`，直到代码通过。这个修复循环是 **opt-in** 的：默认失败 = 诊断，不是自动改写授权。详见下文 [Agent 工作流里的报错恢复](#agent-工作流里的报错恢复)。
 
 ---
 
@@ -498,6 +517,15 @@ claude mcp add stata-code --scope project -- stata-code-mcp
 
 接着运行 `claude`，输入 `/mcp` 确认 `stata-code` 出现并带有 8 个工具（`stata_run`, `stata_info`, `get_log`, `get_graph`, `get_matrix`, `list_sessions`, `cancel_session`, `reset_session`）。
 
+#### Agent 工作流里的报错恢复
+
+`stata_run` 不会自行改写源 `.do` 文件或替你改代码。它执行提交的 Stata 代码，所以代码本身仍可能照常生成日志、图形、表格或其他输出。Stata 报错时，`stata_run` 返回结构化诊断（`error.kind`, `error.message`, `error.line`, `error.context`）和尽力生成的 `suggestions`。这支持两种不同的 Claude Code 工作流：
+
+- 如果你说的是「运行这个 do-file」或「验证这段代码」，Claude 可以只报告失败原因和建议的下一步，不修改源文件。
+- 如果你明确说「帮我修到跑通」或「修复并反复运行直到成功」，Claude 可以基于同一组结构化错误字段修改 `.do` 文件，再调用 `stata_run` 继续迭代。
+
+如果需要自动修复循环，请明确说出来。否则，失败的运行应先被视为诊断结果，而不是自动改写代码的授权。
+
 #### 用 `uvx`（不必全局 pip install）
 
 如果不想全局 `pip install stata-code`，可以用 [`uv`](https://github.com/astral-sh/uv) 临时运行：

{stata_code-0.4.0 → stata_code-0.5.0}/README.md

@@ -21,7 +21,12 @@
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**Status: v0.2 (May 2026)** — the core, MCP server, and Jupyter kernel work end-to-end against Stata 18 MP. Current test suite: 144 passing tests (88 no-Stata unit tests + 56 real-Stata integration tests). License: **MIT**.
+**Status: v0.5 (May 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. Current test suite: 218 passing tests across schema, runner, MCP, kernel, and ref-store modules. License: **MIT**.
+
+Two workflows v0.5 explicitly supports for end users:
+
+- **Run Stata code from a Jupyter notebook.** `pip install "stata-code[kernel]"` + `stata-code-kernel install --user` registers a **Stata** kernel that the Jupyter Notebook UI, JupyterLab, and the VS Code Jupyter extension all pick up by name. Cells render Stata logs, graphs, and warnings inline (the kernel logo bundled in v0.5 makes it appear in VS Code's kernel picker too). See [As a Jupyter Kernel](#as-a-jupyter-kernel).
+- **Optional agent "fix and rerun" loop.** `stata_run` returns typed `error.kind/line/context` plus `suggestions` on every failure. By default Claude Code only reports diagnostics — but if you explicitly say "fix this and rerun until it passes", the agent uses the same fields to edit your `.do` file and re-call `stata_run` until the run is green. The repair loop is **opt-in**: failed runs are diagnostics first, not automatic rewrite permission. See [Error Recovery in Agent Workflows](#error-recovery-in-agent-workflows).
 
 ---
 
@@ -118,6 +123,15 @@ claude mcp add stata-code --scope project -- stata-code-mcp
 
 Then launch `claude` and type `/mcp` to confirm `stata-code` shows up with its 8 tools (`stata_run`, `stata_info`, `get_log`, `get_graph`, `get_matrix`, `list_sessions`, `cancel_session`, `reset_session`).
 
+#### Error Recovery in Agent Workflows
+
+`stata_run` does not rewrite the source `.do` file or change code on its own. It executes the submitted Stata code, so that code may still create logs, graphs, tables, or other outputs as usual. When Stata fails, `stata_run` returns typed diagnostics (`error.kind`, `error.message`, `error.line`, `error.context`) plus best-effort `suggestions`. That supports two distinct Claude Code workflows:
+
+- For "run this do-file" or "verify this code", Claude can report the failure and suggested next steps without changing source files.
+- For "fix this and rerun until it passes", Claude can use the same structured error fields to edit the `.do` file, call `stata_run` again, and iterate.
+
+If you want the repair loop, say so explicitly. Otherwise, treat failed runs as diagnostics first, not as automatic permission to rewrite code.
+
 #### `uvx` (no global pip install)
 
 If you prefer not to `pip install stata-code` globally, run it ephemerally through [`uv`](https://github.com/astral-sh/uv):
@@ -276,7 +290,7 @@ stata_code/
 
 ## Roadmap
 
-### Done (v0.2 — May 2026)
+### Done (through v0.5 — May 2026)
 
 - v1.0 result schema ([SCHEMA.md](SCHEMA.md))
 - `pystata`-based runner with native-typed `r()`, `e()`, and matrices
@@ -309,7 +323,7 @@ See [SCHEMA.md §7](SCHEMA.md) for explicitly out-of-scope items.
 
 ```bash
 pip install -e ".[dev,mcp,kernel]"
-pytest                              # full suite (144 tests)
+pytest                              # full suite (218 tests)
 pytest -m "not stata_required"      # CI subset; no Stata needed
 pytest -m "stata_required" -v       # Stata-only integration tests
 ```
@@ -364,7 +378,12 @@ The Stata tooling landscape that this project builds on and learns from is surve
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**当前状态：v0.2（2026 年 5 月）** —— core、MCP server 和 Jupyter kernel 已经可以在 Stata 18 MP 上端到端运行。当前测试：144 passing（88 个不需要 Stata 的单元测试 + 56 个真实 Stata 集成测试）。许可证：**MIT**。
+**当前状态：v0.5（2026 年 5 月）** —— core、MCP server、Jupyter kernel、VS Code 扩展都已经在 Stata 18 MP 上端到端跑通。测试套件：218 个 passing tests，覆盖 schema、runner、MCP、kernel 和 ref-store。许可证：**MIT**。
+
+v0.5 明确支持的两种用户工作流：
+
+- **在 Jupyter notebook 里跑 Stata 代码。** `pip install "stata-code[kernel]"` + `stata-code-kernel install --user` 会注册一个名为 **Stata** 的 kernel，Jupyter Notebook、JupyterLab、以及 VS Code 的 Jupyter 扩展都能在 kernel 选择器里看到它。Cell 里直接写 Stata 命令，日志、图形和警告会内联渲染（v0.5 把 kernel logo 一起打包进 PyPI wheel，VS Code 的 Jupyter kernel picker 也能正常显示）。详见下文 [作为 Jupyter kernel](#作为-jupyter-kernel)。
+- **可选的 agent「修复并重跑」循环。** `stata_run` 在每次失败时都会返回结构化的 `error.kind/line/context` 和 `suggestions`。默认情况下 Claude Code 只把它当作诊断信息上报；但如果你明确说「帮我修到跑通」「修复并反复运行直到成功」，agent 就会用同一组字段去改 `.do` 文件、再调 `stata_run`，直到代码通过。这个修复循环是 **opt-in** 的：默认失败 = 诊断，不是自动改写授权。详见下文 [Agent 工作流里的报错恢复](#agent-工作流里的报错恢复)。
 
 ---
 
@@ -460,6 +479,15 @@ claude mcp add stata-code --scope project -- stata-code-mcp
 
 接着运行 `claude`，输入 `/mcp` 确认 `stata-code` 出现并带有 8 个工具（`stata_run`, `stata_info`, `get_log`, `get_graph`, `get_matrix`, `list_sessions`, `cancel_session`, `reset_session`）。
 
+#### Agent 工作流里的报错恢复
+
+`stata_run` 不会自行改写源 `.do` 文件或替你改代码。它执行提交的 Stata 代码，所以代码本身仍可能照常生成日志、图形、表格或其他输出。Stata 报错时，`stata_run` 返回结构化诊断（`error.kind`, `error.message`, `error.line`, `error.context`）和尽力生成的 `suggestions`。这支持两种不同的 Claude Code 工作流：
+
+- 如果你说的是「运行这个 do-file」或「验证这段代码」，Claude 可以只报告失败原因和建议的下一步，不修改源文件。
+- 如果你明确说「帮我修到跑通」或「修复并反复运行直到成功」，Claude 可以基于同一组结构化错误字段修改 `.do` 文件，再调用 `stata_run` 继续迭代。
+
+如果需要自动修复循环，请明确说出来。否则，失败的运行应先被视为诊断结果，而不是自动改写代码的授权。
+
 #### 用 `uvx`（不必全局 pip install）
 
 如果不想全局 `pip install stata-code`，可以用 [`uv`](https://github.com/astral-sh/uv) 临时运行：

{stata_code-0.4.0 → stata_code-0.5.0}/SCHEMA.md

@@ -389,7 +389,7 @@ Populated iff `ok: false`. The schema's most important contribution to agent UX:
 }
 ```
 
-Suggestions are best-effort; agents should treat them as hints, not directives. The `kind` enum below documents what suggestions are typically populated.
+Suggestions are best-effort; agents should treat them as hints, not directives. A suggestion is not consent to mutate source files or silently retry changed code; consumers should apply fixes automatically only in workflows where the user requested repair or approved iteration. The `kind` enum below documents what suggestions are typically populated.
 
 **`kind` enum (v1.0):**
 

{stata_code-0.4.0 → stata_code-0.5.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "stata-code"
-version = "0.4.0"
+version = "0.5.0"
 description = "Agent-native Stata bridge — one core, multiple frontends (MCP, Jupyter, VSCode)"
 readme = "README.md"
 license = "MIT"

{stata_code-0.4.0 → stata_code-0.5.0}/stata_code/__init__.py

@@ -58,7 +58,7 @@ from stata_code.core.schema import (
 # Convenience alias: `run(...)` == `execute(...)`.
 run = execute
 
-__version__ = "0.4.0"
+__version__ = "0.5.0"
 
 __all__ = [
     # Primary entry points

stata_code-0.5.0/stata_code/kernel/assets/logo-svg.svg

@@ -0,0 +1,41 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" width="64" height="64">
+  <defs>
+    <linearGradient id="bg" x1="0" y1="0" x2="0" y2="1">
+      <stop offset="0" stop-color="#8B1E2D"/>
+      <stop offset="1" stop-color="#5A1220"/>
+    </linearGradient>
+    <linearGradient id="bar" x1="0" y1="0" x2="1" y2="0">
+      <stop offset="0" stop-color="#F5E9D2" stop-opacity="0.55"/>
+      <stop offset="0.5" stop-color="#F5E9D2"/>
+      <stop offset="1" stop-color="#F5E9D2" stop-opacity="0.55"/>
+    </linearGradient>
+  </defs>
+
+  <rect width="64" height="64" rx="12" fill="url(#bg)"/>
+
+  <g stroke="url(#bar)" stroke-width="3" stroke-linecap="round" fill="none">
+    <line x1="14" y1="32" x2="50" y2="32"/>
+    <line x1="14" y1="24" x2="14" y2="40" stroke="#F5E9D2"/>
+    <line x1="50" y1="24" x2="50" y2="40" stroke="#F5E9D2"/>
+  </g>
+
+  <g>
+    <circle cx="32" cy="19" r="1.2" fill="#F5E9D2"/>
+    <line x1="32" y1="20" x2="32" y2="24" stroke="#F5E9D2" stroke-width="1.2" stroke-linecap="round"/>
+    <rect x="24" y="24" width="16" height="14" rx="3" fill="#F5E9D2"/>
+    <circle cx="28.5" cy="30" r="1.5" fill="#5A1220"/>
+    <circle cx="35.5" cy="30" r="1.5" fill="#5A1220"/>
+    <circle cx="28.5" cy="30" r="0.45" fill="#F5E9D2"/>
+    <circle cx="35.5" cy="30" r="0.45" fill="#F5E9D2"/>
+    <line x1="29.5" y1="34.5" x2="34.5" y2="34.5" stroke="#5A1220" stroke-width="1.3" stroke-linecap="round"/>
+  </g>
+
+  <g fill="#F5E9D2">
+    <circle cx="22" cy="14" r="1.3" opacity="0.55"/>
+    <circle cx="44" cy="50" r="1.3" opacity="0.55"/>
+    <circle cx="42" cy="13" r="0.9" opacity="0.4"/>
+    <circle cx="22" cy="51" r="0.9" opacity="0.4"/>
+    <circle cx="52" cy="11" r="0.7" opacity="0.3"/>
+    <circle cx="12" cy="53" r="0.7" opacity="0.3"/>
+  </g>
+</svg>

{stata_code-0.4.0 → stata_code-0.5.0}/stata_code/kernel/kernel.py

@@ -13,12 +13,18 @@ Install via `python -m stata_code.kernel install --user`.
 from __future__ import annotations
 
 import json
+import shutil
 import sys
 import traceback
 from pathlib import Path
 from tempfile import TemporaryDirectory
 from typing import Any
 
+# Bundled kernelspec resources (logo files) shipped alongside this module.
+# Copied into the kernelspec dir at install time so VS Code's Jupyter extension
+# lists the kernel in its picker — it filters out kernelspecs without logos.
+ASSETS_DIR = Path(__file__).parent / "assets"
+
 try:
     from ipykernel.kernelbase import Kernel
 
@@ -262,7 +268,11 @@ def install_kernel(user: bool = True, system: bool = False) -> None:
     """
     from jupyter_client.kernelspec import KernelSpecManager
 
-    py_exec = Path(sys.executable).resolve()
+    # Do not .resolve() — on macOS Homebrew venvs, .venv/bin/python is a symlink
+    # to the underlying system Python; resolving it bypasses the venv and the
+    # kernel fails to find stata_code. sys.executable already points to the
+    # interpreter currently running this install command, which is what we want.
+    py_exec = Path(sys.executable)
     kernel_json = {
         "argv": [
             str(py_exec),
@@ -280,6 +290,10 @@ def install_kernel(user: bool = True, system: bool = False) -> None:
     with TemporaryDirectory(prefix="stata_code_kernel_") as td:
         src_dir = Path(td)
         (src_dir / "kernel.json").write_text(json.dumps(kernel_json, indent=2))
+        if ASSETS_DIR.is_dir():
+            for asset in ASSETS_DIR.iterdir():
+                if asset.is_file():
+                    shutil.copy2(asset, src_dir / asset.name)
         dest = KernelSpecManager().install_kernel_spec(
             str(src_dir),
             kernel_name="stata",

{stata_code-0.4.0 → stata_code-0.5.0}/stata_code/mcp/server.py

@@ -43,7 +43,7 @@ from stata_code.core.runner import (
     is_cancel_pending,
 )
 
-__version__ = "0.4.0"
+__version__ = "0.5.0"
 
 APP: Any = Server("stata-code") if _MCP_AVAILABLE else None
 
@@ -63,7 +63,11 @@ def _tool_definitions() -> list[Tool]:
                 "error (typed), log (head+tail+ref by default), results.r/e "
                 "(scalars/macros/matrices, native types), dataset metadata, "
                 "graphs, warnings, and capabilities. Use the structured "
-                "fields rather than parsing the log."
+                "fields rather than parsing the log. On ok=false, surface "
+                "error.kind/message/line/suggestions. Use suggestions for "
+                "iterative debug/fix loops only when the user asked for that "
+                "or approved changes; for run/validate-only requests, report "
+                "diagnostics without rewriting source code."
             ),
             inputSchema={
                 "type": "object",

{stata_code-0.4.0 → stata_code-0.5.0}/tests/test_kernel.py

@@ -221,7 +221,7 @@ class TestInstallKernel:
                 "replace": True,
                 "spec": {
                     "argv": [
-                        str((tmp_path / "python").resolve()),
+                        str(tmp_path / "python"),
                         "-m",
                         "stata_code.kernel",
                         "-f",
@@ -234,6 +234,37 @@ class TestInstallKernel:
             }
         ]
 
+    def test_install_kernel_copies_bundled_logos(self, tmp_path):
+        """install_kernel should copy bundled logo assets into the kernelspec."""
+        from stata_code.kernel.kernel import ASSETS_DIR, install_kernel
+
+        captured_files: dict[str, bytes] = {}
+
+        class DummyKernelSpecManager:
+            def install_kernel_spec(
+                self,
+                source_dir: str,
+                *,
+                kernel_name: str,
+                user: bool,
+                replace: bool,
+            ) -> str:
+                for child in Path(source_dir).iterdir():
+                    if child.is_file():
+                        captured_files[child.name] = child.read_bytes()
+                return str(tmp_path / "kernels" / kernel_name)
+
+        with patch(
+            "jupyter_client.kernelspec.KernelSpecManager",
+            return_value=DummyKernelSpecManager(),
+        ):
+            install_kernel(user=True)
+
+        for asset in ASSETS_DIR.iterdir():
+            if asset.is_file():
+                assert asset.name in captured_files, f"missing {asset.name}"
+                assert captured_files[asset.name] == asset.read_bytes()
+
     def test_install_kernel_system_not_user(self, tmp_path):
         """system=True should pass user=False to Jupyter's installer."""
         from stata_code.kernel.kernel import install_kernel

{stata_code-0.4.0 → stata_code-0.5.0}/tests/test_mcp.py

@@ -44,6 +44,10 @@ class TestToolRegistry:
         assert schema["type"] == "object"
         assert "code" in schema["properties"]
         assert "code" in schema["required"]
+        assert "ok=false" in run.description
+        assert "iterative debug/fix loops" in run.description
+        assert "run/validate-only requests" in run.description
+        assert "without rewriting source code" in run.description
         # Token-economy options are exposed
         assert "include_graphs" in schema["properties"]
         assert "include_full_log" in schema["properties"]