outcometick 1.4.1 → 1.5.0

package/README.md

@@ -5,7 +5,7 @@
   scripts/publish-sdk-repos.mjs and overwritten wholesale on each publish.
   An edit made here survives until the next publish and then disappears.
 
-  Generated from monorepo revision 0ad1fd0cb6d49a6ceca5b70175f0ebeeaa207b6d.
+  Generated from monorepo revision c210f1ac8cbf693e62cc5b3c5580b0f8663e495a.
 -->
 
 # outcometick
@@ -79,6 +79,37 @@ npm install && npm test
 Requires `python3` on PATH: one of the two static analysers is written in
 Python, and the CLI drives it the same way the API does.
 
+## Downloading data
+
+The other half of the package: a client for the data subscription, on a
+separate import because it has nothing to do with writing a strategy.
+
+```ts
+import { DataClient, NO_VALUE } from "outcometick/data";
+
+const ot = new DataClient();                    // key from OT_KEY
+
+const meta = await ot.meta();                   // what can this key see?
+
+const { files } = await ot.files({
+  from: "2026-08-01", to: "2026-08-12",         // or date: "2026-08-12"
+  asset: ["BTCUSD", "ETHUSD"],                  // an array means "any of these"
+  dataset: "prices",
+  interval: ["5m", NO_VALUE],                   // "5m" alone EXCLUDES the
+});                                             // period-less settlement streams
+
+await ot.download(files[0], { saveTo: files[0].name });   // checksum verified
+```
+
+`meta()` reports the dimensions this key can actually reach. Note that
+`intervals` holds real durations only — the `none` sentinel is reported
+separately under `filterTokens`, so a caller that builds an enum from it or
+parses the values as durations never meets a token.
+
+Downloads are checksum-verified: `/v1/dl` redirects to storage with the sha256
+in a header, and the client follows that redirect itself so the checksum is not
+thrown away.
+
 ---
 
 Writing your strategy in Python instead? The SDK for it is

package/api/lib/backtest-contract.mjs

@@ -15,7 +15,7 @@ import { FIRST_COMPLETE_DAY } from './coverage-window.mjs';
 export const SCHEMA_VERSION = 1;
 
 /** SDK version reported by the docs page and stamped into every report. */
-export const SDK_VERSION = '1.4.1';
+export const SDK_VERSION = '1.5.0';
 
 // ---------------------------------------------------------------------------
 // Languages

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "outcometick",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "description": "Strategy SDK and CLI for outcometick prediction-market backtests",
   "type": "module",
   "license": "MIT",
@@ -20,6 +20,10 @@
     ".": {
       "types": "./index.d.ts",
       "default": "./index.mjs"
+    },
+    "./data": {
+      "types": "./client/data.d.ts",
+      "default": "./client/data.mjs"
     }
   },
   "engines": {
@@ -36,7 +40,7 @@
     "!**/*.test-d.ts"
   ],
   "scripts": {
-    "test": "node --test runner/analyze/*.test.mjs runner/engine/*.test.mjs runner/harness/node/*.test.mjs cli/*.test.mjs"
+    "test": "node --test runner/analyze/*.test.mjs runner/engine/*.test.mjs runner/harness/node/*.test.mjs cli/*.test.mjs client/*.test.mjs"
   },
   "dependencies": {
     "acorn": "^8.18.0"

package/runner/analyze/python_analyze.py

@@ -145,6 +145,26 @@ def check_import(module, name, line, deps, relative_ok):
             else "E_FORBIDDEN"
         )
         raise Reject(code, f"{name}:{line}: import {root} — {FORBIDDEN_IMPORTS[root]}", name, line)
+    # `outcometick` is allowed as the SDK module and nothing else. In the
+    # sandbox it is a single flat module -- Strategy and Order -- so
+    # `outcometick.data` resolves to nothing there, even though pip installs it
+    # as a real submodule. Allowing it because the ROOT matches would mean
+    # `ot check` passing a strategy that dies on import after being queued,
+    # which is the exact failure the "if it passes locally it will not be
+    # rejected on submit" promise exists to prevent.
+    #
+    # The JavaScript analyser has always compared the whole specifier, so
+    # `outcometick/data` was already refused there. This is the Python half of
+    # the same rule.
+    if root == "outcometick" and module != "outcometick":
+        raise Reject(
+            "E_IMPORT",
+            f"{name}:{line}: import of {module!r} — only 'outcometick' itself is "
+            "available to a strategy; the sandbox has no network and no submodules",
+            name,
+            line,
+            specifier=module,
+        )
     if root in ALWAYS_ALLOWED or root in deps:
         return
     raise Reject(