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

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

@@ -218,6 +218,7 @@ __marimo__/
 .streamlit/secrets.toml
 
 # Stata-specific
+log-files/
 *.gph
 *.smcl
 *.dta

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

@@ -4,7 +4,67 @@ 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).
 
-## [Unreleased]
+## [0.4.0] — 2026-05-07
+
+### Added
+
+- **Persistent per-run log bundles.** When a `.do` file path is supplied as
+  `origin_path`, the runner writes an immutable `log-files/<run>/` directory
+  next to the source file containing:
+  - `<run>.log` and `<run>.smcl` — Stata's textual and SMCL logs
+  - `manifest.json` — run metadata (elapsed_ms, rc, session, Stata edition)
+  - `submitted.do` — a snapshot of the code that was executed
+  - `graphs/` — captured graph files materialized from graph refs
+  - `outputs/` — newly created or modified table/export files copied from
+    the run's working directory
+
+  The directory name encodes UTC timestamp, session, and request IDs so
+  parallel runs and reruns are never ambiguous.
+
+- **Working-directory defaults from `origin_path`.** Before running,
+  Stata `cd`s to the `.do` file's parent so relative `graph export`,
+  `putexcel`, `esttab using`, `collect export`, etc. output next to the
+  source. Toggle with `use_origin_workdir` / `useDoFileDirectory` setting.
+  Explicit `working_dir` overrides this.
+
+- **Schema extensions.** `LogInfo.files` (`LogFileInfo`) carries the
+  bundle paths and derived `graphs_dir`/`outputs_dir`; `GraphInfo.file_path`
+  records where a graph was materialized; two new capabilities
+  `log_files` and `run_artifacts` signal support.
+
+- **MCP tool options.** `stata_run` gains `persist_log_files`,
+  `persist_generated_files`, `origin_path`, `origin_kind`,
+  `origin_label`, `use_origin_workdir`, `working_dir`.
+
+- **VS Code settings.** Three new configuration options:
+  `stataCode.persistLogFiles` (default `true`),
+  `stataCode.persistGeneratedFiles` (default `true`),
+  `stataCode.useDoFileDirectory` (default `true`).
+
+- **VS Code tree views.** The Last Result tree now shows "saved" and
+  "N outputs" badges on the log node when artifacts are present; the
+  output log header prints `working_dir:`, `log_file:`, `smcl_file:`,
+  `graphs_dir:`, `outputs_dir:` for each run.
+
+### Changed
+
+- **VSCode MCP startup.** The extension now expands common macOS Python
+  script directories before spawning `stata-code-mcp`, tries workspace
+  `.venv` and `python -m stata_code.mcp` fallbacks for the default command,
+  and writes child-process stderr to the `stata-code` output channel so
+  missing PATH / missing dependency failures are actionable.
+- **VSCode toolbar ordering.** Run-all and run-selection now share the same
+  ordinary `editor/title` toolbar sequence, with ordering moved later in the
+  `navigation` group to reduce interleaving from other extensions.
+
+## [0.3.2] — 2026-05-08
+
+### Changed
+
+- **VSCode toolbar ordering.** Editor title-bar actions now live in one
+  contiguous `navigation` group so `stata-code` buttons stay together. The
+  order prioritizes run commands first, then data/output views, session
+  controls, cancellation/reset, and working-directory actions.
 
 ## [0.3.1] — 2026-05-07
 

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stata-code
-Version: 0.3.1
+Version: 0.4.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
@@ -135,7 +135,7 @@ else:
 
 ### As an MCP Server
 
-After `pip install stata-code`, the `stata-code-mcp` binary is on your `PATH`. You can wire it into Claude Code, Cursor, Claude Desktop, or any other MCP-compatible client.
+After `pip install "stata-code[mcp]"`, the `stata-code-mcp` binary is on your `PATH`. You can wire it into Claude Code, Cursor, Claude Desktop, or any other MCP-compatible client.
 
 #### Claude Code via `claude mcp add` (recommended)
 
@@ -201,17 +201,30 @@ The MCP server registers 8 tools:
 
 ### As a Jupyter Kernel
 
+`stata-code` ships a Jupyter kernel as part of the Python package — there is no separate "Jupyter plugin" in the JupyterLab extension marketplace. Installation is two steps: `pip install` the package with the `kernel` extra, then register the kernelspec with Jupyter.
+
+**Prerequisites**: Stata 17+ installed locally with a valid license (the kernel calls Stata via `pystata`), and Python 3.10+ with `jupyter`/`jupyterlab` already on the same environment.
+
 ```bash
+# 1. Install stata-code with the kernel extra (pulls in ipykernel)
+pip install "stata-code[kernel]"
+
+# 2. Register the kernelspec into Jupyter's user data dir
 stata-code-kernel install --user
+# Or, equivalently:
+# python -m stata_code.kernel install --user
 ```
 
-Or install it as a module:
+Verify the kernel is registered:
 
 ```bash
-python -m stata_code.kernel install --user
+jupyter kernelspec list
+# should include an entry named `stata`
 ```
 
-Then open a notebook and select the **Stata** kernel. Stata commands run in cells; logs, graphs, and warnings render inline.
+Then open Jupyter Notebook / JupyterLab (or a `.ipynb` in VS Code), pick **Stata** in the kernel selector, and run Stata commands in cells. Logs, graphs, and warnings render inline.
+
+> JupyterLab's Extension Manager only installs front-end JS extensions, so it cannot install a kernel — `pip install` plus the `install --user` step above is the only supported path.
 
 ### As a VS Code Extension
 
@@ -224,7 +237,7 @@ code --install-extension brycewang-stanford.stata-code-vscode
 
 Or open the **Extensions** sidebar in VS Code and search `stata-code`.
 
-The extension still requires `stata-code` itself to be importable on your system Python (`pip install stata-code`), so that `stata-code-mcp` resolves on `PATH`. Stata 17+ and a valid Stata license are required as for any other frontend.
+The extension still requires the MCP extra on your system Python (`pip install "stata-code[mcp]"`), so that `stata-code-mcp` resolves on `PATH` and can import the MCP SDK. Stata 17+ and a valid Stata license are required as for any other frontend.
 
 ---
 
@@ -464,7 +477,7 @@ else:
 
 ### 作为 MCP server
 
-`pip install stata-code` 之后，`stata-code-mcp` 会出现在你的 `PATH` 中。可以接到 Claude Code、Cursor、Claude Desktop 等任何兼容 MCP 的客户端里。
+`pip install "stata-code[mcp]"` 之后，`stata-code-mcp` 会出现在你的 `PATH` 中。可以接到 Claude Code、Cursor、Claude Desktop 等任何兼容 MCP 的客户端里。
 
 #### 用 `claude mcp add` 接入 Claude Code（推荐）
 
@@ -530,17 +543,30 @@ MCP server 注册了 8 个工具：
 
 ### 作为 Jupyter kernel
 
+`stata-code` 的 Jupyter 支持是以 **kernel** 形式打包在 Python 包里的 —— JupyterLab 插件市场里**没有**独立的 "stata-code 插件"。安装分两步：先 `pip install` 安装带 `kernel` extra 的包，再把 kernelspec 注册到 Jupyter。
+
+**前置条件**：本机已经安装 Stata 17+ 且持有合法许可证（kernel 通过 `pystata` 调用本地 Stata），同一个 Python 环境里已经装好 `jupyter`/`jupyterlab`，Python 版本 ≥ 3.10。
+
 ```bash
+# 1. 安装带 kernel extra 的 stata-code（会同时装上 ipykernel）
+pip install "stata-code[kernel]"
+
+# 2. 把 kernelspec 注册到当前用户的 Jupyter data dir
 stata-code-kernel install --user
+# 等价命令：
+# python -m stata_code.kernel install --user
 ```
 
-也可以直接以 module 方式安装：
+检查 kernel 是否注册成功：
 
 ```bash
-python -m stata_code.kernel install --user
+jupyter kernelspec list
+# 输出里应该能看到名为 `stata` 的条目
 ```
 
-然后打开 notebook，选择 **Stata** kernel。Stata 命令会在 cell 中运行，日志、图形和 warnings 会以内联方式显示。
+然后打开 Jupyter Notebook / JupyterLab（或 VS Code 中的 `.ipynb`），在 kernel 选择器里挑 **Stata**，cell 里直接写 Stata 命令即可，日志、graphs 和 warnings 会以内联方式显示。
+
+> JupyterLab 的 Extension Manager 只能安装前端 JS 扩展，**装不了 kernel**。所以上面的 `pip install` + `install --user` 是唯一支持的安装路径。
 
 ### 作为 VS Code 扩展
 
@@ -553,7 +579,7 @@ code --install-extension brycewang-stanford.stata-code-vscode
 
 或者打开 VS Code 的 **Extensions** 侧栏，搜索 `stata-code`。
 
-扩展仍然依赖系统 Python 上能导入 `stata-code`（`pip install stata-code`），从而保证 `stata-code-mcp` 在 `PATH` 上可用。和其它前端一样，需要 Stata 17+ 和有效的 Stata 许可证。
+扩展仍然依赖系统 Python 上安装了 MCP extra（`pip install "stata-code[mcp]"`），从而保证 `stata-code-mcp` 在 `PATH` 上可用，并且能导入 MCP SDK。和其它前端一样，需要 Stata 17+ 和有效的 Stata 许可证。
 
 ---
 

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

@@ -97,7 +97,7 @@ else:
 
 ### As an MCP Server
 
-After `pip install stata-code`, the `stata-code-mcp` binary is on your `PATH`. You can wire it into Claude Code, Cursor, Claude Desktop, or any other MCP-compatible client.
+After `pip install "stata-code[mcp]"`, the `stata-code-mcp` binary is on your `PATH`. You can wire it into Claude Code, Cursor, Claude Desktop, or any other MCP-compatible client.
 
 #### Claude Code via `claude mcp add` (recommended)
 
@@ -163,17 +163,30 @@ The MCP server registers 8 tools:
 
 ### As a Jupyter Kernel
 
+`stata-code` ships a Jupyter kernel as part of the Python package — there is no separate "Jupyter plugin" in the JupyterLab extension marketplace. Installation is two steps: `pip install` the package with the `kernel` extra, then register the kernelspec with Jupyter.
+
+**Prerequisites**: Stata 17+ installed locally with a valid license (the kernel calls Stata via `pystata`), and Python 3.10+ with `jupyter`/`jupyterlab` already on the same environment.
+
 ```bash
+# 1. Install stata-code with the kernel extra (pulls in ipykernel)
+pip install "stata-code[kernel]"
+
+# 2. Register the kernelspec into Jupyter's user data dir
 stata-code-kernel install --user
+# Or, equivalently:
+# python -m stata_code.kernel install --user
 ```
 
-Or install it as a module:
+Verify the kernel is registered:
 
 ```bash
-python -m stata_code.kernel install --user
+jupyter kernelspec list
+# should include an entry named `stata`
 ```
 
-Then open a notebook and select the **Stata** kernel. Stata commands run in cells; logs, graphs, and warnings render inline.
+Then open Jupyter Notebook / JupyterLab (or a `.ipynb` in VS Code), pick **Stata** in the kernel selector, and run Stata commands in cells. Logs, graphs, and warnings render inline.
+
+> JupyterLab's Extension Manager only installs front-end JS extensions, so it cannot install a kernel — `pip install` plus the `install --user` step above is the only supported path.
 
 ### As a VS Code Extension
 
@@ -186,7 +199,7 @@ code --install-extension brycewang-stanford.stata-code-vscode
 
 Or open the **Extensions** sidebar in VS Code and search `stata-code`.
 
-The extension still requires `stata-code` itself to be importable on your system Python (`pip install stata-code`), so that `stata-code-mcp` resolves on `PATH`. Stata 17+ and a valid Stata license are required as for any other frontend.
+The extension still requires the MCP extra on your system Python (`pip install "stata-code[mcp]"`), so that `stata-code-mcp` resolves on `PATH` and can import the MCP SDK. Stata 17+ and a valid Stata license are required as for any other frontend.
 
 ---
 
@@ -426,7 +439,7 @@ else:
 
 ### 作为 MCP server
 
-`pip install stata-code` 之后，`stata-code-mcp` 会出现在你的 `PATH` 中。可以接到 Claude Code、Cursor、Claude Desktop 等任何兼容 MCP 的客户端里。
+`pip install "stata-code[mcp]"` 之后，`stata-code-mcp` 会出现在你的 `PATH` 中。可以接到 Claude Code、Cursor、Claude Desktop 等任何兼容 MCP 的客户端里。
 
 #### 用 `claude mcp add` 接入 Claude Code（推荐）
 
@@ -492,17 +505,30 @@ MCP server 注册了 8 个工具：
 
 ### 作为 Jupyter kernel
 
+`stata-code` 的 Jupyter 支持是以 **kernel** 形式打包在 Python 包里的 —— JupyterLab 插件市场里**没有**独立的 "stata-code 插件"。安装分两步：先 `pip install` 安装带 `kernel` extra 的包，再把 kernelspec 注册到 Jupyter。
+
+**前置条件**：本机已经安装 Stata 17+ 且持有合法许可证（kernel 通过 `pystata` 调用本地 Stata），同一个 Python 环境里已经装好 `jupyter`/`jupyterlab`，Python 版本 ≥ 3.10。
+
 ```bash
+# 1. 安装带 kernel extra 的 stata-code（会同时装上 ipykernel）
+pip install "stata-code[kernel]"
+
+# 2. 把 kernelspec 注册到当前用户的 Jupyter data dir
 stata-code-kernel install --user
+# 等价命令：
+# python -m stata_code.kernel install --user
 ```
 
-也可以直接以 module 方式安装：
+检查 kernel 是否注册成功：
 
 ```bash
-python -m stata_code.kernel install --user
+jupyter kernelspec list
+# 输出里应该能看到名为 `stata` 的条目
 ```
 
-然后打开 notebook，选择 **Stata** kernel。Stata 命令会在 cell 中运行，日志、图形和 warnings 会以内联方式显示。
+然后打开 Jupyter Notebook / JupyterLab（或 VS Code 中的 `.ipynb`），在 kernel 选择器里挑 **Stata**，cell 里直接写 Stata 命令即可，日志、graphs 和 warnings 会以内联方式显示。
+
+> JupyterLab 的 Extension Manager 只能安装前端 JS 扩展，**装不了 kernel**。所以上面的 `pip install` + `install --user` 是唯一支持的安装路径。
 
 ### 作为 VS Code 扩展
 
@@ -515,7 +541,7 @@ code --install-extension brycewang-stanford.stata-code-vscode
 
 或者打开 VS Code 的 **Extensions** 侧栏，搜索 `stata-code`。
 
-扩展仍然依赖系统 Python 上能导入 `stata-code`（`pip install stata-code`），从而保证 `stata-code-mcp` 在 `PATH` 上可用。和其它前端一样，需要 Stata 17+ 和有效的 Stata 许可证。
+扩展仍然依赖系统 Python 上安装了 MCP extra（`pip install "stata-code[mcp]"`），从而保证 `stata-code-mcp` 在 `PATH` 上可用，并且能导入 MCP SDK。和其它前端一样，需要 Stata 17+ 和有效的 Stata 许可证。
 
 ---
 

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

@@ -228,6 +228,7 @@ The single biggest token-economy decision in the schema. Default response carrie
 | `complete` | `bool` | Reserved for v2 streaming. Always `true` in v1. v2 may emit interim results with `complete: false`. |
 | `error_window` | `string \| null` | When `error` is non-null, the ~10 log lines immediately surrounding the failing emission (regardless of `head`/`tail` window). Cheap for the producer to compute; saves agents from bumping `log_lines` or fetching the full log just to see "what did Stata say right when it broke." `null` on success or when not computable. |
 | `ref` | `string \| null` | Opaque reference for `get_log`. Required when `truncated: true`; may be set when `truncated: false` for caller convenience; `null` is allowed when full log is in `head`. |
+| `files` | `object \| null` | Persistent `.log` / `.smcl` artifacts written for file-backed runs when requested. `null` when no files were written. See "Persistent log files" below. |
 
 **ANSI handling.** All log views (`head`, `tail`, `error_window`, the payload returned by `get_log(ref)`) are ANSI-escape-stripped, consistently.
 
@@ -237,6 +238,37 @@ The single biggest token-economy decision in the schema. Default response carrie
 
 **Defaults.** `head=20`, `tail=20`. Configurable per call via `log_lines_head` / `log_lines_tail` (see §4). If `lines_total ≤ head+tail`, the producer MUST set `truncated: false`, place the full log in `head`, set `tail: ""`, and set `ref: null`.
 
+**Persistent log files.** When a frontend passes a source `.do` path and requests `persist_log_files`, producers write immutable run artifacts under:
+
+```text
+<do-file-dir>/log-files/<do-stem>__<UTC timestamp>__<session_id>__<request_id>/
+```
+
+`log.files` then has:
+
+```json
+{
+  "directory": "/abs/path/log-files/test1__20260508T012233123Z__main__abc123",
+  "log_path": "/abs/path/.../test1__20260508T012233123Z__main__abc123.log",
+  "smcl_path": "/abs/path/.../test1__20260508T012233123Z__main__abc123.smcl",
+  "manifest_path": "/abs/path/.../manifest.json",
+  "code_path": "/abs/path/.../submitted.do",
+  "working_dir": "/abs/path",
+  "graphs_dir": "/abs/path/.../graphs",
+  "outputs_dir": "/abs/path/.../outputs",
+  "graph_paths": ["/abs/path/.../graphs/01-Graph.png"],
+  "output_paths": ["/abs/path/.../outputs/table.xlsx"],
+  "policy": "per_run_directory",
+  "append": false
+}
+```
+
+The stable folder name is `log-files`; timestamps belong on child run directories, not on the root. Producers SHOULD NOT append different executions into one log file, because parallel sessions, reruns after a pause, and selection/cell executions become ambiguous. Each run directory SHOULD include a manifest and submitted-code snapshot so the log is attributable without relying on editor history.
+
+When `origin_path` is supplied, producers SHOULD default Stata's working directory to the source `.do` file's directory before running. This mirrors how users organize project-relative `graph export`, `putexcel`, `esttab using`, `collect export`, and similar output commands. Frontends may disable this with `use_origin_workdir: false` or override it with `working_dir`.
+
+When `persist_generated_files` is true, producers SHOULD copy newly created or modified common output files from the run working directory into `outputs/`, preserving relative paths where practical. Captured graph refs SHOULD also be materialized into `graphs/`, with the corresponding `GraphInfo.file_path` set.
+
 ### 3.4 `results`
 
 Stata's `r()` and `e()` return dictionaries, structurally separated. Each follows the same shape:
@@ -317,6 +349,7 @@ Each entry describes one captured graph. By default the bytes are **not** inline
 | `source_command` | `string \| null` | The user-submitted command line that produced this graph, when isolatable. |
 | `source_line` | `int \| null` | 1-indexed line within the submitted code that produced this graph. |
 | `inline` | `string \| null` | Base64-encoded bytes when the caller explicitly asked for inline (`include_graphs: "inline"`); else `null`. |
+| `file_path` | `string \| null` | Persistent graph file path when the run bundle materialized captured graphs under `log.files.graphs_dir`; else `null`. |
 
 ### 3.7 `error`
 
@@ -426,6 +459,11 @@ The schema also dictates what callers may *ask for*. Every frontend exposes the
 | `graph_format` | `"png" \| "svg" \| "pdf"` | `"png"` | Render format. |
 | `include_dataset_variables` | `bool` | `true` | Set `false` to omit `dataset.variables`. |
 | `timeout_ms` | `int \| null` | `600000` (10 min) | Hard timeout. `null` disables. On expiry, returns `ok: false`, `error.kind: "timeout"`, `rc: -2`. Frontends MAY override the default if their use case demands. |
+| `persist_log_files` | `bool` | `false` | With `origin_path`, writes immutable `.log` / `.smcl` / manifest files under the source `.do` file's `log-files/` directory. |
+| `persist_generated_files` | `bool` | `true` | When log files are persisted, also copies newly created or modified table/export files into `outputs/` and captured graphs into `graphs/`. |
+| `origin_path` | `string \| null` | `null` | Absolute source `.do` path used for working-directory defaults and run-bundle placement. |
+| `use_origin_workdir` | `bool` | `true` | With `origin_path`, `cd` Stata to the source `.do` directory before running. |
+| `working_dir` | `string \| null` | `null` | Explicit Stata working directory; overrides the source `.do` directory. |
 
 Frontends translate their native idiom (MCP `inputSchema`, Jupyter kernel options, VSCode commands) into these names without renaming.
 
@@ -481,6 +519,8 @@ These are *additions* to `run()`. A minimal client only needs `run()` plus which
 | `matrix_ref` | Producer can emit large matrices as refs and supports `get_matrix`. |
 | `multi_session` | Producer supports `session_id != "main"` and `list_sessions`. |
 | `inline_graphs` | Producer supports `include_graphs: "inline"`. |
+| `log_files` | Producer can persist immutable per-run `.log` / `.smcl` bundles. |
+| `run_artifacts` | Producer can materialize captured graphs and copied table/export outputs into the run bundle. |
 
 Consumers detect optional features via `capabilities`, not by parsing `schema_version`. Producers may add entries; agents MUST treat unknown capability names as opaque.
 

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

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

{stata_code-0.3.1 → stata_code-0.4.0}/schema/run_result.schema.json

@@ -247,6 +247,18 @@
     "GraphInfo": {
       "additionalProperties": true,
       "properties": {
+        "file_path": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "File Path"
+        },
         "format": {
           "$ref": "#/$defs/GraphFormat",
           "default": "png"
@@ -327,6 +339,109 @@
       "title": "GraphInfo",
       "type": "object"
     },
+    "LogFileInfo": {
+      "additionalProperties": true,
+      "description": "Persistent on-disk artifacts written for file-backed runs.",
+      "properties": {
+        "append": {
+          "default": false,
+          "title": "Append",
+          "type": "boolean"
+        },
+        "code_path": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Code Path"
+        },
+        "directory": {
+          "title": "Directory",
+          "type": "string"
+        },
+        "graph_paths": {
+          "items": {
+            "type": "string"
+          },
+          "title": "Graph Paths",
+          "type": "array"
+        },
+        "graphs_dir": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Graphs Dir"
+        },
+        "log_path": {
+          "title": "Log Path",
+          "type": "string"
+        },
+        "manifest_path": {
+          "title": "Manifest Path",
+          "type": "string"
+        },
+        "output_paths": {
+          "items": {
+            "type": "string"
+          },
+          "title": "Output Paths",
+          "type": "array"
+        },
+        "outputs_dir": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Outputs Dir"
+        },
+        "policy": {
+          "const": "per_run_directory",
+          "default": "per_run_directory",
+          "title": "Policy",
+          "type": "string"
+        },
+        "smcl_path": {
+          "title": "Smcl Path",
+          "type": "string"
+        },
+        "working_dir": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Working Dir"
+        }
+      },
+      "required": [
+        "directory",
+        "log_path",
+        "smcl_path",
+        "manifest_path"
+      ],
+      "title": "LogFileInfo",
+      "type": "object"
+    },
     "LogInfo": {
       "additionalProperties": true,
       "properties": {
@@ -352,6 +467,17 @@
           "default": null,
           "title": "Error Window"
         },
+        "files": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/LogFileInfo"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
         "head": {
           "default": "",
           "title": "Head",

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

@@ -42,6 +42,7 @@ from stata_code.core.schema import (
     GraphFormat,
     GraphInfo,
     IncludeGraphs,
+    LogFileInfo,
     LogInfo,
     Matrix,
     ResultsInfo,
@@ -57,7 +58,7 @@ from stata_code.core.schema import (
 # Convenience alias: `run(...)` == `execute(...)`.
 run = execute
 
-__version__ = "0.3.1"
+__version__ = "0.4.0"
 
 __all__ = [
     # Primary entry points
@@ -86,6 +87,7 @@ __all__ = [
     "GraphInfo",
     "IncludeGraphs",
     "LogInfo",
+    "LogFileInfo",
     "Matrix",
     "ResultsInfo",
     "StataEdition",

{stata_code-0.3.1 → stata_code-0.4.0}/stata_code/core/__init__.py

@@ -27,6 +27,7 @@ from stata_code.core.schema import (
     GraphFormat,
     GraphInfo,
     IncludeGraphs,
+    LogFileInfo,
     LogInfo,
     Matrix,
     ResultsInfo,
@@ -58,6 +59,7 @@ __all__ = [
     "ErrorContext",
     "Suggestion",
     "LogInfo",
+    "LogFileInfo",
     "ResultsInfo",
     "StataReturns",
     "Matrix",