stata-code 0.7.2__tar.gz → 0.8.1__tar.gz

{stata_code-0.7.2 → stata_code-0.8.1}/CHANGELOG.md

@@ -4,7 +4,47 @@ 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.8.1 — 2026-06-20
+
+### Changed
+
+- **README & metadata refresh.** Documented the VS Code extension's
+  seven-view sidebar (added the **Data** variables browser and the
+  **Outputs** table/export-artifact panel), corrected the error taxonomy
+  count to 31 kinds, and sharpened the Claude Code plugin / VS Code
+  Marketplace descriptions to lead with the empirical-economics workflow
+  (DiD/IV/RDD, publication tables, StatsPAI cross-validation).
+- **Partner module.** Added a Stanford REAP × CoPaper.AI partner block
+  (logos, QR, links) to both the English and Chinese README, with the logo
+  assets bundled under `branding/partners/`.
+
+## 0.8.0 — 2026-06-20
+
+### Added
+
+- **Economist workflow coordination and roadmap.** Added
+  `AGENT_COORDINATION.md` for concurrent-agent lanes and
+  `docs/industry-leader-roadmap.md` for the one-month product plan: workflow
+  intelligence, parity audits, data-MCP handoff, editor/artifact polish, and
+  distribution diagnostics.
+- **Cross-stack and data-MCP workflow references.** The `stata-code` skill now
+  includes `references/parity-audit.md` and
+  `references/data-mcp-handoff.md`, plus cookbook examples for cross-stack
+  parity audits and external-data-MCP handoff into Stata.
+- **Modern empirical-economics package notes.** Added package references for
+  `csdid`, `drdid`, `did_imputation`, `eventstudyinteract`,
+  `did_multiplegt_dyn`, `rdrobust`, `ivreg2`, `ivreghdfe`, `boottest`, and
+  `outreg2`, and wired them into the skill routing table.
+- **MCP prompt discoverability for economist workflows.** Added
+  `plan_cross_stack_parity_audit`, `data_mcp_to_stata_handoff`,
+  `did_event_study`, `iv_2sls`, `rdd`, `publication_table`, and
+  `cross_validate_did` prompts so clients can discover the new protocols and
+  turnkey empirical recipes directly through MCP.
+- **Read-only installation diagnostics.** Added the top-level `stata-code`
+  console script with `doctor` / `verify` commands. The diagnostic reports
+  package/Python version, MCP and kernel extras, `pystata` discovery, console
+  scripts on `PATH`, client/VS Code hints, and an optional live Stata
+  version/edition probe without mutating user configuration.
 
 ## 0.7.2 — 2026-06-20
 

{stata_code-0.7.2 → stata_code-0.8.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: stata-code
-Version: 0.7.2
+Version: 0.8.1
 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,6 +59,24 @@ Description-Content-Type: text/markdown
 [![GitHub release](https://img.shields.io/github/v/release/brycewang-stanford/stata-code)](https://github.com/brycewang-stanford/stata-code/releases)
 [![GitHub stars](https://img.shields.io/github/stars/brycewang-stanford/stata-code?style=social)](https://github.com/brycewang-stanford/stata-code)
 
+<div align="center">
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-logo.png" alt="CoPaper.AI" width="200" /></a>
+    </td>
+    <td width="48"></td>
+    <td align="center">
+      <a href="https://sccei.fsi.stanford.edu/reap"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/stanford-reap-logo.png" alt="Stanford REAP — Center on China's Economy & Institutions" width="280" /></a>
+    </td>
+  </tr>
+</table>
+
+<sub><strong>Stanford REAP × CoPaper.AI</strong> · an academic–industrial AI toolkit for empirical research</sub>
+
+</div>
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/github-instructions.png" alt="stata-code: agent-native Stata bridge — one Python core, multiple frontends (Jupyter kernel, MCP server, VS Code extension)" width="720" />
 </p>
@@ -67,6 +85,22 @@ Description-Content-Type: text/markdown
 
 `stata-code` lets you drive Stata from modern environments: an LLM agent (Claude Code, Cursor, Claude Desktop), a Jupyter notebook, or a VS Code editor session. All frontends share one Python core and return a stable, structured, **agent-friendly** result schema.
 
+**For empirical economists.** Drive Stata in plain language: run **DiD, IV, RDD, and publication-ready `esttab` tables in one conversation** — then cross-check each estimate across Stata and Python so you only trust results that *agree* (the Cunningham cross-package robustness check).
+
+**Try it in 60 seconds** with [Claude Code](https://github.com/anthropics/claude-code) — no global install needed:
+
+```bash
+claude mcp add stata-code --scope user -- uvx --from "stata-code[mcp]" stata-code-mcp
+```
+
+Then just ask:
+
+> *"Using `data/cfps_panel.dta`, run a two-way fixed-effects regression of monthly wage on the treatment (controls: `age age2 edu industry`), then test heterogeneous effects with Callaway-Sant'Anna, and export an `esttab` table."*
+
+`stata-code` writes the do-file, runs it, returns the table, and interprets the result — and can re-estimate the same ATT with [StatsPAI](https://github.com/brycewang-stanford/StatsPAI) to confirm the two stacks agree. These workflows ship as one-call MCP prompts (`did_event_study`, `iv_2sls`, `rdd`, `publication_table`, `cross_validate_did`) backed by an on-demand [recipe library](skills/stata-code/references/recipes/).
+
+**Why `stata-code`:** MIT-licensed · ships as an MCP server, a bundled agent skill, a Jupyter kernel, **and** a VS Code extension · one structured, token-economy result schema (typed errors, native `r()` / `e()`) · cross-stack validation with StatsPAI for the Cunningham check.
+
 ```text
                     ┌────────────────────────────────────────┐
                     │     stata-code core (Python)           │
@@ -84,12 +118,18 @@ Description-Content-Type: text/markdown
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**Status: v0.7 (May 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. The test suite covers schema, runner, MCP, kernel, notebook, run-index, subprocess-pool, and VS Code modules; CI also checks linting, type safety, schema generation, package metadata, and VSIX packaging. License: **MIT**.
+**Status: v0.8 (June 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. The test suite covers schema, runner, MCP, kernel, notebook, run-index, subprocess-pool, and VS Code modules; CI also checks linting, type safety, schema generation, package metadata, and VSIX packaging. License: **MIT**.
 
-Two workflows the current release explicitly supports for end users:
+Three workflows the current tree explicitly supports for end users and agents:
 
 - **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 since 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).
+- **Economist workflow guides.** The bundled skill and cookbook now cover
+  modern DiD, IV/weak-IV, RDD, table export, data-MCP handoff, and
+  cross-stack parity audits. `stata-code` runs and audits the Stata leg; R,
+  Python, and official data MCPs remain separate tools with explicit handoff
+  files and source metadata. See [`skills/stata-code/references/`](skills/stata-code/references/)
+  and [`examples/`](examples/).
 
 ---
 
@@ -138,6 +178,19 @@ pip install -e ".[mcp,kernel]"
 
 Note: `pystata` is **not** on PyPI; it ships with Stata. `stata-code` auto-discovers it on macOS at `/Applications/Stata/utilities/pystata` and at equivalent Linux / Windows paths. If your install is elsewhere, add it to `PYTHONPATH` before importing.
 
+Verify the local setup with the read-only doctor:
+
+```bash
+stata-code doctor
+stata-code doctor --json          # machine-readable output
+stata-code doctor --no-stata-probe # skip live Stata initialization
+```
+
+The doctor reports the package/Python version, MCP and Jupyter extras, `pystata`
+discovery, console scripts on `PATH`, client/VS Code configuration hints, and a
+best-effort Stata version/edition probe. It never edits shell, Stata, Claude, or
+VS Code config.
+
 ---
 
 ## Quick Start
@@ -315,8 +368,11 @@ resources:
 
 MCP prompts are available for common agent workflows:
 `run_do_file_and_report`, `debug_stata_error`,
-`fix_and_rerun_until_passes`, `replication_audit`, and
-`summarize_estimation_results`.
+`fix_and_rerun_until_passes`, `replication_audit`,
+`plan_cross_stack_parity_audit`, `data_mcp_to_stata_handoff`,
+`summarize_estimation_results`, `run_notebook_cell_and_report`,
+`fix_and_rerun_notebook_cell`, `did_event_study`, `iv_2sls`, `rdd`,
+`publication_table`, and `cross_validate_did`.
 
 ### As a Jupyter Kernel
 
@@ -347,7 +403,7 @@ Then open Jupyter Notebook / JupyterLab (or a `.ipynb` in VS Code), pick **Stata
 
 ### As a VS Code Extension
 
-The companion extension is on the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode). It spawns `stata-code-mcp` as a child process and adds syntax highlighting, an Outline view for `**#` sections and `program define` blocks, code-lens "Run cell" and "Run section" actions on `.do` files, a sidebar (sessions / last result / run history / logs / graphs), status-bar indicators, completions, help lookup, conservative variable rename, and inline diagnostics from the v1.0 typed errors.
+The companion extension is on the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode). It spawns `stata-code-mcp` as a child process and adds syntax highlighting, an Outline view for `**#` sections and `program define` blocks, code-lens "Run cell" and "Run section" actions on `.do` files, a **seven-view sidebar** (sessions / last result / **data variables** / run history / logs / graphs / **outputs**) — including an agent-native equivalent of Stata's **Variables window** and an **Outputs** panel that surfaces the `esttab` tables and `export` files each run writes to disk — status-bar indicators, completions, help lookup, conservative variable rename, and inline diagnostics from the v1.0 typed errors.
 
 ```bash
 # from the VS Code CLI
@@ -358,6 +414,12 @@ Or open the **Extensions** sidebar in VS Code and search `stata-code`. The exten
 
 On first activation the extension probes for `stata-code-mcp` on `PATH` (and in any workspace `.venv` / `venv`). If nothing resolves, it shows a one-time install hint with the exact `pip install "stata-code[mcp]"` command — choose **Don't show again** to silence it for the installed extension version.
 
+If the extension or an MCP client cannot find the server, run
+`stata-code doctor --no-stata-probe` in the same Python environment. It reports
+whether `stata-code-mcp` is on `PATH` and suggests absolute-path or
+`python -m stata_code.mcp` fallbacks for GUI clients whose `PATH` differs from
+your shell.
+
 #### Cell and section conventions
 
 The extension recognizes two complementary structural markers inside `.do` files. Either can be mixed in the same file; they do not conflict.
@@ -437,7 +499,7 @@ stata_code/
 | Jupyter kernel | ✓ | — | — | ✓ |
 | Unified result schema | ✓ ([SCHEMA.md](SCHEMA.md)) | per-tool | per-tool | per-tool |
 | Token-economy defaults | ✓ (log refs, graph refs) | — | — | — |
-| Typed errors + suggestions | ✓ (32 kinds) | — | — | — |
+| Typed errors + suggestions | ✓ (31 kinds) | — | — | — |
 | Multi-session | ✓ (Stata frames) | partial | — | — |
 | Mature ecosystem | early | ✓ (statamcp.com, cookbook) | ✓ (11k installs) | ✓ |
 
@@ -447,7 +509,7 @@ stata_code/
 
 ## Roadmap
 
-### Done (through v0.7 — May 2026)
+### Done (current tree)
 
 - v1.0 result schema ([SCHEMA.md](SCHEMA.md))
 - `pystata`-based runner with native-typed `r()`, `e()`, and matrices
@@ -456,15 +518,21 @@ stata_code/
 - Graph capture: `png` / `svg` / `pdf` with ref store and source-command attribution
 - Log truncation with ref store
 - Warning extraction: 5 categories + generic notes
-- 32-kind error taxonomy with canonical suggestions
+- 31-kind error taxonomy with canonical suggestions
 - MCP server: 18 tools, including notebook navigation / search / atomic edits, the run-bundle index (`list_runs`), log grep (`search_log`), dataset inspection (`inspect_data`), and package installation (`install_package`)
 - Jupyter kernel: rewired to the v1.0 pipeline, kernel logos bundled
 - Matrix size cap + `get_matrix(ref)` for large matrices (>10k cells)
 - Subprocess-backed hard timeout and cancellation for the public Python API and MCP server: `timeout_ms`, `cancel(session_id)`, and MCP `cancel_session`
 - Per-cell repair loop on `.ipynb` via `notebook_outline` / `notebook_get_cell` / `notebook_edit_cell` with optimistic-concurrency `expected_source` guards and `origin_cell_id` echo on `RunResult`
 - Persistent run bundles + `list_runs` query over `manifest.json` files (filter by cell / origin / session / since / ok; page with limit / offset)
+- Read-only `stata-code doctor` / `verify` diagnostics for package version,
+  extras, `pystata` discovery, console scripts, client hints, and optional live
+  Stata version probing
+- Economist workflow layer: skill references and examples for modern DiD,
+  IV/weak-IV, RDD, table export, data-MCP handoff, and cross-stack parity
+  audits
 - JSON Schema artifact auto-generated from `schema.py`: [`schema/run_result.schema.json`](schema/run_result.schema.json)
-- VS Code extension published to the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode): syntax highlighting, section outline/navigation, code-lens cell and section runners, sidebar (sessions / last result / run history / logs / graphs), status bar, completions, conservative variable rename, diagnostics, MCP child-process spawn
+- VS Code extension published to the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode): syntax highlighting, section outline/navigation, code-lens cell and section runners, seven-view sidebar (sessions / last result / data variables / run history / logs / graphs / outputs), status bar, completions, conservative variable rename, diagnostics, MCP child-process spawn
 - Clean-room license policy ([LICENSE-POLICY.md](LICENSE-POLICY.md))
 
 ### Next Up
@@ -510,3 +578,36 @@ Stata is a registered trademark of StataCorp LLC. This project is independent an
 ## Acknowledgements
 
 The Stata tooling landscape that this project builds on and learns from is surveyed in [References-tools.md](References-tools.md). All listed projects retain their own licenses and authorship; please consult each repository before reuse.
+
+---
+
+<div align="center">
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-logo.png" alt="CoPaper.AI" width="200" /></a>
+    </td>
+    <td width="40"></td>
+    <td align="center">
+      <a href="https://sccei.fsi.stanford.edu/reap"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/stanford-reap-logo.png" alt="Stanford REAP" width="280" /></a>
+    </td>
+  </tr>
+</table>
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-qrcode.png" alt="Visit copaper.ai" width="160" /></a><br/>
+      <strong>Visit <a href="https://copaper.ai">copaper.ai</a></strong>
+    </td>
+    <td align="center">
+      <img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-wechat.jpg" alt="CoPaper.AI WeChat" width="160" /><br/>
+      <strong>WeChat: CoPaper.AI</strong>
+    </td>
+  </tr>
+</table>
+
+<sub>Maintained by <a href="https://copaper.ai"><strong>CoPaper.AI</strong></a>, incubated at <a href="https://sccei.fsi.stanford.edu/reap"><strong>Stanford REAP / SCCEI</strong></a> · AI Assistant for Empirical Research</sub>
+
+</div>

{stata_code-0.7.2 → stata_code-0.8.1}/README.md

@@ -20,6 +20,24 @@
 [![GitHub release](https://img.shields.io/github/v/release/brycewang-stanford/stata-code)](https://github.com/brycewang-stanford/stata-code/releases)
 [![GitHub stars](https://img.shields.io/github/stars/brycewang-stanford/stata-code?style=social)](https://github.com/brycewang-stanford/stata-code)
 
+<div align="center">
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-logo.png" alt="CoPaper.AI" width="200" /></a>
+    </td>
+    <td width="48"></td>
+    <td align="center">
+      <a href="https://sccei.fsi.stanford.edu/reap"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/stanford-reap-logo.png" alt="Stanford REAP — Center on China's Economy & Institutions" width="280" /></a>
+    </td>
+  </tr>
+</table>
+
+<sub><strong>Stanford REAP × CoPaper.AI</strong> · an academic–industrial AI toolkit for empirical research</sub>
+
+</div>
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/github-instructions.png" alt="stata-code: agent-native Stata bridge — one Python core, multiple frontends (Jupyter kernel, MCP server, VS Code extension)" width="720" />
 </p>
@@ -28,6 +46,22 @@
 
 `stata-code` lets you drive Stata from modern environments: an LLM agent (Claude Code, Cursor, Claude Desktop), a Jupyter notebook, or a VS Code editor session. All frontends share one Python core and return a stable, structured, **agent-friendly** result schema.
 
+**For empirical economists.** Drive Stata in plain language: run **DiD, IV, RDD, and publication-ready `esttab` tables in one conversation** — then cross-check each estimate across Stata and Python so you only trust results that *agree* (the Cunningham cross-package robustness check).
+
+**Try it in 60 seconds** with [Claude Code](https://github.com/anthropics/claude-code) — no global install needed:
+
+```bash
+claude mcp add stata-code --scope user -- uvx --from "stata-code[mcp]" stata-code-mcp
+```
+
+Then just ask:
+
+> *"Using `data/cfps_panel.dta`, run a two-way fixed-effects regression of monthly wage on the treatment (controls: `age age2 edu industry`), then test heterogeneous effects with Callaway-Sant'Anna, and export an `esttab` table."*
+
+`stata-code` writes the do-file, runs it, returns the table, and interprets the result — and can re-estimate the same ATT with [StatsPAI](https://github.com/brycewang-stanford/StatsPAI) to confirm the two stacks agree. These workflows ship as one-call MCP prompts (`did_event_study`, `iv_2sls`, `rdd`, `publication_table`, `cross_validate_did`) backed by an on-demand [recipe library](skills/stata-code/references/recipes/).
+
+**Why `stata-code`:** MIT-licensed · ships as an MCP server, a bundled agent skill, a Jupyter kernel, **and** a VS Code extension · one structured, token-economy result schema (typed errors, native `r()` / `e()`) · cross-stack validation with StatsPAI for the Cunningham check.
+
 ```text
                     ┌────────────────────────────────────────┐
                     │     stata-code core (Python)           │
@@ -45,12 +79,18 @@
               └─────────────┘  └────────────┘  └─────────────────┘
 ```
 
-**Status: v0.7 (May 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. The test suite covers schema, runner, MCP, kernel, notebook, run-index, subprocess-pool, and VS Code modules; CI also checks linting, type safety, schema generation, package metadata, and VSIX packaging. License: **MIT**.
+**Status: v0.8 (June 2026)** — the core, MCP server, Jupyter kernel, and VS Code extension work end-to-end against Stata 18 MP. The test suite covers schema, runner, MCP, kernel, notebook, run-index, subprocess-pool, and VS Code modules; CI also checks linting, type safety, schema generation, package metadata, and VSIX packaging. License: **MIT**.
 
-Two workflows the current release explicitly supports for end users:
+Three workflows the current tree explicitly supports for end users and agents:
 
 - **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 since 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).
+- **Economist workflow guides.** The bundled skill and cookbook now cover
+  modern DiD, IV/weak-IV, RDD, table export, data-MCP handoff, and
+  cross-stack parity audits. `stata-code` runs and audits the Stata leg; R,
+  Python, and official data MCPs remain separate tools with explicit handoff
+  files and source metadata. See [`skills/stata-code/references/`](skills/stata-code/references/)
+  and [`examples/`](examples/).
 
 ---
 
@@ -99,6 +139,19 @@ pip install -e ".[mcp,kernel]"
 
 Note: `pystata` is **not** on PyPI; it ships with Stata. `stata-code` auto-discovers it on macOS at `/Applications/Stata/utilities/pystata` and at equivalent Linux / Windows paths. If your install is elsewhere, add it to `PYTHONPATH` before importing.
 
+Verify the local setup with the read-only doctor:
+
+```bash
+stata-code doctor
+stata-code doctor --json          # machine-readable output
+stata-code doctor --no-stata-probe # skip live Stata initialization
+```
+
+The doctor reports the package/Python version, MCP and Jupyter extras, `pystata`
+discovery, console scripts on `PATH`, client/VS Code configuration hints, and a
+best-effort Stata version/edition probe. It never edits shell, Stata, Claude, or
+VS Code config.
+
 ---
 
 ## Quick Start
@@ -276,8 +329,11 @@ resources:
 
 MCP prompts are available for common agent workflows:
 `run_do_file_and_report`, `debug_stata_error`,
-`fix_and_rerun_until_passes`, `replication_audit`, and
-`summarize_estimation_results`.
+`fix_and_rerun_until_passes`, `replication_audit`,
+`plan_cross_stack_parity_audit`, `data_mcp_to_stata_handoff`,
+`summarize_estimation_results`, `run_notebook_cell_and_report`,
+`fix_and_rerun_notebook_cell`, `did_event_study`, `iv_2sls`, `rdd`,
+`publication_table`, and `cross_validate_did`.
 
 ### As a Jupyter Kernel
 
@@ -308,7 +364,7 @@ Then open Jupyter Notebook / JupyterLab (or a `.ipynb` in VS Code), pick **Stata
 
 ### As a VS Code Extension
 
-The companion extension is on the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode). It spawns `stata-code-mcp` as a child process and adds syntax highlighting, an Outline view for `**#` sections and `program define` blocks, code-lens "Run cell" and "Run section" actions on `.do` files, a sidebar (sessions / last result / run history / logs / graphs), status-bar indicators, completions, help lookup, conservative variable rename, and inline diagnostics from the v1.0 typed errors.
+The companion extension is on the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode). It spawns `stata-code-mcp` as a child process and adds syntax highlighting, an Outline view for `**#` sections and `program define` blocks, code-lens "Run cell" and "Run section" actions on `.do` files, a **seven-view sidebar** (sessions / last result / **data variables** / run history / logs / graphs / **outputs**) — including an agent-native equivalent of Stata's **Variables window** and an **Outputs** panel that surfaces the `esttab` tables and `export` files each run writes to disk — status-bar indicators, completions, help lookup, conservative variable rename, and inline diagnostics from the v1.0 typed errors.
 
 ```bash
 # from the VS Code CLI
@@ -319,6 +375,12 @@ Or open the **Extensions** sidebar in VS Code and search `stata-code`. The exten
 
 On first activation the extension probes for `stata-code-mcp` on `PATH` (and in any workspace `.venv` / `venv`). If nothing resolves, it shows a one-time install hint with the exact `pip install "stata-code[mcp]"` command — choose **Don't show again** to silence it for the installed extension version.
 
+If the extension or an MCP client cannot find the server, run
+`stata-code doctor --no-stata-probe` in the same Python environment. It reports
+whether `stata-code-mcp` is on `PATH` and suggests absolute-path or
+`python -m stata_code.mcp` fallbacks for GUI clients whose `PATH` differs from
+your shell.
+
 #### Cell and section conventions
 
 The extension recognizes two complementary structural markers inside `.do` files. Either can be mixed in the same file; they do not conflict.
@@ -398,7 +460,7 @@ stata_code/
 | Jupyter kernel | ✓ | — | — | ✓ |
 | Unified result schema | ✓ ([SCHEMA.md](SCHEMA.md)) | per-tool | per-tool | per-tool |
 | Token-economy defaults | ✓ (log refs, graph refs) | — | — | — |
-| Typed errors + suggestions | ✓ (32 kinds) | — | — | — |
+| Typed errors + suggestions | ✓ (31 kinds) | — | — | — |
 | Multi-session | ✓ (Stata frames) | partial | — | — |
 | Mature ecosystem | early | ✓ (statamcp.com, cookbook) | ✓ (11k installs) | ✓ |
 
@@ -408,7 +470,7 @@ stata_code/
 
 ## Roadmap
 
-### Done (through v0.7 — May 2026)
+### Done (current tree)
 
 - v1.0 result schema ([SCHEMA.md](SCHEMA.md))
 - `pystata`-based runner with native-typed `r()`, `e()`, and matrices
@@ -417,15 +479,21 @@ stata_code/
 - Graph capture: `png` / `svg` / `pdf` with ref store and source-command attribution
 - Log truncation with ref store
 - Warning extraction: 5 categories + generic notes
-- 32-kind error taxonomy with canonical suggestions
+- 31-kind error taxonomy with canonical suggestions
 - MCP server: 18 tools, including notebook navigation / search / atomic edits, the run-bundle index (`list_runs`), log grep (`search_log`), dataset inspection (`inspect_data`), and package installation (`install_package`)
 - Jupyter kernel: rewired to the v1.0 pipeline, kernel logos bundled
 - Matrix size cap + `get_matrix(ref)` for large matrices (>10k cells)
 - Subprocess-backed hard timeout and cancellation for the public Python API and MCP server: `timeout_ms`, `cancel(session_id)`, and MCP `cancel_session`
 - Per-cell repair loop on `.ipynb` via `notebook_outline` / `notebook_get_cell` / `notebook_edit_cell` with optimistic-concurrency `expected_source` guards and `origin_cell_id` echo on `RunResult`
 - Persistent run bundles + `list_runs` query over `manifest.json` files (filter by cell / origin / session / since / ok; page with limit / offset)
+- Read-only `stata-code doctor` / `verify` diagnostics for package version,
+  extras, `pystata` discovery, console scripts, client hints, and optional live
+  Stata version probing
+- Economist workflow layer: skill references and examples for modern DiD,
+  IV/weak-IV, RDD, table export, data-MCP handoff, and cross-stack parity
+  audits
 - JSON Schema artifact auto-generated from `schema.py`: [`schema/run_result.schema.json`](schema/run_result.schema.json)
-- VS Code extension published to the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode): syntax highlighting, section outline/navigation, code-lens cell and section runners, sidebar (sessions / last result / run history / logs / graphs), status bar, completions, conservative variable rename, diagnostics, MCP child-process spawn
+- VS Code extension published to the Marketplace as [`brycewang-stanford.stata-code-vscode`](https://marketplace.visualstudio.com/items?itemName=brycewang-stanford.stata-code-vscode): syntax highlighting, section outline/navigation, code-lens cell and section runners, seven-view sidebar (sessions / last result / data variables / run history / logs / graphs / outputs), status bar, completions, conservative variable rename, diagnostics, MCP child-process spawn
 - Clean-room license policy ([LICENSE-POLICY.md](LICENSE-POLICY.md))
 
 ### Next Up
@@ -471,3 +539,36 @@ Stata is a registered trademark of StataCorp LLC. This project is independent an
 ## Acknowledgements
 
 The Stata tooling landscape that this project builds on and learns from is surveyed in [References-tools.md](References-tools.md). All listed projects retain their own licenses and authorship; please consult each repository before reuse.
+
+---
+
+<div align="center">
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-logo.png" alt="CoPaper.AI" width="200" /></a>
+    </td>
+    <td width="40"></td>
+    <td align="center">
+      <a href="https://sccei.fsi.stanford.edu/reap"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/stanford-reap-logo.png" alt="Stanford REAP" width="280" /></a>
+    </td>
+  </tr>
+</table>
+
+<table>
+  <tr>
+    <td align="center">
+      <a href="https://copaper.ai"><img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-qrcode.png" alt="Visit copaper.ai" width="160" /></a><br/>
+      <strong>Visit <a href="https://copaper.ai">copaper.ai</a></strong>
+    </td>
+    <td align="center">
+      <img src="https://raw.githubusercontent.com/brycewang-stanford/stata-code/main/branding/partners/copaper-wechat.jpg" alt="CoPaper.AI WeChat" width="160" /><br/>
+      <strong>WeChat: CoPaper.AI</strong>
+    </td>
+  </tr>
+</table>
+
+<sub>Maintained by <a href="https://copaper.ai"><strong>CoPaper.AI</strong></a>, incubated at <a href="https://sccei.fsi.stanford.edu/reap"><strong>Stanford REAP / SCCEI</strong></a> · AI Assistant for Empirical Research</sub>
+
+</div>

stata_code-0.8.1/docs/industry-leader-roadmap.md

@@ -0,0 +1,99 @@
+# stata-code Industry Leadership Roadmap
+
+This roadmap translates the June 2026 empirical-research MCP landscape into
+work that fits `stata-code`'s architecture. The project should win by being the
+most reliable agent-native Stata execution and audit layer for empirical
+economists, not by becoming a grab-bag data platform or a second R/Python
+runtime.
+
+## North Star
+
+`stata-code` should be the default way an AI agent runs, inspects, repairs, and
+audits Stata work:
+
+- one execution core across Python, MCP, Jupyter, and VS Code;
+- stable `RunResult` schema with typed errors and native `r()` / `e()` values;
+- token-efficient logs, graphs, matrices, and run bundles;
+- economist-facing workflows for DiD, IV, RDD, tables, data handoff, and
+  cross-package verification.
+
+## Product Pillars
+
+1. **Reliable execution contract.** Keep `SCHEMA.md` load-bearing. Agents
+   branch on `ok`, `error.kind`, `results.e`, refs, and run manifests instead
+   of parsing log prose.
+2. **Econometrics workflow intelligence.** Ship concise skill references and
+   prompts that know the Stata commands economists actually use: `csdid`,
+   `did_imputation`, `eventstudyinteract`, `rdrobust`, `ivreg2`,
+   `ivreghdfe`, `boottest`, `esttab`, `collect`, and related packages.
+3. **Cross-stack parity audits.** Treat R/Python/Stata disagreement as a first
+   class research risk. `stata-code` should run the Stata leg and define the
+   comparison protocol without pretending to own the R or Python runtimes.
+4. **Data-MCP handoff.** External MCP servers can discover and fetch official
+   data. `stata-code` should document and validate the handoff into Stata:
+   source metadata, stable raw files, key checks, and reproducible imports.
+5. **Editor and artifact ergonomics.** VS Code should make sessions, graphs,
+   logs, tables, data previews, and run bundles easy to inspect without hiding
+   the underlying structured result.
+6. **Distribution confidence.** Install and runtime checks should be easy to
+   verify without mutating user config. Prefer `doctor`/`verify` diagnostics
+   before any automatic config writer.
+
+## Scope Boundaries
+
+`stata-code` should not directly bundle data-provider APIs, R sessions, Python
+causal libraries, or paid services. Those are separate tools. The durable
+boundary is: external data/model tools produce files or results; `stata-code`
+executes and audits the Stata side with traceable artifacts.
+
+## One-Month Execution Plan
+
+### Week 1: Workflow Layer
+
+- Add cross-agent coordination and this roadmap.
+- Expand the skill reference library for modern DiD, IV/weak-IV, RDD,
+  table-export, data-MCP handoff, and parity audits.
+- Add examples that show how agents should use the workflows without claiming
+  unsupported automation.
+- Add MCP prompts for parity audit planning, data-MCP-to-Stata handoff, and
+  turnkey method templates for DiD/event study, IV/2SLS, RDD, and publication
+  tables.
+- Validate with skill packaging tests, MCP prompt tests, and markdown hygiene.
+
+### Week 2: Diagnostics and Setup Confidence
+
+- Ship a read-only `stata-code doctor` / `verify` command that reports Python,
+  `stata-code`, MCP extras, `pystata` discovery, Stata version/edition, PATH
+  resolution, and common client config hints.
+- Keep config writing out of scope until backups and dry-run behavior exist.
+- Add tests for missing `pystata`, missing MCP extra, path mismatch, and JSON
+  output.
+
+### Week 3: VS Code and Artifacts
+
+- Improve dataset preview from first-100 text output toward a paged/filterable
+  view or a clearly documented intermediate step.
+- Surface table/export artifacts from run bundles more explicitly.
+- Add tests around formatter and tree-provider behavior before broad UI work.
+
+### Week 4: Release Quality
+
+- Sweep README.md, README.zh.md, vscode/README.md, CHANGELOG.md, examples,
+  and skill docs for drift.
+- Run release-relevant checks: version guard, schema export, skill zip build,
+  MCP tests, core tests that do not require Stata, and VS Code compile/tests if
+  touched.
+- Prepare release notes that separate shipped features from roadmap items.
+
+## Success Criteria
+
+- Agents can find a documented path for the top empirical workflows without
+  loading the whole reference library.
+- Parity audits preserve sample definitions, package versions, estimator
+  defaults, failure/refusal behavior, and numeric tolerances.
+- Data pulled by external MCP servers enters Stata through a reproducible raw
+  file plus metadata handoff, not through unstated browser-copy steps.
+- User-facing docs explain that `stata-code` runs Stata and coordinates with
+  other MCP tools; they do not imply that it directly runs R/Python or hosts
+  official data APIs.
+- All changed surfaces have targeted validation evidence before handoff.