terse-mcp 0.3.1__tar.gz

terse_mcp-0.3.1/.github/workflows/release.yml

@@ -0,0 +1,71 @@
+name: release
+# Fires when a version tag is pushed (e.g. `v0.1.0`). Builds the sdist+wheel, cuts a
+# GitHub Release, and publishes to PyPI via Trusted Publishing (OIDC — no stored token).
+# The tag IS the version (hatch-vcs) — a build here resolves to the tag, byte-for-byte.
+#
+# The distribution name is `terse-mcp` (the bare `terse` is taken on PyPI); it normalizes
+# to `terse_mcp` in wheel filenames (e.g. v0.3.0 -> terse_mcp-0.3.0-*.whl).
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions: {} # least privilege — each job opts into exactly what it needs
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write # create the GitHub Release + upload artifacts; nothing more
+    steps:
+      # fetch-depth: 0 is REQUIRED — hatch-vcs derives the version from `git describe`,
+      # which needs full history + the tag. A shallow checkout yields a wrong/dev version.
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@e58605a9b6da7c637471fab8847a5e5a6b8df081 # v5
+        with:
+          enable-cache: true
+      - name: Build sdist + wheel
+        run: uv build
+      - name: Sanity-check the built version matches the tag
+        # Fail loudly if hatch-vcs and the tag disagree — the artifact name must contain
+        # the tag without its leading `v`.
+        run: |
+          expected="${GITHUB_REF_NAME#v}"
+          if ! ls dist/terse_mcp-"${expected}"-*.whl >/dev/null 2>&1; then
+            echo "::error::built wheel does not match tag ${GITHUB_REF_NAME} (expected version ${expected})"; ls -1 dist/; exit 1
+          fi
+          echo "built version ${expected} matches tag ${GITHUB_REF_NAME}"
+      # Build ONCE — the same artifacts go to both the GitHub Release and PyPI.
+      - name: Upload dist for the publish job
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+      - name: Publish GitHub Release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release create "${GITHUB_REF_NAME}" dist/* --generate-notes --title "${GITHUB_REF_NAME}"
+
+  pypi-publish:
+    needs: release
+    runs-on: ubuntu-latest
+    # `pypi` MUST match the Trusted Publisher's environment on PyPI, or the OIDC exchange is
+    # rejected. Gate it with a required reviewer in Settings -> Environments for human approval.
+    environment:
+      name: pypi
+      url: https://pypi.org/project/terse-mcp/
+    permissions:
+      id-token: write # OIDC is the ONLY credential — no PyPI token is stored anywhere
+    steps:
+      - name: Download the built dist
+        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: dist
+          path: dist/
+      # Trusted Publishing is automatic (no `with:` creds); PEP 740 attestations default on;
+      # uploads everything in dist/ (packages-dir defaults to dist/).
+      - name: Publish to PyPI (Trusted Publishing + attestations)
+        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0

terse_mcp-0.3.1/.github/workflows/tests.yml

@@ -0,0 +1,42 @@
+name: tests
+on:
+  push:
+    branches: [main]
+  pull_request:
+permissions:
+  contents: read          # least privilege — the workflow only reads the repo
+jobs:
+  lint:
+    # Deterministic and version-independent — its own job so a lint failure reports as
+    # one named check, not 3 identical red X's under the pytest matrix.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        with:
+          fetch-depth: 0        # hatch-vcs derives the version from git history + tags
+      - uses: astral-sh/setup-uv@e58605a9b6da7c637471fab8847a5e5a6b8df081 # v5
+        with:
+          enable-cache: true
+      - run: uv sync --dev          # no anthropic extra: keeps CI keyless, matches design
+      - run: uv run ruff check .
+      - run: uv run mypy            # checked annotations (audit fix #1); config in pyproject
+  pytest:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # Floor (the requires-python promise) through current stable. Test both ends so
+        # a ">=3.11" claim is actually verified, not just the dev default. 3.14 is left
+        # off until tiktoken ships wheels for it (else CI compiles the Rust ext + fails).
+        python-version: ["3.11", "3.12", "3.13"]
+    env:
+      UV_PYTHON: ${{ matrix.python-version }}
+    steps:
+      - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
+        with:
+          fetch-depth: 0        # hatch-vcs derives the version from git history + tags
+      - uses: astral-sh/setup-uv@e58605a9b6da7c637471fab8847a5e5a6b8df081 # v5
+        with:
+          enable-cache: true
+      - run: uv sync --dev          # no anthropic extra: keeps CI keyless, matches design
+      - run: uv run pytest -q

terse_mcp-0.3.1/.gitignore

@@ -0,0 +1,38 @@
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+*.egg-info/
+.pytest_cache/
+
+# uv
+# uv.lock IS committed (pinned deps) — do not ignore it.
+
+# Captured corpus payloads may contain tool output; keep the dir, ignore contents.
+corpus/*
+!corpus/.gitkeep
+
+# Synthetic stress corpus for the fluency eval — derived; regenerate with
+# `python scripts/gen_stress_corpus.py`.
+corpus-stress/
+
+# Ad-hoc eval corpora for cross-call diffing (synthetic pair + real gh captures) — derived.
+corpus-diff/
+corpus-real/
+
+# Spike reports
+reports/
+
+# runecho stray index dirs (created if `runecho-ir` is run with cwd here)
+.ai/
+
+# Ad-hoc experiment harnesses (e.g. the fidelity probe) — not part of the lib
+scratch_fidelity/
+.codegraph
+.coverage
+
+# hatch-vcs build-time version file (generated from the git tag; never committed)
+src/terse/_version.py
+
+# Benchmark: pinned TOON encoder deps (regenerate with `cd scripts/bench && npm install`)
+scripts/bench/node_modules/

terse_mcp-0.3.1/.gitleaksignore

@@ -0,0 +1,2 @@
+# False positives only — verify before adding (fake test fixture data, not a real secret).
+tests/test_cli.py:generic-api-key:193

terse_mcp-0.3.1/.runechoguardignore

@@ -0,0 +1,106 @@
+# Symbols the guard mis-flags as unresolved. The guard parses `from X import Y`
+# only within a staged diff hunk, so a new line using a stdlib symbol whose import
+# line isn't also in the hunk gets a false positive. A genuinely missing import of
+# these is caught immediately by pytest/import, so suppressing them here is safe.
+Path
+OrderedDict
+Lock
+Counter
+Thread
+field
+dataclass
+# Also mis-flagged: a callback PARAMETER invoked as a bare call (`drop_sink(h, v)` in
+# policy.apply). The guard resolves module symbols/imports, not function parameters, so a
+# param called by name reads as unresolved. A genuinely wrong name is caught by pytest.
+drop_sink
+answerer
+rule_for
+# cli.py's _build_answerers(args, make_openai, make_anthropic, ...) — the two answerer-
+# factory PARAMETERS, called bare (make_openai(base, key, m) / make_anthropic(model)).
+# Same false-positive class as drop_sink/answerer/rule_for above.
+make_openai
+make_anthropic
+# fluency.py's _aggregate_by_model(pairs, answerers, trials, payload_fn) — the eval
+# PARAMETER (run_diff_payload/run_text_diff_payload), called bare as payload_fn(a, b,
+# fn, tool, trials=trials). Same false-positive class as drop_sink/answerer above.
+payload_fn
+# Also mis-flagged: a local variable holding a function REFERENCE, called bare in a
+# monkeypatch wrapper (`real = mod.fn; def wrapper(*a): return real(*a)`), same
+# root cause as the callback-parameter case above — the guard resolves module
+# symbols/imports, not locals. Confirmed correct: pytest passes with these wrappers.
+real_apply
+real
+orig_send
+# test_run_text_diff_payload_computes_wire_exactly_once's `original = fluency.text_diff.
+# text_diff_wire`, called bare inside its counting_wire wrapper. Same class as real/
+# orig_send above.
+original
+# Also mis-flagged: plain English words inside a docstring that happen to look like
+# `word(...)` bare calls to the guard's pattern match (e.g. "the client's stdin",
+# "server->client", "closes the transport in turn"). Not code at all.
+client
+wire
+cleanly
+server
+args
+keys
+measurement
+one
+unconditionally
+flight
+rows
+inner
+built
+wide
+name
+callers
+detail
+scope
+scopes
+implicitly
+# report.py's _build_diff_style_report docstring: "pre-split into lines (not a single
+# string)" — "lines (not" reads as a bare call. Not code.
+lines
+# fluency.py's run_text_diff_payload docstring: "computes the diff wire exactly ONCE
+# (unlike calling gen_text_diff_questions..." — "ONCE (unlike" reads as a bare call.
+ONCE
+# Also mis-flagged: importlib.metadata.version, imported locally inside
+# _attestation_card (html_report.py) the same way report.py's build_verify_header
+# already does — same hunk-splitting false positive as the stdlib symbols above.
+# Confirmed resolving correctly: `terse verify --html` prints the real version.
+version
+# probes.py / cli.py #64 cross-server probe: hunk-split import + same-file false
+# positives — the guard parses `from X import Y` only within the staged hunk and does not
+# resolve same-file top-level defs (e.g. value_redundancy called inside cross_server_*).
+# All confirmed defined/imported; a genuinely missing one is caught by pytest/import.
+combinations
+extract_records
+encode_cl100k
+value_redundancy
+DEFAULT_PROBE_REPORT
+# probes.py cross_call_overlap docstring: "When `idf` is supplied (from `token_idf`)" —
+# "supplied (from" reads as a bare call to the guard's pattern match. Not code.
+supplied
+# proxy.py _emit_audit: `audit = self.audit` narrowed local (mypy baseline, audit
+# fix #1), called bare — same local-variable false-positive class as real/orig_send.
+audit
+# test_codec_hotpath.py's counting wrapper: `real_minify = transforms.minify`, called
+# bare inside the monkeypatch lambda. Same local-variable class as real/orig_send.
+real_minify
+# proxy.py run_proxy docstring (stats ledger): "record per result (sizes + decision"
+# and "ON by default (cli.py resolves" — English words reading as bare calls. Not code.
+result
+default
+# test_stats.py locals holding build_stats_writer's returned closure, called bare
+# (writer(...) / quiet(...) / loud(...)). Same local-variable class as real/orig_send.
+writer
+quiet
+loud
+# policy.py select / proxy.py run_proxy docstrings (#83): English prose the guard's
+# pattern match reads as bare calls — "when `server` is known (#83)", "self-prefix
+# their own tool names (kb names ...)", "a server-scoped rule (`runecho.*`)", "the
+# command basename (kb behind ...)". Not code.
+known
+names
+rule
+basename

terse_mcp-0.3.1/BENCHMARKS.md

@@ -0,0 +1,151 @@
+# terse — Benchmarks
+
+**Last updated: 2026-07-17.** All figures below were produced on that date and are
+**reproducible end-to-end** with the commands shown — nothing here is hand-typed or
+estimated. If you re-run and get different numbers, the code changed; open an issue.
+
+## What is being measured
+
+- **Token reduction** = how many fewer tokens the compressed form costs vs the raw JSON,
+  counted in **`cl100k_base`** (the tiktoken vocabulary terse uses). Higher is better.
+  A payload that is *already* compact (no pretty-print whitespace) makes every number here
+  a *pure structural* gain — the hardest honest case.
+- **Lossless** = `decompress(compress(x)) == x` exactly. Every terse row below is verified
+  lossless per payload; a payload is dropped from a total if either tool fails its round-trip.
+- "raw", "terse", "TOON" columns are % fewer tokens than the raw JSON.
+
+## Reproduce everything
+
+```bash
+uv sync
+cd scripts/bench && npm install          # pins the official @toon-format/toon encoder
+cd -
+uv run scripts/bench/benchmark.py        # §1  terse vs TOON on real GitHub API payloads
+uv run scripts/bench/width_sweep.py      # §2  the column-width sweep
+uv run scripts/bench/diff_demo.py        # §3  cross-call diff (terse's own axis)
+```
+
+---
+
+## §1 — terse vs TOON on real, public GitHub API payloads
+
+The corpus is real GitHub API output (`scripts/bench/corpus/`) — the nested, record-shaped
+tool traffic terse targets. `cl100k` tokens, all lossless.
+
+| payload | records | raw tok | **terse** | TOON |
+|---|--:|--:|--:|--:|
+| gh_pulls | 30 | 151,165 | **76.1%** | −8.4% |
+| gh_workflow_runs | 20 | 76,032 | **80.3%** | −7.5% |
+| gh_issues | 30 | 48,032 | **32.7%** | −8.0% |
+| gh_commits | 30 | 69,652 | **26.5%** | −4.5% |
+| gh_dir_listing | 24 | 6,736 | **31.4%** | −7.7% |
+| gh_rate_limit | 1 obj | 357 | **13.4%** | −36.7% |
+| gh_repo_single | 1 obj | 1,652 | 0.0% | −4.4% |
+| gh_commits_flat | 30 | 10,886 | **2.4%** | 1.7% |
+| gh_labels | 9 | 632 | 15.2% | **19.0%** |
+| **weighted total** | | **365,144** | **58.3%** | **−7.1%** |
+
+**Plain reading:** on real nested records terse cuts tokens **58%**; TOON *regresses* to −7%
+(worse than raw) because it adds a key-path per nesting level, while terse folds the repeated
+subtrees and long repeated strings (e.g. `gh_pulls` = 60 copies of the same repo object
+collapsed to one legend entry → 76%). TOON wins only on `gh_labels` — a flat, short-valued
+uniform table, its designed sweet spot.
+
+---
+
+## §2 — Column-width sweep: is there a "narrow vs wide" crossover? (No.)
+
+A natural hypothesis is that TOON overtakes terse once records get *wide* (many columns),
+because TOON writes the header once per table. We tested it directly: **40 rows held fixed,
+column count swept 2→12**, seeded, each row verified lossless for both tools.
+
+| columns | terse% | TOON% | winner |
+|--:|--:|--:|--:|
+| 2 | 40.4 | 44.0 | TOON +3.6 |
+| 3 | 52.1 | 48.7 | terse +3.4 |
+| 4 | 46.8 | 48.8 | TOON +2.0 |
+| 5 | 52.6 | 50.7 | terse +1.9 |
+| 6 | 48.9 | 50.5 | TOON +1.6 |
+| 7 | 52.7 | 51.5 | terse +1.2 |
+| 8 | 50.0 | 51.2 | TOON +1.2 |
+| 9 | 52.9 | 52.1 | terse +0.8 |
+| 10 | 50.6 | 51.7 | TOON +1.1 |
+| 11 | 52.9 | 52.3 | terse +0.6 |
+| 12 | 51.1 | 52.1 | TOON +1.0 |
+
+**Plain reading:** there is **no clean column-count crossover.** The winner oscillates by
+parity, the margins are ~1–4 points, and they **converge toward a tie** as width grows — the
+opposite of "TOON pulls decisively ahead when wide." (An earlier draft of this repo's README
+claimed a ≤3/≥4-column boundary from a single synthetic construction; a seeded sweep does not
+reproduce it, and the claim was corrected.)
+
+**The real dividing axis is value repetition, not width.** On these stripped-flat synthetic
+tables — no nesting, no long repeated strings — terse's dictionary/subtree tiers have little
+to fold, so the two tools tie. terse's decisive §1 win comes precisely from the redundancy
+that real records have and synthetic flat tables don't.
+
+---
+
+## §3 — Cross-call diff (an axis no stateless encoder has)
+
+When the same tool is called again (poll a list, re-read a file), terse can emit a lossless
+*delta* against the prior result instead of the whole payload. TOON, minify, and terse's own
+single-shot codec all pay the full column every call. Modeling one repeat call per payload
+(`diff_demo.py`), the **second** call costs:
+
+| repeated call | full re-send | diff | smaller by |
+|---|--:|--:|--:|
+| gh_commits_flat | 10,681 | 812 | **92.4%** |
+| gh_issues | 32,608 | 4,448 | **86.4%** |
+| gh_pulls | 37,776 | 15,292 | **59.5%** |
+| **weighted total** | 152,837 | 40,138 | **73.7%** |
+
+**Honest caveat (read this):** these are *modeled* repeat-call savings. How *often* the
+pattern occurs in a real agent loop is workload-dependent and is being measured directly (the
+proxy now records a per-result `diff_reason` — run `terse stats` to see the breakdown for your
+own traffic). Do **not** read §3 as a claim about aggregate real-world savings; read §1 for that.
+
+---
+
+## §4 — Competitor landscape (hands-on, tested 2026-07-17)
+
+Installed and tested, not cited from marketing. Only TOON (§1) is directly comparable on a
+lossless token axis; the rest measure *different guarantees*, so no head-to-head % is claimed.
+
+| Tool | What it is (verified) | Comparable? |
+|---|---|---|
+| **headroom** (`headroom-ai`, v0.32.0) | JSON compressor is a **deterministic Rust transform, not ML**: lossless on uniform arrays, but **drops rows** on larger/irregular sets, recoverable only via a `retrieve` round-trip against a **time-boxed cache** (default 30-min TTL). Measured on our corpus: 33.1% (lossless reformat) to 42.5%/64.1% (lossy, dropping 13/30 and 13/20 rows). A separate optional text compressor *is* ML. | No — its larger numbers come from *dropping data* with time-limited recovery; terse's are unconditionally lossless. |
+| **LLMLingua-2** (Microsoft) | Lossy prompt token-classifier. Fed JSON it strips syntax (`{`,`}`,`:`,`"`) as low-information and emits **invalid, unparseable JSON**; truncates past 512 tokens. ~50% on both prose and JSON. | No — different axis (prompts, not tool output), lossy, corrupts structure. |
+| **Atlassian mcp-compressor** | Primarily lossless schema/description compression at connect time — **complementary and stackable** with terse (`terse proxy -- mcp-compressor -- <server>`). An opt-in `--toonify` flag also reformats results into TOON (off by default; no diffing/policy/state). | Adjacent, not competing. |
+| **Anthropic / OpenAI context editing** | Native, server-side, **lossy** history-pruning; no local artifact to run keylessly. | Different mechanism (drops old results server-side). |
+
+---
+
+## §5 — Generate your own real-session evidence
+
+The benchmarks above are a fixed corpus. terse also keeps an always-on, **payload-free**
+savings ledger from your real sessions (sizes + decisions only, never content), so you can
+measure what terse saved *you*, not a synthetic corpus:
+
+```bash
+terse stats                 # rollup: results, decisions, tokens saved, per-tool rows
+terse stats --since 7d      # windowed
+```
+
+This is terse's "evidence over stars" path: your own numbers, on your own traffic, verifiable
+without trusting this file.
+
+---
+
+## Methodology & honesty notes
+
+- Tokenizer is `cl100k_base`; absolute % shift under a different vocabulary but the ranking is
+  stable (terse's cross-tokenizer-invariance claim, tested separately in the suite).
+- §1 corpus is real, public GitHub API output. §2 is **synthetic and seeded** — illustrative
+  of a mechanism, not production-representative; the exact numbers depend on the construction
+  (short keys, value cardinality), which is why §2's takeaway is "no crossover," not a constant.
+- Every terse figure is verified lossless per payload. §4's headroom row is the only place a
+  "reduction %" is reported for a tool that achieves it by *discarding* data — flagged inline.
+- Adoption honesty: terse is new (pre-PyPI as of this date); TOON and headroom are far more
+  established. terse's wedge is narrow and specific — *unconditionally lossless, no ML, no
+  egress* — not breadth of adoption.

terse_mcp-0.3.1/CHANGELOG.md

@@ -0,0 +1,58 @@
+# Changelog
+
+All notable changes to terse are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+Releases are cut from git tags (`vX.Y.Z`, via hatch-vcs) — an entry moves from
+`[Unreleased]` to a versioned section when its tag is pushed.
+
+## [Unreleased]
+
+## [0.3.1] - 2026-07-18
+
+### Added
+- Automated PyPI publishing via GitHub Actions **Trusted Publishing** (OIDC) with
+  PEP 740 provenance attestations — tagged releases upload to PyPI with no stored
+  token. This is the first PyPI release of `terse-mcp`. (#111)
+
+### Fixed
+- `release` workflow: corrected the built-wheel name check for the `terse-mcp`
+  rename (`terse_mcp-*.whl`), which had blocked the tagged release run. (#110)
+
+## [0.3.0] - 2026-07-18
+
+### Added
+- **Installable package** — MIT license and PyPI-ready metadata. The distribution is
+  named `terse-mcp` (the bare `terse` is taken on PyPI); the import package stays
+  `terse`, so `python -m terse` is unchanged. (#103)
+- `verify --json`: emit the lossless-gate verdict and cl100k savings totals as JSON
+  on stdout instead of the markdown report — CI-checkable (`… | jq -e
+  .lossless_gate.ok`), parity with `stats --json` / `mcp-status --json`. (#107)
+- diff-moat instrumentation: `stats` records why the cross-call diff tier did or did
+  not fire per call, to measure the diff feature's real-world reach (Phase 0+1). (#101)
+- Property-based fuzzing of the lossless round-trip guarantee. (#105)
+
+### Documentation
+- Onboarding quickstart + per-client install recipes. (#108)
+- Codeshot architecture diagram embedded in TECHNICAL.md. (#104)
+
+## [0.2.0] - 2026-07-17
+
+### Added
+- `mcp-status`: each wrapped server now shows what it actually fronts
+  (`wraps=<downstream cmd/url>`), whether the cross-call diff tier is
+  on/off/default, and whether the stats ledger is on; a policy file that has gone
+  missing since install is flagged `(MISSING)`; new `--json` output for
+  scripts/CI. (#97)
+- `tune`: each drop-candidate bucket ends with a savings rollup — estimated gross
+  tokens the whole bucket would evict and its share of the corpus. (#98)
+- `fluency --html`: writes the forest-plot comprehension-gap report next to
+  `--out` for the paired diff-family evals (`--diff`, `--diff-soak`,
+  `--text-diff-eval`); same inline-SVG/no-JS/no-CDN form as `measure --html`. (#99)
+
+### Fixed
+- `stats`: the per-tool table falls back to character columns when tiktoken token
+  counts are absent (was rendering as all-zeros); an empty `--since` window now
+  reports the window rather than "nothing ever recorded"; added a per-tool
+  cross-call diff hit-rate (`diff%`) column. (#96)

terse_mcp-0.3.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Eric Minish
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.