pmquant 0.4.3__tar.gz → 0.4.4__tar.gz

pmquant-0.4.4/.githooks/pre-push

@@ -0,0 +1,10 @@
+#!/bin/sh
+# pmq pre-push guard: refuse to push red. CI is the backstop; this catches
+# it before the remote does. Bypass knowingly with --no-verify.
+set -e
+cd "$(git rev-parse --show-toplevel)"
+PY=./.venv/bin/python
+[ -x "$PY" ] || PY=python3
+$PY -m ruff check . || { echo "pre-push: ruff rouge"; exit 1; }
+$PY -m mypy || { echo "pre-push: mypy rouge"; exit 1; }
+$PY -m pytest -q || { echo "pre-push: tests rouges"; exit 1; }

pmquant-0.4.4/.github/workflows/codeql.yml

@@ -0,0 +1,21 @@
+name: codeql
+on:
+  push:
+    branches: [main]
+  pull_request:
+  schedule:
+    - cron: "41 7 * * 1"
+
+permissions: read-all
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - uses: github/codeql-action/init@54f647b7e1bb85c95cddabcd46b0c578ec92bc1a # v4
+        with:
+          languages: python
+      - uses: github/codeql-action/analyze@54f647b7e1bb85c95cddabcd46b0c578ec92bc1a # v4

pmquant-0.4.4/.github/workflows/mcp-publish.yml

@@ -0,0 +1,35 @@
+name: mcp-publish
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  id-token: write              # OIDC login to the MCP registry
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+      - name: Fetch mcp-publisher
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release download --repo modelcontextprotocol/registry \
+            --pattern "mcp-publisher_*linux_amd64.tar.gz" --output mp.tgz
+          tar -xzf mp.tgz
+          ./mcp-publisher --version
+      - name: Wait for the version to exist on PyPI
+        run: |
+          V=$(python3 -c "import json; print(json.load(open('server.json'))['version'])")
+          for i in $(seq 1 20); do
+            curl -s "https://pypi.org/pypi/pmquant/$V/json" | grep -q '"version"' && exit 0
+            echo "PyPI does not serve $V yet ($i/20)"; sleep 30
+          done
+          echo "giving up: registry would reject an unpublished version"; exit 1
+      - name: Publish server.json to the MCP registry
+        run: |
+          ./mcp-publisher login github-oidc
+          ./mcp-publisher publish

{pmquant-0.4.3 → pmquant-0.4.4}/.github/workflows/publish.yml

@@ -5,6 +5,9 @@ on:
     types: [published]
   workflow_dispatch:
 
+permissions:
+  contents: read
+
 jobs:
   publish:
     runs-on: ubuntu-latest

pmquant-0.4.3/.hypothesis/constants/1720e64af9235558 → pmquant-0.4.4/.hypothesis/constants/3687cdf4cf8f7af3

@@ -1,4 +1,4 @@
 # file: /home/runner/work/pmq/pmq/src/pmq/__init__.py
 # hypothesis_version: 6.156.1
 
-['0.4.3', 'DEFAULT_BUILDER_CODE', 'FEE_RATES', 'Fill', 'OrderUncertain', 'PmqError', 'PolymarketExecutor', '__version__', 'band_ask_depth_usd', 'best_bid_ask', 'book_inferred_winner', 'book_meta', 'event_markets', 'fee', 'get_book', 'get_market', 'get_tape', 'http_get_json', 'parse_market', 'positions', 'resolved_winner']
+['0.4.4', 'DEFAULT_BUILDER_CODE', 'FEE_RATES', 'Fill', 'OrderUncertain', 'PmqError', 'PolymarketExecutor', '__version__', 'band_ask_depth_usd', 'best_bid_ask', 'book_inferred_winner', 'book_meta', 'event_markets', 'fee', 'get_book', 'get_market', 'get_tape', 'http_get_json', 'parse_market', 'positions', 'resolved_winner']

{pmquant-0.4.3 → pmquant-0.4.4}/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.4.4 (2026-07-04)
+
+* Harden: json.loads accepts NaN and Infinity, so a drifted or hostile
+  exchange response could book non-finite or negative matched amounts.
+  `_parse_fill` now zeroes anything non-finite or negative (fail closed),
+  and a hypothesis fuzz suite (four property groups, hundreds of generated
+  adversarial responses per run) pins the whole fill contract: market and
+  limit paths book only confirmed finite amounts, the 4xx/uncertain
+  exception partition is total, every transport exception surfaces as
+  OrderUncertain.
+* Security surface: CodeQL workflow (its first scan caught and we fixed a
+  host-boundary bypass in the egress allowlist), Scorecard alert triage
+  with written dismissal reasons, top-level permissions on the publish
+  workflow, direct private-advisory link in SECURITY.md, Dependabot
+  vulnerability alerts enabled. Listed in the official MCP registry as
+  io.github.crp4222/pmq (publish rides releases via OIDC).
+
 ## 0.4.3 (2026-07-04)
 
 * Fix: py-clob-client-v2 1.0.2 reuses its limit-order rounding table for

{pmquant-0.4.3 → pmquant-0.4.4}/CLAUDE.md

@@ -9,16 +9,26 @@ agents EDITING it. Read both before changing code.)
    confirmed (`orderID` + `success is not False` + matched amounts); 4xx is a
    clean rejection; timeout/5xx raises `OrderUncertain`; unparseable = zero.
    Any change that books more optimistically is a regression by definition,
-   whatever it fixes elsewhere. `reconcile()` must keep meaning cancel +
-   `get_trades` truth.
+   whatever it fixes elsewhere. Matched amounts must be finite and
+   non-negative (json.loads accepts NaN/Infinity; hostile values book zero).
+   `reconcile()` must keep meaning cancel + `get_trades` truth. The
+   hypothesis fuzz suite (tests/test_fill_fuzz.py) pins all of this with
+   generated adversarial responses: extend it with every parser change,
+   never delete it.
 2. **Startup introspection** (`_EXPECTED_METHODS`/`_EXPECTED_MARKET_ARGS`):
    the executor REFUSES to run on a drifted py-clob-client-v2. When bumping
    the client dependency, re-verify signatures by introspection and update
    the tables in the same commit.
-3. **Builder code policy**: default = maintainer's code, DISCLOSED in README
-   and code comment, opt-out one line (`builder_code=None` / env). Never
-   hide it, never remove the disclosure, never make opt-out harder. This is
-   the trust model (JKorf pattern).
+3. **Builder code policy**: default = maintainer's code, defined in exactly
+   ONE place (`DEFAULT_BUILDER_CODE` in executor.py) and applied
+   automatically by every order path. DISCLOSED in README and code comment,
+   opt-out one line (`builder_code=None` / env). Never hide it, never remove
+   the disclosure, never make opt-out harder. AND the mirror rule: keep the
+   disclosure at the DOCUMENTATION level only; do not surface attribution in
+   runtime channels (server startup logs, MCP tools or instructions, order
+   responses). It is public on-chain in every signed order; in-band
+   reminders just prompt sessions to toggle a setting that costs users
+   nothing. This is the trust model (JKorf pattern).
 4. **No strategy content, ever**: the maintainer's private bot strategy
    (bands, timing, hours, families, sizing) must never appear in code, docs,
    tests, commits or issues. The bot-template ships deliberately naive
@@ -41,10 +51,20 @@ agents EDITING it. Read both before changing code.)
 * Exchange rules (min size, tick, fee rate) are READ from the venue
   (`book_meta`, `fee_rate`), not hardcoded. `FEE_RATES` is a documented
   snapshot of the official schedule used for estimates.
-* Releases: bump version in `pyproject.toml` AND `src/pmq/__init__.py`,
-  update CHANGELOG.md, push, then `gh release create vX.Y.Z`: PyPI publish
-  is automatic via trusted publishing (no tokens anywhere). PyPI name is
-  `pmquant`, import name `pmq`: keep the README line explaining it.
+* Releases: bump version in `pyproject.toml`, `src/pmq/__init__.py` AND
+  `server.json` (both version fields), update CHANGELOG.md, push, then
+  `gh release create vX.Y.Z`: PyPI publish (trusted publishing, signed
+  attestations) and the MCP registry republish (mcp-publish.yml,
+  github-oidc) both fire on the release event. Registry gotchas: the
+  server.json description caps at 100 characters, and the version must
+  exist on PyPI. PyPI name is `pmquant`, import name `pmq`: keep the
+  README line explaining it.
+* CLAUDE.md and CONTRIBUTING.md are THE SAME FILE by contract: after
+  editing one, copy it over the other in the same commit (`cp CLAUDE.md
+  CONTRIBUTING.md`). Drift between them means an agent read stale rules.
+* Local guard: `git config core.hooksPath .githooks` once per clone
+  enables the pre-push hook (ruff + mypy + pytest). CI is the backstop,
+  but the hook catches a broken push before it lands.
 * GitHub Actions stay pinned by commit SHA (dependabot bumps them); new
   workflows get an explicit least-privilege permissions block. The egress
   test and pip-audit ride the weekly canary: never move them to default CI

pmquant-0.4.4/CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# pmq: engineering invariants for agents CONTRIBUTING to this repo
+
+(AGENTS.md in this repo is for agents USING the library; this file is for
+agents EDITING it. Read both before changing code.)
+
+## Never weaken (the product IS these properties)
+
+1. **The fail-closed fill contract**: a `Fill` books only what the exchange
+   confirmed (`orderID` + `success is not False` + matched amounts); 4xx is a
+   clean rejection; timeout/5xx raises `OrderUncertain`; unparseable = zero.
+   Any change that books more optimistically is a regression by definition,
+   whatever it fixes elsewhere. Matched amounts must be finite and
+   non-negative (json.loads accepts NaN/Infinity; hostile values book zero).
+   `reconcile()` must keep meaning cancel + `get_trades` truth. The
+   hypothesis fuzz suite (tests/test_fill_fuzz.py) pins all of this with
+   generated adversarial responses: extend it with every parser change,
+   never delete it.
+2. **Startup introspection** (`_EXPECTED_METHODS`/`_EXPECTED_MARKET_ARGS`):
+   the executor REFUSES to run on a drifted py-clob-client-v2. When bumping
+   the client dependency, re-verify signatures by introspection and update
+   the tables in the same commit.
+3. **Builder code policy**: default = maintainer's code, defined in exactly
+   ONE place (`DEFAULT_BUILDER_CODE` in executor.py) and applied
+   automatically by every order path. DISCLOSED in README and code comment,
+   opt-out one line (`builder_code=None` / env). Never hide it, never remove
+   the disclosure, never make opt-out harder. AND the mirror rule: keep the
+   disclosure at the DOCUMENTATION level only; do not surface attribution in
+   runtime channels (server startup logs, MCP tools or instructions, order
+   responses). It is public on-chain in every signed order; in-band
+   reminders just prompt sessions to toggle a setting that costs users
+   nothing. This is the trust model (JKorf pattern).
+4. **No strategy content, ever**: the maintainer's private bot strategy
+   (bands, timing, hours, families, sizing) must never appear in code, docs,
+   tests, commits or issues. The bot-template ships deliberately naive
+   demos only.
+5. **Claims must be falsifiable**: no superlatives in README/docs; dated
+   claims with evidence (comparison table, on-chain receipts, measured
+   studies). If you cannot prove it, do not write it.
+6. **MCP safety gates**: trading tools are REGISTERED only when the operator
+   sets `PMQ_MCP_LIVE=1`; per-order `PMQ_MCP_MAX_USD` cap enforced before
+   any client call. Read tools must keep working with zero credentials.
+
+## Working rules
+
+* Tests green (`pytest -q`) and `ruff check .` clean before any push;
+  `pyscn check src/pmq bot-template` (complexity <= 10, no dead code)
+  must stay green too; clone warnings are informational (the template
+  dash deliberately duplicates helpers to stay stdlib-standalone). Add
+  tests with every behavior change. Network-touching tests go to
+  `tests/test_canary_live.py` behind `PMQ_CANARY=1`, never in default CI.
+* Exchange rules (min size, tick, fee rate) are READ from the venue
+  (`book_meta`, `fee_rate`), not hardcoded. `FEE_RATES` is a documented
+  snapshot of the official schedule used for estimates.
+* Releases: bump version in `pyproject.toml`, `src/pmq/__init__.py` AND
+  `server.json` (both version fields), update CHANGELOG.md, push, then
+  `gh release create vX.Y.Z`: PyPI publish (trusted publishing, signed
+  attestations) and the MCP registry republish (mcp-publish.yml,
+  github-oidc) both fire on the release event. Registry gotchas: the
+  server.json description caps at 100 characters, and the version must
+  exist on PyPI. PyPI name is `pmquant`, import name `pmq`: keep the
+  README line explaining it.
+* CLAUDE.md and CONTRIBUTING.md are THE SAME FILE by contract: after
+  editing one, copy it over the other in the same commit (`cp CLAUDE.md
+  CONTRIBUTING.md`). Drift between them means an agent read stale rules.
+* Local guard: `git config core.hooksPath .githooks` once per clone
+  enables the pre-push hook (ruff + mypy + pytest). CI is the backstop,
+  but the hook catches a broken push before it lands.
+* GitHub Actions stay pinned by commit SHA (dependabot bumps them); new
+  workflows get an explicit least-privilege permissions block. The egress
+  test and pip-audit ride the weekly canary: never move them to default CI
+  (they need network) and never widen the egress allowlist beyond
+  polymarket.com without updating SECURITY.md and the README section.
+* The weekly canary workflow is the drift alarm: if it opens an issue, the
+  fix starts by re-running the introspection against the new surface, not
+  by loosening the checks.
+* Keep the library small and auditable (five modules): resist adding
+  dependencies; stdlib first. Anything bot-shaped belongs in bot-template/,
+  not in the package.
+* Style: no em-dashes and no " - " connectors anywhere (strong user rule);
+  keep comments sparse and constraint-focused.

{pmquant-0.4.3 → pmquant-0.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pmquant
-Version: 0.4.3
+Version: 0.4.4
 Summary: Fail-closed execution and market-data layer for Polymarket CLOB V2: local signing, confirmed fills only, fee-correct math, working deposit-wallet (POLY_1271) support.
 Project-URL: Homepage, https://github.com/crp4222/pmq
 Project-URL: Issues, https://github.com/crp4222/pmq/issues
@@ -130,7 +130,10 @@ not your hopes.
 
 At startup pmq **introspects the installed py-clob-client-v2** against the API
 surface it was verified on, and refuses to trade on drift instead of sending
-orders through changed semantics.
+orders through changed semantics. The whole table is pinned by an executable
+test per row plus a hypothesis fuzz suite (hundreds of generated adversarial
+responses per run, including NaN/Infinity and negative amounts, which book
+zero).
 
 ## Quickstart
 
@@ -217,7 +220,9 @@ JKorf/Polymarket.Net; the official client defaults to zero attribution.)
 
 ## MCP server (agents)
 
-`pip install "pmquant[mcp]"` then run `pmq-mcp` (stdio). Read tools (market,
+`pip install "pmquant[mcp]"` then run `pmq-mcp` (stdio). Listed in the
+[official MCP registry](https://registry.modelcontextprotocol.io) as
+`io.github.crp4222/pmq`. Read tools (market,
 book, taker_fee, account_collateral, account_trades) always exist. Trading
 tools (`fak_buy`, `fak_sell`, `cancel_and_reconcile`) are **only registered
 when the operator sets `PMQ_MCP_LIVE=1`** in the server environment: an

{pmquant-0.4.3 → pmquant-0.4.4}/README.md

@@ -95,7 +95,10 @@ not your hopes.
 
 At startup pmq **introspects the installed py-clob-client-v2** against the API
 surface it was verified on, and refuses to trade on drift instead of sending
-orders through changed semantics.
+orders through changed semantics. The whole table is pinned by an executable
+test per row plus a hypothesis fuzz suite (hundreds of generated adversarial
+responses per run, including NaN/Infinity and negative amounts, which book
+zero).
 
 ## Quickstart
 
@@ -182,7 +185,9 @@ JKorf/Polymarket.Net; the official client defaults to zero attribution.)
 
 ## MCP server (agents)
 
-`pip install "pmquant[mcp]"` then run `pmq-mcp` (stdio). Read tools (market,
+`pip install "pmquant[mcp]"` then run `pmq-mcp` (stdio). Listed in the
+[official MCP registry](https://registry.modelcontextprotocol.io) as
+`io.github.crp4222/pmq`. Read tools (market,
 book, taker_fee, account_collateral, account_trades) always exist. Trading
 tools (`fak_buy`, `fak_sell`, `cancel_and_reconcile`) are **only registered
 when the operator sets `PMQ_MCP_LIVE=1`** in the server environment: an

{pmquant-0.4.3 → pmquant-0.4.4}/SECURITY.md

@@ -35,6 +35,7 @@ the important questions:
 
 ## Reporting a vulnerability
 
-Open a GitHub security advisory on this repository (Security tab, "Report a
-vulnerability") or an issue with the `security` label if it is not sensitive.
+Open a [private security advisory](https://github.com/crp4222/pmq/security/advisories/new)
+(Security tab, "Report a vulnerability") or, if it is not sensitive, an
+[issue](https://github.com/crp4222/pmq/issues) with the `security` label.
 You will get an answer within a few days.

{pmquant-0.4.3 → pmquant-0.4.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pmquant"
-version = "0.4.3"
+version = "0.4.4"
 description = "Fail-closed execution and market-data layer for Polymarket CLOB V2: local signing, confirmed fills only, fee-correct math, working deposit-wallet (POLY_1271) support."
 readme = "README.md"
 license = { text = "MIT" }

{pmquant-0.4.3 → pmquant-0.4.4}/server.json

@@ -2,18 +2,18 @@
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.crp4222/pmq",
   "title": "pmq (Polymarket CLOB V2)",
-  "description": "Fail-closed Polymarket CLOB V2 market data and execution, production-proven daily with the maintainer's own funds. Exchange-confirmed fills only; keys never leave the process (weekly public CI egress proof: only polymarket.com is ever contacted). Read tools need zero credentials; trading tools exist only when the operator sets PMQ_MCP_LIVE=1, capped per order by PMQ_MCP_MAX_USD.",
+  "description": "Production-proven Polymarket CLOB V2 trading and data. Fail-closed fills; keys stay local.",
   "repository": {
     "url": "https://github.com/crp4222/pmq",
     "source": "github"
   },
-  "version": "0.4.2",
+  "version": "0.4.4",
   "packages": [
     {
       "registryType": "pypi",
       "registryBaseUrl": "https://pypi.org",
       "identifier": "pmquant",
-      "version": "0.4.2",
+      "version": "0.4.4",
       "runtimeHint": "uvx",
       "transport": {
         "type": "stdio"

{pmquant-0.4.3 → pmquant-0.4.4}/src/pmq/__init__.py

@@ -25,7 +25,7 @@ from .data import (
 )
 from .exceptions import IntrospectionMismatch, OrderUncertain, PmqError
 
-__version__ = "0.4.3"
+__version__ = "0.4.4"
 __all__ = [
     "FEE_RATES", "band_ask_depth_usd", "best_bid_ask", "book_inferred_winner",
     "book_meta", "event_markets", "fee", "get_book", "get_market", "get_tape",

{pmquant-0.4.3 → pmquant-0.4.4}/tests/test_canary_live.py

@@ -101,5 +101,6 @@ def test_egress_only_polymarket_hosts(monkeypatch):
     except pmq.OrderUncertain:
         pass                                  # 5xx path; egress is the point
     print("hosts contacted:", sorted(hosts))
-    foreign = {h for h in hosts if not h.endswith("polymarket.com")}
+    foreign = {h for h in hosts
+               if h != "polymarket.com" and not h.endswith(".polymarket.com")}
     assert not foreign, f"unexpected egress: {sorted(foreign)}"

pmquant-0.4.3/CONTRIBUTING.md

@@ -1,52 +0,0 @@
-# pmq: engineering invariants for agents CONTRIBUTING to this repo
-
-(AGENTS.md in this repo is for agents USING the library; this file is for
-agents EDITING it. Read both before changing code.)
-
-## Never weaken (the product IS these properties)
-
-1. **The fail-closed fill contract**: a `Fill` books only what the exchange
-   confirmed (`orderID` + `success is not False` + matched amounts); 4xx is a
-   clean rejection; timeout/5xx raises `OrderUncertain`; unparseable = zero.
-   Any change that books more optimistically is a regression by definition,
-   whatever it fixes elsewhere. `reconcile()` must keep meaning cancel +
-   `get_trades` truth.
-2. **Startup introspection** (`_EXPECTED_METHODS`/`_EXPECTED_MARKET_ARGS`):
-   the executor REFUSES to run on a drifted py-clob-client-v2. When bumping
-   the client dependency, re-verify signatures by introspection and update
-   the tables in the same commit.
-3. **Builder code policy**: default = maintainer's code, DISCLOSED in README
-   and code comment, opt-out one line (`builder_code=None` / env). Never
-   hide it, never remove the disclosure, never make opt-out harder. This is
-   the trust model (JKorf pattern).
-4. **No strategy content, ever**: the maintainer's private bot strategy
-   (bands, timing, hours, families, sizing) must never appear in code, docs,
-   tests, commits or issues. The bot-template ships deliberately naive
-   demos only.
-5. **Claims must be falsifiable**: no superlatives in README/docs; dated
-   claims with evidence (comparison table, on-chain receipts, measured
-   studies). If you cannot prove it, do not write it.
-6. **MCP safety gates**: trading tools are REGISTERED only when the operator
-   sets `PMQ_MCP_LIVE=1`; per-order `PMQ_MCP_MAX_USD` cap enforced before
-   any client call. Read tools must keep working with zero credentials.
-
-## Working rules
-
-* Tests green (`pytest -q`) and `ruff check .` clean before any push; add
-  tests with every behavior change. Network-touching tests go to
-  `tests/test_canary_live.py` behind `PMQ_CANARY=1`, never in default CI.
-* Exchange rules (min size, tick, fee rate) are READ from the venue
-  (`book_meta`, `fee_rate`), not hardcoded. `FEE_RATES` is a documented
-  snapshot of the official schedule used for estimates.
-* Releases: bump version in `pyproject.toml` AND `src/pmq/__init__.py`,
-  update CHANGELOG.md, push, then `gh release create vX.Y.Z`: PyPI publish
-  is automatic via trusted publishing (no tokens anywhere). PyPI name is
-  `pmquant`, import name `pmq`: keep the README line explaining it.
-* The weekly canary workflow is the drift alarm: if it opens an issue, the
-  fix starts by re-running the introspection against the new surface, not
-  by loosening the checks.
-* Keep the library small and auditable (five modules): resist adding
-  dependencies; stdlib first. Anything bot-shaped belongs in bot-template/,
-  not in the package.
-* Style: no em-dashes and no " - " connectors anywhere (strong user rule);
-  keep comments sparse and constraint-focused.