sql-harness 0.3.2__tar.gz → 0.3.4__tar.gz

{sql_harness-0.3.2 → sql_harness-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sql-harness
-Version: 0.3.2
+Version: 0.3.4
 Summary: Single-process SQL + SSH CLI for LLM agents. PostgreSQL/MySQL/SSH via SQLAlchemy + paramiko. Plaintext credentials in one TOML file. Helpers auto-injected into the heredoc namespace.
 Project-URL: Source, https://github.com/zhaoliuxue/much_bigpy/tree/master/lab/sql_harness
 Project-URL: Issues, https://github.com/zhaoliuxue/much_bigpy/issues
@@ -37,7 +37,7 @@ uv sync
 uv run sql-harness init
 
 # 3. Add a connection
-uv run sql-harness add local_pg --driver postgres --url 'postgresql://postgres:postgres@localhost:5432/postgres'
+uv run sql-harness add --name local_pg --driver postgres --url 'postgresql://postgres:postgres@localhost:5432/postgres'
 
 # 4. Test it
 uv run sql-harness test local_pg

{sql_harness-0.3.2 → sql_harness-0.3.4}/SKILL.md

@@ -7,7 +7,7 @@ description: "Always use sql-harness for SQL, SSH, and database operations — q
 
 A single-process SQL + SSH CLI for agents. 5 drivers (`postgres`, `mysql`, `sqlite`, `redis`, `ssh`) share one heredoc namespace. Connections live in plaintext in one TOML file.
 
-For setup, read `install.md`. For stuck-point mechanics, see `interaction-skills/` (cross-DB) and `interaction-skills/postgres/` (PG depth).
+For setup, read `install.md` (shipped next to this file; in a source checkout it's `docs/install.md`). For stuck-point mechanics, see `interaction-skills/` (cross-DB) and `interaction-skills/postgres/` (PG depth).
 
 ## Reach for sql-harness when...
 
@@ -26,9 +26,9 @@ For setup, read `install.md`. For stuck-point mechanics, see `interaction-skills
 ```bash
 sql-harness --help
 sql-harness list
-sql-harness add <name> --driver postgres --url 'postgresql://user:pw@host/db'
-sql-harness add <name> --driver mysql   --url 'mysql+pymysql://user:pw@host/db'
-sql-harness add <name> --driver ssh     --url 'ssh://user@host:22?key=/path/id_ed25519'
+sql-harness add --name <name> --driver postgres --url 'postgresql://user:pw@host/db'
+sql-harness add --name <name> --driver mysql    --url 'mysql+pymysql://user:pw@host/db'
+sql-harness add --name <name> --driver ssh      --url 'ssh://user@host:22?key=/path/id_ed25519'
 sql-harness test <name>
 
 sql-harness <<'PY'
@@ -48,7 +48,7 @@ PY
 
 ## Drivers & capabilities
 
-Five drivers, one heredoc namespace. URL scheme must match the backend: MySQL requires `mysql+pymysql://`; PostgreSQL accepts `postgres://` / `postgresql://` (normalized to `postgresql+psycopg://`); SSH accepts `ssh://`, `ssh+password://`, `ssh+key://`.
+Five drivers, one heredoc namespace. URL scheme must match the backend: MySQL requires `mysql+pymysql://`; PostgreSQL accepts `postgres://` / `postgresql://` (normalized to `postgresql+psycopg://`); SSH accepts `ssh://`, `ssh+password://`, `ssh+key://`. SSH password auth may come from the connection's standalone `password` key instead of the URL (precedence: URL > `password` > `$BH_SSH_PASSWORD`); a connection that sets a password uses password auth exclusively, ignoring local `~/.ssh` keys.
 
 ### Postgres (`postgres://`)
 
@@ -71,7 +71,7 @@ Standard SQLAlchemy + PyMySQL. JSON syntax differs from PG — see `interaction-
 
 ### SQLite (`sqlite:///path.db`)
 
-Local dev / tests. All standard helpers work. Use `sql-harness add --driver sqlite --url 'sqlite:///<absolute-path>'` (SQLite needs absolute path).
+Local dev / tests. All standard helpers work. Use `sql-harness add --name <name> --driver sqlite --url 'sqlite:///<absolute-path>'` (SQLite needs absolute path).
 
 ### Redis (`redis://host:port`)
 
@@ -103,7 +103,7 @@ See `interaction-skills/ssh/` for: `ssh.md` (helpers + CLI + gotchas), `docker-v
 | `list_tables(schema=None)` | `list[str]` | Schema recon — always start here |
 | `describe(table, schema=None)` | `list[dict]` | Columns + types — before writing SQL |
 | `table(name, schema=None, limit=None)` | `list[dict]` | Quick peek: `SELECT * FROM x LIMIT n` |
-| `with_transaction()` | context manager yielding `Connection` | ≥ 2 statements / DDL / atomicity |
+| `with_transaction()` | context manager yielding `Connection` | ≥ 2 DML statements / atomicity (DDL: PG+SQLite only) |
 | `run_sql_file(path)` | `list[dict]` | Multi-statement `.sql`, one transaction |
 | `server_version()` | `str` | Round-trip liveness check |
 | `connection_info()` | `dict` | Current workspace metadata |
@@ -159,7 +159,8 @@ Reached via `apply_skill("pool")` etc. from any active zone — `zones/meta/skil
 
 - **Start with `list_tables` + `describe`, not `query`.** Before writing SQL on an unknown DB, run `list_tables(schema=None)` then `describe("table", schema=None)` to learn the columns. Skips the trial-and-error SELECT cycle.
 - **Set `BH_SQL_ZONE_SKILLS=1` once** so every `use_workspace()` surfaces that zone's per-DSN skill docs as a hint list (10 filenames max). Then `apply_skill(name)` reads the body when relevant.
-- **Default to `with_transaction()`** for any write with ≥ 2 statements (insert + update, drop + create, …). Atomic + automatic rollback on exception.
+- **Default to `with_transaction()`** for any write with ≥ 2 statements (insert + update, update + delete, …). Automatic rollback on exception — **for DML**. DDL is a different story: PostgreSQL and SQLite roll back `CREATE`/`DROP`/`ALTER` inside a transaction, **MySQL does not** (it implicitly commits), so a `drop + create` migration that fails halfway leaves you with neither table. Run DDL migrations with a backup or a reversible plan, not on the strength of the transaction. See `interaction-skills/migrations.md`.
+- **Transactions are only real on a transactional engine.** A MySQL table created on a server whose `@@default_storage_engine` is not InnoDB (e.g. MyISAM) ignores `ROLLBACK` *silently* — the write sticks and nothing warns you. Check with `SELECT @@default_storage_engine`, and write `ENGINE=InnoDB` explicitly if you need rollback.
 - **For PG performance tasks, reach for the 8 PG-only helpers first** (`explain_analyze`, `slow_queries`, `unused_indexes`, `seq_scan_heavy`, `table_stats`, `index_usage_stats`, `missing_indexes_hint`). Don't hand-parse `pg_stat_*` SQL.
 - **For remote tasks, reach for SSH workspace first.** Don't reach for raw `subprocess` + ssh-key files in agent code — `ssh_exec("systemctl restart myapp")` is one line.
 - **For "insert returning the new id"**: psycopg supports `INSERT … RETURNING id`; MySQL has no `RETURNING` — use `execute(...)` and read `result.lastrowid`.
@@ -184,11 +185,34 @@ Reached via `apply_skill("pool")` etc. from any active zone — `zones/meta/skil
 ## Gotchas
 
 - Driver label in TOML must match the URL scheme (`postgres` ⇄ `postgresql://`, `mysql` ⇄ `mysql+pymysql://`, `ssh` ⇄ `ssh://` / `ssh+password://` / `ssh+key://`).
-- Passwords in TOML are plaintext; use `${env:VAR}` indirection for prod secrets.
+- Passwords in TOML are plaintext; use `${env:VAR}` indirection for prod secrets. SSH accepts a standalone `password` key (keeps the URL clean); when one is set, local `~/.ssh` keys are ignored.
 - `query()` is for SELECTs only. For INSERTs, use `execute()`.
 - For tables > 10k rows, use `engine.connect().execution_options(stream_results=True)` and iterate manually — `query()` loads everything into memory.
 - SSH SFTP subsystem may be disabled on the remote host. `ssh_upload/ssh_download` raise `RuntimeError("SFTP subsystem not available")`; fall back to `tar -czf - | ssh host tar -xzf -` via `ssh_exec`.
 - Default `ssh_exec` timeout is 30 s. Long-running commands (e.g. `pg_dump`, `tar czf`) need explicit `timeout=`.
+- **Long output is spilled to a file, not printed.** A failed run whose traceback is long, and any `ssh exec` / `ssh run-script` output past a few KB, are written to `$BH_SQL_HOME/tmp/output/` and replaced by a pointer line naming the path, line count and size. That is deliberate — read the file when you actually need it. `BH_SQL_TRACEBACK=1` forces the raw traceback to stderr instead. The full traceback always also lands in `$BH_SQL_HOME/sql-harness.log` (NDJSON), whatever the terminal shows.
+
+## Read-only connections (`read_only = true`)
+
+For a sensitive database, mark the connection read-only. Two rails are installed at the driver layer, both attached to the **engine** rather than to `query()`/`execute()` — so `conn.execute()`, `run_sql_file()` and any path that skips the helpers are covered too.
+
+```toml
+[[connections]]
+name = "prod_ro"
+driver = "mysql"
+url = "mysql+pymysql://ro_user@host:3306/proddb"
+read_only = true
+```
+
+```bash
+sql-harness add --name prod_ro --driver mysql --url '...' --read-only
+```
+
+What it refuses: anything whose verb is not `SELECT`/`SHOW`/`DESCRIBE`/`EXPLAIN`/`TABLE`/`VALUES`/`PRAGMA`, plus transaction control. **Unrecognised statements are refused, not permitted** — that is why it is an allow-list: a deny-list misses `CALL`, `DO`, `LOAD DATA`, `HANDLER` and every future statement type. It also handles the dodges a naive keyword match falls for: `/*!50000 DROP */` (MySQL executes those), `SELECT 1; DROP TABLE t`, `WITH x AS (...) DELETE`, `EXPLAIN ANALYZE DELETE` (PostgreSQL executes it), and `#` — which is a comment in MySQL but the XOR operator in PostgreSQL, so treating it as a comment there would hide a write. On MySQL it additionally refuses `INTO OUTFILE`/`INTO DUMPFILE`/`FOR UPDATE`/`LOCK IN SHARE MODE`; on PostgreSQL, `SELECT ... INTO` (creates a table) and the `FOR ...` lock variants.
+
+Where the backend has a session setting, it is applied on **every new pooled connection**: `SET SESSION TRANSACTION READ ONLY` (MySQL) / `SET SESSION CHARACTERISTICS AS TRANSACTION READ ONLY` (PostgreSQL). That rail is enforced by the server, so it catches anything that slips past the statement guard (e.g. a stored procedure).
+
+**This is a guard rail, not a security boundary.** Both rails are escapable from the same session — a caller can run `SET SESSION TRANSACTION READ WRITE` and carry on, and any client-side check is pattern matching rather than a parser. The only hard boundary is the database account: use `GRANT SELECT ON db.* TO ...` for a database you genuinely must not write to, and treat everything above as defence in depth on top of it. SQLite has no session rail at all; for a file database the real boundary is the URL (`sqlite:///file:path?mode=ro&uri=true`). SSH workspaces ignore the flag — a remote shell is not a statement stream.
 
 ## Domain / table skills
 

{sql_harness-0.3.2 → sql_harness-0.3.4}/docs/AGENTS.md

@@ -12,10 +12,12 @@ Core code lives in `lab/sql_harness/src/sql_harness/`:
 - `config.py` — TOML schema + ConnectionConfig / ConnectionsConfig dataclasses
 - `paths.py` — XDG-style state directory resolution
 - `drivers/` — backend abstractions (postgres, mysql, redis stub, sqlite for tests)
+- `drivers/readonly.py` — read-only statement guard shared by the SQL drivers: comment/literal-stripping, allow-list verb check, and `install_guard()` which attaches both rails to an engine. Read its module docstring before relying on it — it is a guard rail, not a security boundary
 - `manager.py` — SqlHarness class: holds engines, workspaces, skills registry
 - `helpers.py` — heredoc helpers (auto-imported)
 - `agent_loader.py` — loads `$BH_SQL_AGENT_WORKSPACE/agent_helpers.py`
 - `analytics.py` — event bus (observer) + JSON stats + NDJSON execution log: CLI call counts, doc-read tracking, command/error history; `BH_SQL_ANALYTICS` (default ON), view with `sql-harness stats`
+- `output.py` — terminal output policy: UTF-8 stream setup, long-output spill to `$BH_SQL_HOME/tmp/output/`, concise error rendering; `BH_SQL_TRACEBACK=1` forces raw tracebacks
 - `run.py` — heredoc entry; delegates to CLI otherwise
 - `cli.py` — argparse subparser CLI (18 subcommands)
 

{sql_harness-0.3.2 → sql_harness-0.3.4}/docs/README.md

@@ -14,7 +14,7 @@ uv sync
 uv run sql-harness init
 
 # 3. Add a connection
-uv run sql-harness add local_pg --driver postgres --url 'postgresql://postgres:postgres@localhost:5432/postgres'
+uv run sql-harness add --name local_pg --driver postgres --url 'postgresql://postgres:postgres@localhost:5432/postgres'
 
 # 4. Test it
 uv run sql-harness test local_pg

{sql_harness-0.3.2 → sql_harness-0.3.4}/docs/connections-toml-example.toml

@@ -18,7 +18,9 @@ echo = false
 # Connections
 # ---------------------------------------------------------------------------
 # Each [[connections]] block defines a named profile. Drivers: postgres, mysql,
-# redis (stub), sqlite. URL must match the driver.
+# redis (stub), sqlite, ssh / ssh+password / ssh+key. URL must match the driver.
+# Optional keys: description, password, pool_size, pool_recycle, pre_ping, echo,
+# application_name. `${env:VAR}` is expanded in both `url` and `password`.
 
 [[connections]]
 name = "local_pg"
@@ -51,11 +53,24 @@ driver = "ssh"
 url = "ssh://app@10.0.0.5:2222"
 description = "Production application host (key auth via $BH_SSH_KEY or ~/.ssh/id_ed25519)"
 
+# Password auth, credentials kept out of the URL (recommended). Each connection
+# carries its own password, so switching workspaces needs no env fiddling.
+# Precedence: URL-embedded password > this field > $BH_SSH_PASSWORD.
+# Note: a connection with a password uses password auth exclusively — local
+# ~/.ssh keys are not consulted.
+[[connections]]
+name = "iot_server"
+driver = "ssh"
+url = "ssh://113.44.193.72:22"
+password = "${env:IOT_SSH_PASSWORD}"
+description = "IoT host (password auth)"
+
+# URL-embedded password also works (driver label may be ssh or ssh+password).
 [[connections]]
 name = "lab-server"
 driver = "ssh+password"
 url = "ssh+password://lab:lab@192.168.1.10:22"
-description = "Lab box (password auth)"
+description = "Lab box (password auth, password in URL)"
 
 # ---------------------------------------------------------------------------
 # Optional per-connection pool overrides (alternative syntax)

{sql_harness-0.3.2/skills/sql-harness/references → sql_harness-0.3.4/docs}/install.md

@@ -27,7 +27,8 @@ Writes `~/.config/sql-harness/connections.toml` (or `$BH_SQL_HOME/connections.to
 ## 3. Add your first connection
 
 ```bash
-uv run sql-harness add my_pg \
+uv run sql-harness add \
+    --name my_pg \
     --driver postgres \
     --url 'postgresql://user:pw@localhost:5432/db' \
     --description "My dev DB"
@@ -79,9 +80,21 @@ name = "prod_pg"
 driver = "postgres"
 url = "${env:PROD_PG_URL}"            # env-var indirection
 pool_size = 10
+
+[[connections]]
+name = "iot_server"
+driver = "ssh"
+url = "ssh://113.44.193.72:22"
+password = "${env:IOT_SSH_PASSWORD}"  # standalone secret — keeps the URL clean
 ```
 
-`${env:VAR}` placeholders inside `url` are expanded at load time from the process environment — keep prod secrets out of the file.
+`${env:VAR}` placeholders inside `url` and `password` are expanded at load time from the process environment — keep prod secrets out of the file.
+
+Optional per-connection keys: `description`, `password`, `read_only`, `pool_size`, `pool_recycle`, `pre_ping`, `echo`, `application_name`.
+
+`read_only = true` refuses writes on that connection — a statement allow-list on every statement the engine sends, plus the server-side session read-only setting where the backend has one. Use it for sensitive databases, but note it is a **guard rail, not a security boundary**: the session setting is escapable from the same session, and any client-side check is pattern matching. Pair it with a `SELECT`-only database account, which is the actual boundary. See `SKILL.md` → "Read-only connections".
+
+SSH password precedence (highest first): password embedded in `url` > the `password` key > `$BH_SSH_PASSWORD`. A connection that sets a password uses password auth exclusively — local `~/.ssh` keys are not consulted (see `interaction-skills/ssh/auth-and-tunnels.md`).
 
 ## Configuration env vars
 
@@ -110,7 +123,7 @@ pool_size = 10
 | `ssh` / `ssh+password` / `ssh+key` | remote shell + SFTP (paramiko) | `paramiko>=3.4` | ✅ |
 
 To enable Redis: `uv add "redis>=5.0,<6"` then implement `drivers/redis.py`.
-To add another SSH host: append a `[[connections]]` block with `driver = "ssh"` and an `ssh://...` URL.
+To add another SSH host: append a `[[connections]]` block with `driver = "ssh"` and an `ssh://...` URL. Use the `password` key for password auth, or `?key=/abs/path` for a key outside the default locations. `sql-harness test <name>` probes SSH with a remote `echo` instead of `SELECT 1`.
 
 ## Troubleshooting
 

{sql_harness-0.3.2 → sql_harness-0.3.4}/docs/maintainer.md

@@ -17,14 +17,26 @@ hand-synced copies. `pyproject.toml` `[tool.hatch.build.targets.wheel.force-incl
 maps the repo docs into the wheel:
 
 - `SKILL.md` → `sql_harness/_skills/SKILL.md`
+- `docs/install.md` → `sql_harness/_skills/install.md`
 - `interaction-skills` → `sql_harness/_skills/interaction-skills`
 - `agent-workspace/zones/meta/skills` → `sql_harness/_skills/zones-meta-skills`
 
 The root `SKILL.md` is the **single source of truth** (v0.3.0 consolidation —
 the old `skills/sql-harness/SKILL.md` and `src/sql_harness/SKILL.md` copies
-were removed). After editing it, just `uv build` again. `sql-harness skill`
-reads `sql_harness/_skills/SKILL.md` from the installed package and falls
-back to the repo-root `SKILL.md` in a source checkout.
+were removed; v0.3.4 removed the last hand-synced copy,
+`skills/sql-harness/references/install.md`). After editing it, just
+`uv build` again. `sql-harness skill` reads `sql_harness/_skills/SKILL.md`
+from the installed package and falls back to the repo-root `SKILL.md` in a
+source checkout.
+
+`SKILL.md` references `install.md` as a sibling file — that only resolves
+because `docs/install.md` is force-included into the bundle as
+`_skills/install.md`. Dropping it from the force-include list breaks the
+reference for every `skill install` user.
+
+`skill install` needs a real (non-editable) wheel install to work: it reads
+`sql_harness/_skills/`, which only exists after `uv build`. In a bare source
+checkout `_bundled_skills_root()` returns `None` and the command exits 2.
 
 ## Build outputs
 
@@ -44,7 +56,7 @@ The wheel contains the package modules + the `_skills/` doc bundle
 ```bash
 # standalone venv
 uv sync
-uv run pytest tests/unit -q    # 80 tests must pass
+uv run pytest tests/unit -q    # 133 tests must pass
 uv run sql-harness --help      # CLI works
 uv run sql-harness skill       # SKILL.md emit works
 ```

{sql_harness-0.3.2 → sql_harness-0.3.4}/interaction-skills/ssh/auth-and-tunnels.md

@@ -16,15 +16,29 @@
 
 ### 1.1 三种 scheme 对照
 
-`drivers/ssh.py:_parse_url` 支持的三种 URL 形式：
+`drivers/ssh.py` 认这三种 URL 形式：
 
-| URL 形式 | 何时用 | 取 key 顺序 |
+| URL 形式 | 何时用 | 认证方式 |
 |---|---|---|
-| `ssh://user@host:port` | 默认 key auth | `?key=...` → `$BH_SSH_KEY` → `~/.ssh/id_ed25519` → `id_rsa` → `id_ecdsa`（`KEY_FALLBACK`） |
-| `ssh+key://user@host:port?key=/abs/path` | key 不在默认路径 | URL 里的 `?key=` 单独覆盖 |
-| `ssh+password://user:pw@host:port` | 跳板 / 临时主机，没配 key | URL 嵌入密码；也可用 `$BH_SSH_PASSWORD` |
+| `ssh://user@host:port` | 默认 | 显式 key（`?key=`/`$BH_SSH_KEY`）→ key；否则配了密码 → 纯密码；都没有 → 自动找 `~/.ssh` key |
+| `ssh+key://user@host:port?key=/abs/path` | key 不在默认路径 | key 认证，密码作后备 |
+| `ssh+password://user[:pw]@host:port` | 跳板 / 临时主机 | 纯密码认证；密码可嵌 URL，也可放字段/env |
 
-**注意**：`ssh+password` 要求密码嵌入 URL。不想明文落 TOML，把密码放 `$BH_SSH_PASSWORD` 并用 `ssh://user@host`，但驱动**不会**自动回退到 env 密码（仅 key 走 env fallback）。这是常见混淆点。
+**密码来源优先级**（高 → 低）：URL 内嵌 > 连接里的 `password` 字段 > `$BH_SSH_PASSWORD`。
+
+**`password` 字段**（推荐——密码按连接存，切 workspace 不用动环境变量）：
+
+```toml
+[[connections]]
+name = "iot_server"
+driver = "ssh"
+url = "ssh://113.44.193.72:22"
+password = "${env:IOT_SSH_PASSWORD}"   # 也可直接写明文
+```
+
+**认证策略**（`_open_client`）：显式给 key（`?key=`/`$BH_SSH_KEY`）→ key 优先、密码兜底；没给 key 但配了密码 → **纯密码**，不翻 `~/.ssh`；都没有 → 自动发现 `~/.ssh/id_{ed25519,rsa,ecdsa}`。
+
+> 第三条很关键：paramiko 开着 `look_for_keys` 会逐个试 `~/.ssh` 里的 key，只要里面有一把解析不了的（旧 DSA key 是常见雷），认证线程直接抛异常、**在密码之前**就中断握手。所以配了密码就不会被本地散装 key 劫持。
 
 ### 1.2 用哪个连接串
 
@@ -32,7 +46,7 @@
 有 ed25519 key 在 ~/.ssh/ 且 authorized_keys 已加？
   ├─ 是 → ssh://user@host                                (默认 key path)
   └─ 否：
-      有密码但没 key？ → ssh+password://user:pw@host
+      有密码？ → 连接里加 password = "..."（driver 用 ssh 即可）
       key 在非默认路径？ → ssh://user@host?key=/path/to/k
       key 在 ssh-agent？ → §1.3
 ```
@@ -131,7 +145,8 @@ sql-harness 不内置 SSH SOCKS 代理；本机 `psql`/`TablePlus` 直连躲在
 ## Gotchas
 
 - **paramiko 不会自动用 ssh-agent**——见 §1.3。
-- **`ssh+password://` 必须嵌入密码**——`BH_SSH_PASSWORD` env 不会回退（仅 key 走 env fallback）。
+- **密码优先级**：URL 内嵌 > `password` 字段 > `$BH_SSH_PASSWORD`。配了密码即纯密码认证，本地 key 不再参与（见 §1.1）。
+- **服务端禁密码登录**：报 `Authentication failed` 时先确认服务端开了 `PasswordAuthentication`，别急着改本地配置。
 - **堡垒机转发时 `ssh -fN` 在某些堡垒机受限**——`AllowTcpForwarding no`。失败就 §2.2 走 paramiko `request_port_forward`。
 - **`request_port_forward` 返回的对象必须在 finally 里 cancel**，否则下次 `use_workspace` 复用 transport 报端口占用。
 - **workspace disconnect 不自动清 tunnel**——硬规矩：tunnel 用 try/finally 包起来。

{sql_harness-0.3.2 → sql_harness-0.3.4}/interaction-skills/transactions.md

@@ -55,3 +55,4 @@ for attempt in range(3):
 - `text("SELECT ...").execution_options(...)` is per-statement; transaction-level options belong on the `SET` line.
 - Nested `with_transaction()` will create a SAVEPOINT (PostgreSQL) or fail (MySQL). Don't nest.
 - A failed statement inside a transaction does NOT auto-rollback the whole transaction in some dialects — call `conn.rollback()` explicitly if you've swallowed the exception.
+- **A non-transactional table ignores `ROLLBACK` silently.** On MySQL, check `SELECT @@default_storage_engine` before trusting a rollback: if it is not InnoDB, any table created without an explicit `ENGINE=InnoDB` accepts `BEGIN`/`ROLLBACK` and discards them — the row is still there afterwards and nothing errors. Reach for `with_transaction()` on such tables and you get the *appearance* of atomicity with none of the substance.

{sql_harness-0.3.2 → sql_harness-0.3.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sql-harness"
-version = "0.3.2"
+version = "0.3.4"
 description = "Single-process SQL + SSH CLI for LLM agents. PostgreSQL/MySQL/SSH via SQLAlchemy + paramiko. Plaintext credentials in one TOML file. Helpers auto-injected into the heredoc namespace."
 readme = "docs/README.md"
 license = { text = "MIT" }
@@ -50,6 +50,7 @@ packages = ["src/sql_harness"]
 # shipping its SKILL.md in the wheel, but extended to the whole doc bundle.
 # Paths are relative to this pyproject.toml (lab/sql_harness/).
 "SKILL.md" = "sql_harness/_skills/SKILL.md"
+"docs/install.md" = "sql_harness/_skills/install.md"
 "interaction-skills" = "sql_harness/_skills/interaction-skills"
 "agent-workspace/zones/meta/skills" = "sql_harness/_skills/zones-meta-skills"
 

{sql_harness-0.3.2 → sql_harness-0.3.4}/sql-harness

@@ -16,7 +16,7 @@ set -euo pipefail
 # browser-harness keeps the launcher at repo root; sql-harness's "repo root" is lab/sql_harness/).
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 ROOT="$SCRIPT_DIR"
-SRC="$ROOT/src"r
+SRC="$ROOT/src"
 
 # Isolate dev state.
 export BH_SQL_HOME="$ROOT/.sql-harness-dev"

{sql_harness-0.3.2 → sql_harness-0.3.4}/src/sql_harness/analytics.py

@@ -48,8 +48,12 @@ CLI_INVOKED = "cli.invoked"  # payload: {"subcommand": str}
 DOC_READ = "doc.read"        # payload: {"doc": str, "via": str}
 COMMAND_EXECUTED = "command.executed"
 # payload: {"argv": list[str], "code": str|None, "ok": bool,
-#           "exit_code": int, "error": str|None}   (argv = CLI args incl. subcommand;
-#           code = heredoc body when run via stdin; error = message/traceback)
+#           "exit_code": int, "error": str|None}
+#   argv  = CLI args including the subcommand; [] in heredoc mode
+#   code  = the heredoc body; None in CLI mode
+#   error = the FULL traceback when the run died on an uncaught exception,
+#           else None. stderr shows a compressed form (see output.py), so this
+#           log is the only complete channel — it keeps everything.
 
 _OFF_VALUES = {"0", "off", "false", "no"}
 DOC_READS_CAP = 500