sid-harness 0.3.0__py3-none-any.whl

sid_harness-0.3.0.dist-info/METADATA

@@ -0,0 +1,229 @@
+Metadata-Version: 2.4
+Name: sid-harness
+Version: 0.3.0
+Summary: SID first-party local coding harness (CLI/TUI) — drives the SID native loop against SID's OpenAI-compatible /v1.
+License: Proprietary
+Project-URL: Homepage, https://superintelligencedog.com
+Project-URL: Documentation, https://superintelligencedog.com/docs
+Project-URL: Source, https://superintelligencedog.com
+Keywords: sid,coding-agent,cli,harness
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: OS Independent
+Classifier: Environment :: Console
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Provides-Extra: publish
+Requires-Dist: build>=1.2; extra == "publish"
+Requires-Dist: twine>=6.0; extra == "publish"
+Requires-Dist: sigstore>=3.0; extra == "publish"
+
+# sid-harness — SID first-party local coding client (v1)
+
+A small CLI/TUI client that runs a coding task through **SID's own native
+loop** against SID's OpenAI-compatible `/v1`. Running a model on your desktop no
+longer requires a third-party coding harness: SID *is* the harness.
+
+- **One engine.** The loop, its four-tool contract, and its path denylist are
+  the gateway's `app/native_agent.py`, vendored **verbatim** into the package as
+  `sid_harness/_native.py` — one loop, mirrored, and kept byte-identical by a
+  parity test. Never reimplemented.
+- **One backend.** SID routes, meters, and caps every call under **your** key.
+  No aggregator, no other provider SDK.
+- **One command.**
+
+```bash
+sid setup                              # verify your key via /v1/me, save it, pick a dir
+sid run --task "Fix the off-by-one in add()." --dir ./my-project
+```
+
+Output: the workspace selection, the model + diff, the final response, and a
+**run receipt** written to `<dir>/.sid/runs/<run_id>.json` (override with
+`--receipt`). The CLI prints the receipt as a `file://` link.
+
+## Install / run
+
+No third-party dependencies (stdlib only), and no monorepo checkout — the
+package is self-contained. Either:
+
+```bash
+pipx run --spec infra/sid-harness sid run --task "..." --dir ./proj   # install + run
+pipx install infra/sid-harness          # or install the `sid` console script
+pip install infra/sid-harness           # plain pip works too
+# or run straight from the tree:
+python -m sid_harness run --task "..." --dir ./proj
+```
+
+The loop ships in the package, so nothing under `infra/sid-gateway` is needed at
+runtime. The one optional seam that does use the gateway is `--context`
+(repo-scale retrieval over `app.rag`); it is discovered when a gateway checkout
+is present and overridable with `SID_HARNESS_GATEWAY_PATH`. Every other command
+works with no checkout.
+
+## First run
+
+`sid setup` verifies the key against `GET /v1/me`, then writes
+`~/.sid/config.json` (owner-only) with the key, base URL, and your default
+project directory. Later commands read that file when the env var or flag is
+absent, so `sid run --task "..."` works with no `export` and no `--dir`.
+Override the location with `SID_CONFIG_PATH`.
+
+```bash
+sid setup --dir ./my-project            # non-interactive: key from SID_API_KEY
+sid setup --api-key "<your-key>" --dir .  # or pass it explicitly
+```
+
+Maintainers publish the signed wheel with `scripts/publish_sid_harness.sh`
+(Sigstore attestations via `twine upload --attestations`). Public install
+commands are wired into the landing/docs pages only after the PyPI probe
+returns 200; the commands above remain the source-tree install until then.
+
+## Commands
+
+```bash
+sid run --task "<goal>" --dir <path> [--model auto] [--verify] [--write] [--json]
+sid run ... --git-write [--git-branch NAME] [--git-message MSG] [--no-pr]  # opt-in branch/commit/PR (SUB-95)
+sid run ... --context [--context-k N]  # prepend repo-scale retrieved context (SUB-55)
+sid run ... --mcp "<server cmd>"       # expose an MCP server's tools (SUB-56, repeatable)
+sid run ... --bounds-config <file>     # override loop bounds (SUB-58)
+sid run ... --test-cmd "python -m pytest -q"   # run the approved tests locally (SUB-80)
+sid tui  --dir <path>                  # interactive terminal loop, same engine
+sid status --dir <path> [--diff]       # local git/worktree status (read-only)
+sid session start|resume|replay        # durable local sessions (SUB-58)
+sid tools [--mcp "<server cmd>"] [--json]   # list the loop's tool contract
+sid policy --dir <path> [--json]       # show the platform worktree/gate policy
+sid lsp [--dir <path>]                 # LSP: compiler diagnostics -> loop (SUB-96)
+sid apply --dir <path> --receipt <p> [--approve]   # apply an approved run receipt
+sid editor install [--target-dir <p>] [--force]    # one-command VS Code install
+sid selftest [--receipt <path>]        # one loop turn against a local stub endpoint
+```
+
+Common options: `--base-url` (env `SID_BASE_URL`, default
+`https://superintelligencedog.com/v1`), `--api-key` (env `SID_API_KEY`),
+`--routing-profile` (default `agent`), `--criteria` / `--out-of-scope`
+(repeatable), `--max-tokens`, `--reasoning-effort`, `--receipt`, `--quiet`.
+
+`--verify` reviews the produced diff through the gateway's existing
+`POST /v1/verify/patch` — the harness does not carry a second verify path.
+
+`--write` applies the loop's changed files to the **real working tree**
+(SUB-54). It is off by default (read-only). Deletions are never applied. Inside
+the platform repo, a source write from the MAIN checkout is refused by the repo
+policy (SUB-57), which delegates to the platform's own Gate 31.
+
+`--git-write` is the explicit opt-in that finishes the coder loop (SUB-95):
+create a branch (`--git-branch`, default `sid/<run_id>`), commit **only** the
+files that `--write` applied, push that branch, and open a pull request with
+`gh` (`--git-base`, `--no-pr` to skip). Each step asks for its own approval;
+`--approve` pre-approves the steps for non-interactive use, and without a
+terminal or `--approve` every step fails closed. The path hard-refuses
+`main`/`master` (including sub-refs), never force-pushes, and the receipt's
+`git_write` block names the branch, commit SHA, and PR URL. Without
+`--git-write` the harness remains read-only and never commits or pushes.
+
+`--test-cmd` is the human-approved test command (SUB-80). The CLI splits it into
+an **argv list** and executes it with `subprocess` in the `--dir` root —
+never through a shell. The runner must be allowlisted (`python -m pytest`,
+`pytest`, `python -m unittest`, `npm test`, `yarn/pnpm test`, `cargo test`,
+`go test`), argv may not point outside the workspace, and the run is bounded
+(timeout + output capture). The receipt records `tests_executed`, the test
+backend, exit code, and pass/fail. Nothing is committed or pushed.
+
+## What v1 is (and is not)
+
+**Is:** a bounded workspace loaded from `--dir`, the existing native loop, SID as
+the only model backend, and a written run receipt. As of SUB-54 the workspace is
+a **local driver**: real file read/write (`--write`), real `git` **status/diff**
+(read-only — `sid status`), worktree awareness (linked worktree vs main
+checkout), and a `.gitignore` filter layered on the shared `native_agent._safe_path`
+secret/VCS/dependency denylist. The receipt records the git block and the files
+written.
+
+**Also wired (SUB-55/56/57/58):** repo-scale **context** (`--context` indexes the
+whole tree and prepends sanitized, data-boundaried retrieval — reuses the
+gateway's `app.rag`), the **tool ecosystem** (`sid_harness.tools`: a registry
+over the one loop, an MCP stdio/HTTP client, a skills loader, a plan/todo gate,
+subagent fan-out — reachable via `sid run --mcp` and `sid tools`), **durable
+sessions** (`sid session`), configurable **bounds** (`--bounds-config`), and
+**repo policy** (a write from the platform MAIN checkout is refused).
+
+**Tests (SUB-80):** with `--test-cmd`, the loop's `run_approved_tests` tool and
+the final verification step execute the approved argv locally against the
+workspace root; the receipt records backend/exit/passed and
+`tests_executed: true`. Without an approved command the receipt stays
+`tests_executed: false` — never a claim. By default the harness **never commits
+and never pushes**; only the explicit `--git-write` opt-in branches, commits,
+pushes a feature branch, and opens a PR (SUB-95), and it never touches
+main/master.
+
+## Localhost bridge (for the web Studio)
+
+The web Studio runs in a browser and cannot read your disk (Brave also blocks the
+File System Access API by default). Claude Code / Codex / OpenCode avoid this by
+running a local process with filesystem tools. The **desktop companion** is that
+local process for the Studio, and it removes the old URL/token paste:
+
+```bash
+# one click: starts the loopback bridge, then opens the Studio already paired
+python -m sid_harness companion --dir C:\Users\jerry\JB            # read-only
+python -m sid_harness companion --dir C:\Users\jerry\JB --write    # write available
+# the Studio shows "Enable write access" until the user explicitly grants it
+```
+
+The companion binds **127.0.0.1 only**, exchanges a per-launch pairing code (in
+the URL fragment, never a server log) for the bearer token, and accepts browser
+requests only from the SID origins. The workspace is fixed to `--dir`. The loop
+reads the **real tree on demand** (`list_files` / `read_file`), not a snapshot.
+
+Write mode is opt-in twice: `--write` makes it *available*, and the user then
+clicks **Enable write access** in the Studio (a per-session grant). Applying a
+change requires the exact proposal the bridge generated and the user reviewed:
+the digest is bound, every path goes through the shared secret/VCS denylist plus
+an atomic all-or-nothing write, and a receipt lands in
+`~/.sid/bridge/receipts/apply_*.json`. Endpoints: `GET /health`; `POST /pair`,
+`/grant-write`, `/revoke-write`, `/run` `{task, model?, test_argv?}` (with
+`X-SID-Api-Key`), and `/apply` `{proposal_id, digest}`. The browser cannot choose
+the model backend or run tests without the write grant.
+
+Installers (Windows/macOS/Linux, private venv + login autostart) and the
+sign/verify chain live in `install/`. `install/prove_brave_apply.py` drives the
+whole pair → grant → run → review → apply path in real Brave headless and checks
+the disk plus the receipt.
+
+The Studio ships the client half: a **Local bridge** control in the composer
+shows the paired workspace and read-only/write state; `pairFromLocation()` takes
+the companion's one-click code from the URL fragment, a Chat turn routes to
+`POST {url}/run`, and the receipt (model, tools, tests, diff, changed, final
+response) plus the real workspace preview render in place. **Enable write
+access** posts the explicit grant, and **Apply** posts the reviewed proposal id
+and digest. It fails closed and names the reason when the bridge is unreachable
+or the pairing is stale — there is no silent fallback to the remote gateway. The harness CLI (`sid run` /
+`sid tui`) remains the full-parity product (including `--write`); the Studio's
+bridge path is read-only.
+
+## Editor integration + LSP diagnostics (SUB-96)
+
+The VS Code extension under `editors/vscode` is a thin client over this same
+engine: **SID: Open Coding Session** runs `sid session start`, **Show Proposed
+Diff** opens the receipt's diff, **Approve and Apply** calls `sid apply` (the
+same `LocalWorkspace` + repo-policy write path), and **Attach Selection as
+Context** prepends the editor selection to the next task.
+
+```bash
+python -m sid_harness editor install      # one command; reload VS Code
+```
+
+`sid lsp` is the diagnostics server. It publishes real Python compiler
+diagnostics (`compile`) on open/change/save and accepts diagnostics forwarded
+from VS Code's other language servers through `sid/diagnostics`. The merged feed
+is written to `<workspace>/.sid/diagnostics.json`; `sid run` and `sid session`
+prepend a data-boundaried `COMPILER DIAGNOSTICS` block to the task and record
+`diagnostics: {count, sources, path}` on the receipt. `--no-diagnostics` opts
+out for one run. No model call, no tool contract, and no write path are added by
+the LSP — it is a diagnostic source for the one loop.
+
+## Scope guards
+- SID stays the only model backend (no aggregator).
+- No new pricing surface; your plan's unit is unchanged.
+- No reimplemented verify/scan — the harness calls the gateway's.
+- No vendor/model name is hardcoded into a rule, script default, or gate.

sid_harness-0.3.0.dist-info/RECORD

@@ -0,0 +1,45 @@
+sid_harness/__init__.py,sha256=FlZxkV9TKoN7s6DhHUfFTbBmKfDZCcqdYCiwBf0cKPY,567
+sid_harness/__main__.py,sha256=0iDYjdmiXNBinFF23WUyotsdpA6wFKjoB5aw3esTSRg,83
+sid_harness/_native.py,sha256=A77-vI0xreIKN_uZBi085DObrHyxKDDyTnus7newj8U,68450
+sid_harness/brave_proof.py,sha256=iCi62RkqdCTxJALhN9gtKhdg6OCNdDIc1Y_GjiPU_mA,9081
+sid_harness/bridge.py,sha256=PE1ooqyvGICjYZ5a67NSAkFhncL3rHh3YGOGs4WhW5g,34066
+sid_harness/cli.py,sha256=l1-WTcwwycJEUpC65o_oouJRauW-OYjv6WcooWnCiRg,36362
+sid_harness/client.py,sha256=Y80_4Vl82NtJhxGNILmm4PiVFm4Y4wJk9xE3P84c5mk,5816
+sid_harness/companion.py,sha256=G2G7UtrK72_L07J4CVZ8tMjIfuNb05bepYPU61kxUao,5698
+sid_harness/config.py,sha256=rNTEc6JysGFtVMfbSh8rZ4u8IXDg2se-5BscaHoMTrc,2064
+sid_harness/editor.py,sha256=0TJs1puEju7IDdvAs52QQhY3M752Ebp5fREIbK798QE,8952
+sid_harness/gateway.py,sha256=FQbkVK6SK4BFdvIlWZkiHllkzayVZuOe08iHa4SlR18,3535
+sid_harness/git_write.py,sha256=RAvmvtz1Clx7S4Rf2AoVNyNQ2LDFX8wJq34SUhOrQsY,19720
+sid_harness/local_workspace.py,sha256=oJegI9wg2uDl_buiiPFiD0V6bkExiABIzwtpH6g2o0M,15574
+sid_harness/loop.py,sha256=RbLVTcLCY4gi7sJW1sH3gY9AoNSxhoAqnEWa9wq2-O0,14264
+sid_harness/lsp.py,sha256=N6XaSVpjumzfowzKL9_8aoTWgV26ovp8MGTPSM-uPG8,22056
+sid_harness/receipt.py,sha256=mV9pkex75jIGVgmvB_UpNjd8bQoyyyvPXQI-4ZyciLs,4899
+sid_harness/runner.py,sha256=wbtgq-nO2-_bhzfNo96ADPiKq4LENn-rbhjKdersibY,17801
+sid_harness/selftest.py,sha256=nJmAXgbHtM3TMQopVV6SJOOf4XB2L8e1wY31vFj2jrk,5607
+sid_harness/tui.py,sha256=RN0-uepRr7dV7uY3HEK1Z1U6PrEWkuKLqmM-Bm9ZJHs,3840
+sid_harness/workspace.py,sha256=Ck4DWzie27lDJIWwCfSIRCym5IORU95lKxtA2wj5JCQ,3904
+sid_harness/context/__init__.py,sha256=dA2CZv300FFz-_C-r_rFWGyjH6zMEMkESqOML6d7GYk,1269
+sid_harness/context/index.py,sha256=NSJrVHoNEmydWe2r_e3LwuLqCP-cLC7DX74rfO8qy7Y,8473
+sid_harness/context/retrieval.py,sha256=GnZdwk8lu9Ocr4jPj24ysrel1SDFUGOIbjVcwqFt1BI,2674
+sid_harness/policy/__init__.py,sha256=MzKWyCkW48d7-eVbT71dDO0A9TE0SaY7uHEYdO8Kf18,1071
+sid_harness/policy/repo_policy.py,sha256=zhZKE6SYRqm1iQY0XLEZ9--Y7pFWi4z336vE90CdlqM,23556
+sid_harness/session/__init__.py,sha256=3mdbZ3U2EwnrBJ92mJUSL8sUopgvFZ6GY3KWl2EB2os,1118
+sid_harness/session/bounds.py,sha256=gfbR2UbJFaaSH9vuKltAArYF4bM9CBzA0j2RC0U4wgE,5064
+sid_harness/session/diff_gate.py,sha256=hVD1VaVjIa2Wudmb1DyjD4Ai0GfC1ckf9GhvocPLVWg,2990
+sid_harness/session/session.py,sha256=a4EmD9bQMfJYfCj-5yubZyETJZesqQv8l7q6A5p09zs,16541
+sid_harness/session/store.py,sha256=GbVDuSJ95lu2Vq3KT5BCg1DB9UcY1yo_fKiOhKN4Gfc,3426
+sid_harness/tools/__init__.py,sha256=a7mYMqt7QuQQWKFe_PQ9oA7Hmm3nZ-FDs22qoARYzEQ,1355
+sid_harness/tools/mcp_client.py,sha256=nvrKxsbfe-c_7DLwzYBJ7SJmkoZOZuPBR--3WWoW9Gs,9897
+sid_harness/tools/plan.py,sha256=L7iXbLZrGSuQx4IpzFbM3LFGIuO_tH7DEs9xfgmywso,4595
+sid_harness/tools/registry.py,sha256=kN6YO4xOOEbbQScd9icjdixDH6q4ie7wtK2UjmbSxdY,5527
+sid_harness/tools/skills.py,sha256=7u6RBvOO364h-DxHGngZBrRWpz6z7_O8hqNN7jre0zE,6054
+sid_harness/tools/subagents.py,sha256=K7unNx69-yOGnMUVWa-M8mXyIPYiRoKMSzcy9C0x2Pw,3730
+sid_harness-0.3.0.data/data/share/sid-harness/editors/README.md,sha256=QBjhYFY7K3XZNTXjuFamHwdFRfT1IB2paVpSJWBEuUk,1924
+sid_harness-0.3.0.data/data/share/sid-harness/editors/vscode/README.md,sha256=pfYgIM2bYhFzJ9uY8gu00aMA8zJMYGDm872WAaWoP1Q,1157
+sid_harness-0.3.0.data/data/share/sid-harness/editors/vscode/extension.js,sha256=p9Liief0ClCLvrusHe7iEBGrx-CeNHVzaZiCQkNM-MY,13062
+sid_harness-0.3.0.data/data/share/sid-harness/editors/vscode/package.json,sha256=avz5s3B4O8ZStzfmtlkb1aCXBR7LEWc21Kmi25px-iI,3257
+sid_harness-0.3.0.dist-info/METADATA,sha256=li4Nfu5fNYe7Y7lWi_MPSKB09xZVrxTXde5TZLc4Zrc,12604
+sid_harness-0.3.0.dist-info/WHEEL,sha256=mOdXR9C3wMVov7cSY8PY-XCzo3SmmWCHvGQr5csJoao,91
+sid_harness-0.3.0.dist-info/entry_points.txt,sha256=om_58K5b0llEOc8JbfNkK2a7eOlqtT6M7_WzSiWosJg,45
+sid_harness-0.3.0.dist-info/top_level.txt,sha256=vOs5L6R4jm8sy8EXZrWCkBpWZxYaGUx5JmXj6gstfnM,12
+sid_harness-0.3.0.dist-info/RECORD,,

sid_harness-0.3.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.2.1)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

sid_harness-0.3.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+sid = sid_harness.cli:main

sid_harness-0.3.0.dist-info/top_level.txt

@@ -0,0 +1 @@
+sid_harness