mostlyright-data 0.10.2__tar.gz → 0.10.3__tar.gz

{mostlyright_data-0.10.2 → mostlyright_data-0.10.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.10.2
+Version: 0.10.3
 Summary: Mostly Right CLI for reproducible, reviewed Parquet datasets
 Project-URL: Homepage, https://mostlyright.md/
 Project-URL: Documentation, https://mostlyright.md/docs/guides/cli/
@@ -159,15 +159,13 @@ Requires-Dist: pyhdf==0.11.7; ((sys_platform == 'linux' and platform_machine ==
 Requires-Dist: pypublicdecompwt==2.8.1.6; extra == 'scientific'
 Requires-Dist: rasterio==1.5.1; extra == 'scientific'
 Requires-Dist: zarr==3.3.0; extra == 'scientific'
-Provides-Extra: viewer
-Requires-Dist: nbconvert==7.17.1; extra == 'viewer'
-Requires-Dist: nbformat==5.10.4; extra == 'viewer'
 Description-Content-Type: text/markdown
 
 # mostlyright-data
 
 Browse datasets built by our community or create your own with agents that find the sources and
-configure the pipeline. Mostly Right keeps the dataset live.
+configure the pipeline. Mostly Right treats a successful run as one readable dataset version;
+publishing that version does not by itself prove that catch-up or scheduled refresh is running.
 
 `mostlyright-data` is the command-line client. It probes sources, registers one recipe document,
 starts and follows hosted dataset runs, reads what they delivered, and downloads the datasets after
@@ -183,7 +181,8 @@ Use CPython 3.13.
 python -m pip install mostlyright-data
 ```
 
-The default install is the hosted client. It works on Linux, macOS, and Windows.
+That is the whole install. There is no second profile and no lane to choose: every `mr-data`
+command sends its work to the backend, and it works on Linux, macOS, and Windows.
 
 It also carries the `mr-data-build` agent skill, which Claude Code and Codex read to author a
 recipe without rediscovering the contract a run at a time. The first `mr-data` command you run
@@ -212,7 +211,7 @@ mr-data --help
 ```bash
 mr-data probe SOURCE_ID "does this feed carry city grain before 2021"
 mr-data recipe RECIPE.json
-mr-data run RECIPE_ID --sample --window 2025-03-01..2025-04-01 --max-rows 50000
+mr-data run RECIPE_ID --sample --max-rows 50000
 mr-data checks RUN
 mr-data download RUN --output ./out
 ```
@@ -220,20 +219,21 @@ mr-data download RUN --output ./out
 `probe` asks one registered source one question; the session behind it is opened, reused and closed
 for you. `recipe` registers one document and prints the identifiers the server derived from it.
 `run` starts a run and `mr-data status RUN`, `mr-data runs`, and `mr-data watch RUN` report on it.
-`mr-data promote TABLE_ID` makes a table live, and it is the one step that asks a person first.
+The current Harness worker executes unwindowed `sample` and `full` runs. It refuses a stated run
+window, and it does not execute `refresh`, `backfill`, promotion catch-up, or scheduled warehouse
+continuation. `mr-data promote TABLE_ID` is still the human-gated publication request, but claim a
+table is live and current only when the deployed Studio and warehouse services return that evidence.
 
-## Local execution
+## There is no local execution
 
-The local execution lane runs only on Linux:
+There used to be. A second product lane built datasets on your own machine, and `mr-data` carried
+about fifty commands for making, running, serving, indexing, checking and signing a build here.
+That lane is gone: the engine it ran now ships only inside the backend's worker images.
 
-```bash
-python -m pip install "mostlyright-data[local]"
-```
-
-It is not required for the hosted client, and it is off by default: `mr-data` sends that work to
-the backend. What still runs on this computer is catalog authoring, the search index, and the
-commands that check a document or a run folder. A command with no backend lane refuses by name and
-says why.
+`mr-data --help` lists every command this product has. A name that is not on it is not a command
+and says so. The distribution still publishes a `[local]` extra — that is the engine's dependency
+closure, which the backend's worker image installs — and installing it makes no command run that
+does not run without it.
 
 ## Documentation
 
@@ -246,16 +246,14 @@ says why.
 Use `mr-data --help` for the full command list and options. Commands that support
 `--json` write one JSON object.
 
-`--input-root` and `--output` may use relative paths.
+`--output` may use a relative path.
 
 ## Behavior and limits
 
-- `mr-data review RUN_DIR --local` runs the deterministic checks and writes no review decision. It exits 1 when a check fails. Write the flag after the command name; before it, `--local` is the lane selector.
-- `mr-data review RUN_DIR --report REPORT` seals a review decision from signed reviewer reports.
 - Weather Reader versions 1 and 2 accept one extracted GRIB2 record and refuse a multi-record GFS
   or HRRR file. Version 3 reads a bounded collection and selects exactly one sealed record.
-- Hosted credential-free acquisition supports one single-address public HTTPS object. Bounded collections require both local attestations.
-- A keyed stream venue is named by a credential reference the backend holds, never by a value. No command flag takes a secret as an argument; the local recorder lane reads one from a `0600` file named by `--credential-file`. Venues reached over an actual WebSocket are covered; a venue whose credential comes from an interactive human login, or that is not WebSocket at all, is not.
+- Hosted credential-free acquisition supports one single-address public HTTPS object. Bounded collections have no hosted route, and the route they used to have was the deleted local one.
+- A keyed stream venue is named by a credential reference the backend holds, never by a value. No command flag takes a secret as an argument. Venues reached over an actual WebSocket are covered; a venue whose credential comes from an interactive human login, or that is not WebSocket at all, is not.
 
 ## Verification
 
@@ -272,5 +270,5 @@ before review or merge.
 uv sync --locked --extra dev
 ```
 
-The local test suite requires Linux for worker-boundary tests. The hosted client is tested on Linux,
-macOS, and Windows.
+The test suite drives the execution engine in-process, and requires Linux for the worker-boundary
+tests. The client itself is tested on Linux, macOS, and Windows.

{mostlyright_data-0.10.2 → mostlyright_data-0.10.3}/README.md

@@ -1,7 +1,8 @@
 # mostlyright-data
 
 Browse datasets built by our community or create your own with agents that find the sources and
-configure the pipeline. Mostly Right keeps the dataset live.
+configure the pipeline. Mostly Right treats a successful run as one readable dataset version;
+publishing that version does not by itself prove that catch-up or scheduled refresh is running.
 
 `mostlyright-data` is the command-line client. It probes sources, registers one recipe document,
 starts and follows hosted dataset runs, reads what they delivered, and downloads the datasets after
@@ -17,7 +18,8 @@ Use CPython 3.13.
 python -m pip install mostlyright-data
 ```
 
-The default install is the hosted client. It works on Linux, macOS, and Windows.
+That is the whole install. There is no second profile and no lane to choose: every `mr-data`
+command sends its work to the backend, and it works on Linux, macOS, and Windows.
 
 It also carries the `mr-data-build` agent skill, which Claude Code and Codex read to author a
 recipe without rediscovering the contract a run at a time. The first `mr-data` command you run
@@ -46,7 +48,7 @@ mr-data --help
 ```bash
 mr-data probe SOURCE_ID "does this feed carry city grain before 2021"
 mr-data recipe RECIPE.json
-mr-data run RECIPE_ID --sample --window 2025-03-01..2025-04-01 --max-rows 50000
+mr-data run RECIPE_ID --sample --max-rows 50000
 mr-data checks RUN
 mr-data download RUN --output ./out
 ```
@@ -54,20 +56,21 @@ mr-data download RUN --output ./out
 `probe` asks one registered source one question; the session behind it is opened, reused and closed
 for you. `recipe` registers one document and prints the identifiers the server derived from it.
 `run` starts a run and `mr-data status RUN`, `mr-data runs`, and `mr-data watch RUN` report on it.
-`mr-data promote TABLE_ID` makes a table live, and it is the one step that asks a person first.
+The current Harness worker executes unwindowed `sample` and `full` runs. It refuses a stated run
+window, and it does not execute `refresh`, `backfill`, promotion catch-up, or scheduled warehouse
+continuation. `mr-data promote TABLE_ID` is still the human-gated publication request, but claim a
+table is live and current only when the deployed Studio and warehouse services return that evidence.
 
-## Local execution
+## There is no local execution
 
-The local execution lane runs only on Linux:
+There used to be. A second product lane built datasets on your own machine, and `mr-data` carried
+about fifty commands for making, running, serving, indexing, checking and signing a build here.
+That lane is gone: the engine it ran now ships only inside the backend's worker images.
 
-```bash
-python -m pip install "mostlyright-data[local]"
-```
-
-It is not required for the hosted client, and it is off by default: `mr-data` sends that work to
-the backend. What still runs on this computer is catalog authoring, the search index, and the
-commands that check a document or a run folder. A command with no backend lane refuses by name and
-says why.
+`mr-data --help` lists every command this product has. A name that is not on it is not a command
+and says so. The distribution still publishes a `[local]` extra — that is the engine's dependency
+closure, which the backend's worker image installs — and installing it makes no command run that
+does not run without it.
 
 ## Documentation
 
@@ -80,16 +83,14 @@ says why.
 Use `mr-data --help` for the full command list and options. Commands that support
 `--json` write one JSON object.
 
-`--input-root` and `--output` may use relative paths.
+`--output` may use a relative path.
 
 ## Behavior and limits
 
-- `mr-data review RUN_DIR --local` runs the deterministic checks and writes no review decision. It exits 1 when a check fails. Write the flag after the command name; before it, `--local` is the lane selector.
-- `mr-data review RUN_DIR --report REPORT` seals a review decision from signed reviewer reports.
 - Weather Reader versions 1 and 2 accept one extracted GRIB2 record and refuse a multi-record GFS
   or HRRR file. Version 3 reads a bounded collection and selects exactly one sealed record.
-- Hosted credential-free acquisition supports one single-address public HTTPS object. Bounded collections require both local attestations.
-- A keyed stream venue is named by a credential reference the backend holds, never by a value. No command flag takes a secret as an argument; the local recorder lane reads one from a `0600` file named by `--credential-file`. Venues reached over an actual WebSocket are covered; a venue whose credential comes from an interactive human login, or that is not WebSocket at all, is not.
+- Hosted credential-free acquisition supports one single-address public HTTPS object. Bounded collections have no hosted route, and the route they used to have was the deleted local one.
+- A keyed stream venue is named by a credential reference the backend holds, never by a value. No command flag takes a secret as an argument. Venues reached over an actual WebSocket are covered; a venue whose credential comes from an interactive human login, or that is not WebSocket at all, is not.
 
 ## Verification
 
@@ -106,5 +107,5 @@ before review or merge.
 uv sync --locked --extra dev
 ```
 
-The local test suite requires Linux for worker-boundary tests. The hosted client is tested on Linux,
-macOS, and Windows.
+The test suite drives the execution engine in-process, and requires Linux for the worker-boundary
+tests. The client itself is tested on Linux, macOS, and Windows.

{mostlyright_data-0.10.2 → mostlyright_data-0.10.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mostlyright-data"
-version = "0.10.2"
+version = "0.10.3"
 description = "Mostly Right CLI for reproducible, reviewed Parquet datasets"
 readme = "README.md"
 requires-python = ">=3.13,<3.14"
@@ -26,9 +26,6 @@ Documentation = "https://mostlyright.md/docs/guides/cli/"
 native-reader-artifacts = [
     "mostlyright-grib==0.1.0 ; sys_platform == 'darwin' or sys_platform == 'linux'",
 ]
-viewer-browser = [
-    "playwright==1.61.0",
-]
 pypi-release = [
     # The unprivileged release builder validates both archives with this locked
     # tool before it transfers bytes to the OIDC-only PyPI publisher.
@@ -60,9 +57,8 @@ pyhdf = [
 # ⚠ NOT `cli:main`. `cli` imports `hosted_worker`, which imports pyarrow and cryptography at module
 # scope, so `cli` cannot even be IMPORTED on a thin install. The router is the one module that can
 # run on a bare interpreter and decide which lane this invocation belongs to. The local product
-# lanes are off by default, so with the `local` extra present it hands the names that still run on
-# this computer to `cli.main` unchanged, and every other name is answered by the hosted lane or
-# told, by name, that this computer no longer runs it.
+# lanes are gone rather than off, so the router hands NO name to `cli.main` any more: every name is
+# either answered by the hosted lane or told, by name, that this product does not have it.
 mr-data = "mostlyright.data_harness.thin.router:main"
 # ⚠ AND NOT THE MODULES THEMSELVES, for the same reason. Each of these seven is defined in a
 # module that imports pyarrow or cryptography at module scope -- or, for the catalogue job, reaches
@@ -92,6 +88,9 @@ mr-data-ingestion-job = "mostlyright.data_harness.thin.workers:ingestion_job_mai
 # the ingestion Job run from -- the install stage puts every console script in the image and
 # that stage deletes none of them -- so this entry is the whole of what a new job shape needs.
 mr-data-stream-recorder-job = "mostlyright.data_harness.thin.workers:stream_recorder_job_main"
+# The continuous Worker Pool is a separate long-lived product entrypoint.  The bounded recorder
+# Job above remains an internal smoke/fixture path and is never selected by this executable.
+mr-data-stream-subscription-worker = "mostlyright.data_harness.thin.workers:stream_subscription_worker_main"
 
 [project.optional-dependencies]
 build = [
@@ -258,12 +257,6 @@ local-search-neural = [
 hosted = [
     "mostlyright-studio-client-v3==3.0.0",
 ]
-# `mr-data view` renders through the stdlib-only in-repo nbrender and imports neither of these.
-# The extra pins nbconvert and nbformat for executing appended notebook chart cells.
-viewer = [
-    "nbconvert==7.17.1",
-    "nbformat==5.10.4",
-]
 
 [build-system]
 requires = ["hatchling==1.28.0"]