crowdypy 0.4.0.dev1__tar.gz → 0.4.1.dev1__tar.gz

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/AGENTS.md

@@ -122,8 +122,12 @@ names, a tag that is not the tree's version, and a default origin for another ti
 builds every wheel and the sdist, scans them, publishes `X.Y.Z.devN` (dev), `X.Y.ZrcN` (test)
 or `X.Y.Z` (prod) to PyPI by trusted publishing, downloads the published wheel back to read
 its origin again, and creates the GitHub release with the same files. PyPI publishing runs
-only when the repository variable `PYPI_PUBLISHING` is `enabled`, which the operator sets
-once the PyPI trusted publisher (workflow `release.yml`, environment `pypi`) is registered.
+only when the repository variable `PYPI_PUBLISHING` is `enabled` (it is, since 2026-10-01),
+through the trusted publisher on PyPI project `crowdypy` (owner CrowdedKingdoms, repository
+CrowdyPy, workflow `release.yml`, environment `pypi`). The first version there,
+`0.4.0.dev1`, was uploaded by hand from the `dev/v0.4.0` release's assets before the
+publisher existed; every later one comes from its tag. PyPI accepts a version once, so a
+re-run takes the next N (`scripts/ci/resolve_pypi_version.py` reads what PyPI already has).
 
 Merging a PR from the command line: `gh pr merge` fails its preflight on this org, so use
 `gh api -X PUT repos/CrowdedKingdoms/CrowdyPy/pulls/<n>/merge -f merge_method=merge`.

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/MIGRATION.md

@@ -3,6 +3,18 @@
 CrowdyPy is pre-1.0. Within a minor line, patch releases keep source compatibility; each
 new minor may change the API. Read the section for every minor you skip.
 
+## 0.4.1
+
+Documentation only; nothing the package does changed. Still CrowdyJS 18.0.4 and CrowdyCPP
+0.54.0.
+
+- The README, which PyPI shows, carries the current tier pins and an example of installing a
+  wheel straight from a GitHub release.
+- The roots CrowdyPy wraps beyond CrowdyJS are described precisely: CrowdyJS's portable API
+  sends none of them, CrowdyCPP covers them, and CrowdyJS's in-browser agent does send the
+  two provider-consent roots and the model-usage root.
+- 0.4.1 is the first version PyPI receives from the release workflow, by trusted publishing.
+
 ## 0.4.0
 
 Headless Crowdy Studio and full CrowdyJS parity. Additive; still CrowdyJS 18.0.4 and
@@ -25,7 +37,7 @@ CrowdyCPP 0.54.0.
     `parse_client_tick_interval_ms` port their CrowdyJS namesakes.
   - `canonical_json`, `digest_canonical_json` and `project_content_hash` compute the
     approval digests CrowdyJS computes.
-- **The roots CrowdyCPP sends and CrowdyJS does not:**
+- **The roots CrowdyCPP covers and CrowdyJS's portable API leaves out:**
   - `AuthAPI.confirm_email` and `resend_confirmation_email`;
   - `UsageAPI.org_summary`, `app_projection` and `org_projection`;
   - `AppsAPI.compute_budget`, `set_compute_budget` and `clear_compute_budget`;

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: crowdypy
-Version: 0.4.0.dev1
+Version: 0.4.1.dev1
 Summary: Official Python SDK for Crowded Kingdoms: typed GraphQL clients and a native UDP replication core
 Keywords: crowded-kingdoms,multiplayer,replication,graphql,sdk,udp
 Author: Crowded Kingdoms
@@ -51,19 +51,19 @@ CrowdyPy follows the [CrowdyJS](https://github.com/CrowdedKingdoms/CrowdyJS) API
 client, bound with [nanobind](https://github.com/wjakob/nanobind) and shipped inside the
 wheel. Python never touches a datagram.
 
-**v0.4.0: headless Crowdy Studio, and full parity with CrowdyJS.**
+**v0.4.1: headless Crowdy Studio, and full parity with CrowdyJS.**
 - `crowdypy.studio.CrowdyStudioController` is the Studio editor without a browser: open
   projects, edit with autosave and revision conflicts, bind GitHub, apply agent patches with
   checkpoints, and build, deploy and run mods. `StudioLayoutController` and
   `parse_rustc_diagnostics` match CrowdyJS byte for byte.
-- The roots CrowdyCPP sends and CrowdyJS does not are wrapped too: email confirmation, usage
-  projections, compute budgets, listing versions, the narrow Studio mutations, and
-  `client.crowdy_studio_agent`.
+- The GraphQL roots CrowdyCPP covers and CrowdyJS's portable API leaves out are wrapped too:
+  email confirmation, usage projections, compute budgets, listing versions, the narrow Studio
+  mutations, and `client.crowdy_studio_agent`.
 - `crowdypy.player_host` is the typed observation contract a game implements so tooling can
   read the player it controls, validated exactly as CrowdyJS validates it.
 - The parity gate is strict: [`docs/parity-matrix.md`](docs/parity-matrix.md) has no gaps.
-- 0.3.0 brought the World Stores, the Game Kit, ck-exec and subscriptions; 0.2.0 native UDP
-  replication (`client.udp`); 0.1.0 the GraphQL client.
+- 0.4.1 changes documentation only. 0.3.0 brought the World Stores, the Game Kit, ck-exec and
+  subscriptions; 0.2.0 native UDP replication (`client.udp`); 0.1.0 the GraphQL client.
 
 See [MIGRATION.md](MIGRATION.md).
 
@@ -83,12 +83,14 @@ API origin (`crowdypy.CROWDY_DEFAULT_TIER` says which):
 
 | Tier | PyPI version | Pin |
 |---|---|---|
-| dev | `X.Y.Z.devN` | `crowdypy==0.1.0.dev1` |
-| test | `X.Y.ZrcN` | `crowdypy==0.1.0rc1` |
-| prod | `X.Y.Z` | `crowdypy==0.1.0` |
+| dev | `X.Y.Z.devN` | `crowdypy==0.4.0.dev1` |
+| test | `X.Y.ZrcN` | `crowdypy==0.4.0rc1` |
+| prod | `X.Y.Z` | `crowdypy==0.4.0` |
 
 pip skips pre-releases unless a requirement names one, so a prod range never picks up a dev
-or test build. The same wheels are attached to each GitHub release.
+or test build. The same wheels and the sdist are attached to each
+[GitHub release](https://github.com/CrowdedKingdoms/CrowdyPy/releases), and pip installs one
+from its URL (`pip install https://github.com/CrowdedKingdoms/CrowdyPy/releases/download/<tag>/<wheel>`).
 
 ## Quick start
 

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/README.md

@@ -11,19 +11,19 @@ CrowdyPy follows the [CrowdyJS](https://github.com/CrowdedKingdoms/CrowdyJS) API
 client, bound with [nanobind](https://github.com/wjakob/nanobind) and shipped inside the
 wheel. Python never touches a datagram.
 
-**v0.4.0: headless Crowdy Studio, and full parity with CrowdyJS.**
+**v0.4.1: headless Crowdy Studio, and full parity with CrowdyJS.**
 - `crowdypy.studio.CrowdyStudioController` is the Studio editor without a browser: open
   projects, edit with autosave and revision conflicts, bind GitHub, apply agent patches with
   checkpoints, and build, deploy and run mods. `StudioLayoutController` and
   `parse_rustc_diagnostics` match CrowdyJS byte for byte.
-- The roots CrowdyCPP sends and CrowdyJS does not are wrapped too: email confirmation, usage
-  projections, compute budgets, listing versions, the narrow Studio mutations, and
-  `client.crowdy_studio_agent`.
+- The GraphQL roots CrowdyCPP covers and CrowdyJS's portable API leaves out are wrapped too:
+  email confirmation, usage projections, compute budgets, listing versions, the narrow Studio
+  mutations, and `client.crowdy_studio_agent`.
 - `crowdypy.player_host` is the typed observation contract a game implements so tooling can
   read the player it controls, validated exactly as CrowdyJS validates it.
 - The parity gate is strict: [`docs/parity-matrix.md`](docs/parity-matrix.md) has no gaps.
-- 0.3.0 brought the World Stores, the Game Kit, ck-exec and subscriptions; 0.2.0 native UDP
-  replication (`client.udp`); 0.1.0 the GraphQL client.
+- 0.4.1 changes documentation only. 0.3.0 brought the World Stores, the Game Kit, ck-exec and
+  subscriptions; 0.2.0 native UDP replication (`client.udp`); 0.1.0 the GraphQL client.
 
 See [MIGRATION.md](MIGRATION.md).
 
@@ -43,12 +43,14 @@ API origin (`crowdypy.CROWDY_DEFAULT_TIER` says which):
 
 | Tier | PyPI version | Pin |
 |---|---|---|
-| dev | `X.Y.Z.devN` | `crowdypy==0.1.0.dev1` |
-| test | `X.Y.ZrcN` | `crowdypy==0.1.0rc1` |
-| prod | `X.Y.Z` | `crowdypy==0.1.0` |
+| dev | `X.Y.Z.devN` | `crowdypy==0.4.0.dev1` |
+| test | `X.Y.ZrcN` | `crowdypy==0.4.0rc1` |
+| prod | `X.Y.Z` | `crowdypy==0.4.0` |
 
 pip skips pre-releases unless a requirement names one, so a prod range never picks up a dev
-or test build. The same wheels are attached to each GitHub release.
+or test build. The same wheels and the sdist are attached to each
+[GitHub release](https://github.com/CrowdedKingdoms/CrowdyPy/releases), and pip installs one
+from its URL (`pip install https://github.com/CrowdedKingdoms/CrowdyPy/releases/download/<tag>/<wheel>`).
 
 ## Quick start
 

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/docs/compatibility.md

@@ -5,7 +5,7 @@ are in `pyproject.toml` (`[project].version`, `[tool.crowdypy.crowdyjs]`,
 `[tool.crowdypy.crowdycpp]`); `tests/unit/test_release_versions.py` refuses this page when
 its version disagrees.
 
-- CrowdyPy `0.4.0`
+- CrowdyPy `0.4.1`
 - API surface: CrowdyJS (the pinned version and commit in `pyproject.toml`); the generated
   `docs/parity-matrix.md` lists every covered method, every native equivalent and every
   browser exclusion with its reason. The gate is strict: there are no portable gaps, and a

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/docs/e2e-coverage.md

@@ -47,6 +47,7 @@ player once and signs it in for the later suites.
 |---|---|---|---|
 | 2026-10-01 | local stack: ck-api at `dev` (`78386df3`), two replication servers, the 3-node Citus lab | 0.4.0 (branch) | 8 passed; Studio skipped (no grid in the app) |
 | 2026-10-01 | dev tier, app `96701660793088` (CrowdyPy e2e, in the org admin's org) | 0.4.0 (branch) | 8 passed; Studio skipped (the suite needs a grid the owner controls in that app; a placeholder is refused with `CROWDY_STUDIO_GRID_NOT_FOUND`) |
+| 2026-10-01 | dev tier, app `96701660793088` | the published `dev/v0.4.0` wheel (`0.4.0.dev1`, manylinux x86_64, installed into a clean Python 3.12) | 8 passed |
 
 ## Not covered here
 

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "scikit_build_core.build"
 
 [project]
 name = "crowdypy"
-version = "0.4.0.dev1"
+version = "0.4.1.dev1"
 description = "Official Python SDK for Crowded Kingdoms: typed GraphQL clients and a native UDP replication core"
 readme = "README.md"
 license = "MIT AND Apache-2.0"

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/src/crowdypy/_sync/domains/crowdy_studio_agent.py

@@ -6,7 +6,8 @@ The model endpoint itself is REST (``GET /v1/model/models``, ``POST
 spends tokens through. These GraphQL companions read what it recorded and gate whether it
 may run: the player's provider consent and own usage (``use_studio_agent``), and the app's
 policy and sanitized usage (``view_compute_diagnostics``; ``manage_compute`` to change it).
-Mirrors CrowdyCPP's ``CrowdyStudioAgentAPI``; CrowdyJS sends these from its agent pane.
+Mirrors CrowdyCPP's ``CrowdyStudioAgentAPI``. CrowdyJS's in-browser agent sends the consent
+and model-usage roots itself; its portable API sends none of the seven.
 """
 
 from __future__ import annotations

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/src/crowdypy/_version.py

@@ -1,3 +1,3 @@
 """The CrowdyPy release this source tree builds."""
 
-__version__ = "0.4.0"
+__version__ = "0.4.1"

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/src/crowdypy/domains/crowdy_studio_agent.py

@@ -5,7 +5,8 @@ The model endpoint itself is REST (``GET /v1/model/models``, ``POST
 spends tokens through. These GraphQL companions read what it recorded and gate whether it
 may run: the player's provider consent and own usage (``use_studio_agent``), and the app's
 policy and sanitized usage (``view_compute_diagnostics``; ``manage_compute`` to change it).
-Mirrors CrowdyCPP's ``CrowdyStudioAgentAPI``; CrowdyJS sends these from its agent pane.
+Mirrors CrowdyCPP's ``CrowdyStudioAgentAPI``. CrowdyJS's in-browser agent sends the consent
+and model-usage roots itself; its portable API sends none of the seven.
 """
 
 from __future__ import annotations

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/tests/unit/domains/test_crowdycpp_roots.py

@@ -1,5 +1,5 @@
-"""The roots CrowdyCPP sends and CrowdyJS 18.0.4 does not: each sends its inline document
-with the variables CrowdyCPP sends."""
+"""The roots CrowdyCPP covers and CrowdyJS 18.0.4's portable API leaves out: each sends its
+inline document with the variables CrowdyCPP sends."""
 
 from __future__ import annotations
 

{crowdypy-0.4.0.dev1 → crowdypy-0.4.1.dev1}/uv.lock

@@ -103,7 +103,7 @@ wheels = [
 
 [[package]]
 name = "crowdypy"
-version = "0.4.0"
+version = "0.4.1"
 source = { editable = "." }
 dependencies = [
     { name = "httpx" },