crowdypy 0.5.0.dev1__tar.gz → 0.5.1.dev1__tar.gz

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/MIGRATION.md

@@ -3,6 +3,21 @@
 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.5.1
+
+CrowdyJS 18.2.0 and CrowdyCPP 0.56.0. No API change; one behaviour fix.
+
+- **Chunk loads keep recorded voxel edits** (OI-2026-10-02-006). Since ck-api v2.33.0 every
+  voxel edit recorded for a chunk (a hub's or mod's `world.set_voxels`, `updateVoxel`, a
+  realtime voxel update) arrives only in the chunk's `voxelStates`, never in its `voxels`.
+  `ChunkStore.hydrate()` now applies each entry's voxel type at its voxel, also on a chunk
+  stored with `voxels: null`, and an entry without a state clears the hydrated state there.
+  `ensure_around()` no longer reloads a chunk it already holds when a bulk load around a new
+  center returns it again; prune the chunk to load it afresh. Turn on
+  `hydrate_voxel_states` to see hub and mod edits after a reload.
+- A state a local `set_voxel` gave a voxel is not cleared by a later hydration that says the
+  voxel has none: the native core keeps it until the next realtime update there.
+
 ## 0.5.0
 
 CrowdyJS 18.1.0 and CrowdyCPP 0.55.0. Additive, plus one refusal that is a security fix.

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: crowdypy
-Version: 0.5.0.dev1
+Version: 0.5.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,11 +51,13 @@ 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.5.0: open grids, and the ck-exec gateway check (CrowdyJS 18.1.0, CrowdyCPP 0.55.0).**
-- `client.exec.connect()` sends the connect token only to a gateway on the game API's estate
-  (or the release's default origin's); any other gateway is refused before it is dialed. A
-  gateway that refuses the token is reported as `Denied`, with its reason.
-- `game_apps.open_permissions()` and `set_open_permissions()`: grids open to every player.
+**v0.5.1: chunk loads keep recorded voxel edits (CrowdyJS 18.2.0, CrowdyCPP 0.56.0).**
+- `ChunkStore.hydrate()` puts every recorded voxel edit (`voxelStates`: a hub's or mod's
+  `world.set_voxels`, `updateVoxel`, realtime updates) on the grid, and a later
+  `ensure_around()` keeps a chunk it already loaded instead of reloading its bare voxels.
+- 0.5.0 brought the ck-exec gateway check (`client.exec.connect()` sends the connect token
+  only to a gateway on the game API's estate, and reports a refusal as `Denied`) and open
+  grids (`game_apps.open_permissions()` and `set_open_permissions()`).
 - 0.4 brought the headless Crowdy Studio (`crowdypy.studio`), player-host observation
   (`crowdypy.player_host`), the roots CrowdyCPP covers beyond CrowdyJS, and the strict parity
   gate ([`docs/parity-matrix.md`](docs/parity-matrix.md) has no gaps); 0.3.0 the World Stores,

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/README.md

@@ -11,11 +11,13 @@ 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.5.0: open grids, and the ck-exec gateway check (CrowdyJS 18.1.0, CrowdyCPP 0.55.0).**
-- `client.exec.connect()` sends the connect token only to a gateway on the game API's estate
-  (or the release's default origin's); any other gateway is refused before it is dialed. A
-  gateway that refuses the token is reported as `Denied`, with its reason.
-- `game_apps.open_permissions()` and `set_open_permissions()`: grids open to every player.
+**v0.5.1: chunk loads keep recorded voxel edits (CrowdyJS 18.2.0, CrowdyCPP 0.56.0).**
+- `ChunkStore.hydrate()` puts every recorded voxel edit (`voxelStates`: a hub's or mod's
+  `world.set_voxels`, `updateVoxel`, realtime updates) on the grid, and a later
+  `ensure_around()` keeps a chunk it already loaded instead of reloading its bare voxels.
+- 0.5.0 brought the ck-exec gateway check (`client.exec.connect()` sends the connect token
+  only to a gateway on the game API's estate, and reports a refusal as `Denied`) and open
+  grids (`game_apps.open_permissions()` and `set_open_permissions()`).
 - 0.4 brought the headless Crowdy Studio (`crowdypy.studio`), player-host observation
   (`crowdypy.player_host`), the roots CrowdyCPP covers beyond CrowdyJS, and the strict parity
   gate ([`docs/parity-matrix.md`](docs/parity-matrix.md) has no gaps); 0.3.0 the World Stores,

{crowdypy-0.5.0.dev1 → crowdypy-0.5.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.5.0`
+- CrowdyPy `0.5.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
@@ -34,7 +34,7 @@ requirement names one exactly, the same way a caret never matches an npm prerele
 
 ## Server compatibility
 
-- ck-exec (`client.exec`) is a dev-tier preview; a Game API that does not serve the
+- ck-exec (`client.exec`) runs on dev and test, and on prod from its migration; a Game API that does not serve the
   `exec*` roots answers those calls with a GraphQL validation error.
 - Direct sign-in (`auth.login`, `auth.register`) is served to non-browser callers. CrowdyPy
   sends no `Origin` header, so it is exempt from `HOSTED_SIGN_IN_REQUIRED`.

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/docs/e2e-coverage.md

@@ -51,6 +51,7 @@ player once and signs it in for the later suites.
 | 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 |
 | 2026-10-01 | dev tier, app `96701660793088` | `crowdypy 0.4.1.dev1` from PyPI (`pip install crowdypy` in a clean Python 3.12; the first version published by trusted publishing) | 8 passed; Studio skipped |
+| 2026-10-01 | dev tier, app `96701660793088`; the open-grid suite in its own throwaway org and app (`CROWDY_E2E_THROWAWAY_OWNER=1`) | `crowdypy 0.5.0.dev1` from PyPI (`pip install crowdypy` in a clean Python 3.12) | 10 passed; Studio skipped |
 
 ## Not covered here
 
@@ -60,7 +61,7 @@ These CrowdyCPP suites have no CrowdyPy counterpart yet; the reason is in each r
 |---|---|
 | `e2e_billing_quotas`, `e2e_payments` | billing and payment mutations on a shared tier; CrowdyPy wraps the same documents CrowdyJS sends, covered by the unit suites |
 | `e2e_marketplace_claims` | owns a real chunk; needs a reserved coordinate and a `SELF_CLAIM` app |
-| `e2e_exec_client_halves`, `e2e_exec_gateway` | need a ck-exec mod grid and a running gateway with a connect token; the gateway client is checked against the shared frame fixture and a local server |
+| `e2e_exec_client_halves`, `e2e_exec_gateway` | need a ck-exec mod grid, or a gateway running the ck-exec demo app, for calls and subscription pushes; the open-grid suite connects to the tier's gateway and pings, and the gateway client's frames are checked against the shared fixture and a local server |
 | `e2e_cross_server` | needs a deployment with two or more replication servers reachable from the runner |
 | `e2e_agentic_studio`, `e2e_native_studio_integration` | the agent session is CrowdyJS's in-browser agent; CrowdyPy carries the policy and usage roots only |
 | `e2e_soak_two_clients`, `e2e_permission_refresh` | long-running; slated for `CROWDY_E2E_SLOW=1` suites |

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/docs/parity-matrix.md

@@ -4,8 +4,8 @@ Generated by `tools/parity/parity.py`; do not edit by hand. Classifications live
 
 ## Target
 
-- CrowdyJS: `18.1.0` at `806b14130786d5b739d6124c0c4c275f8997af15`
-- CrowdyCPP (native core): `0.55.0` at `344772ad0c2d577003c92fa30903d7fcada29940`
+- CrowdyJS: `18.2.0` at `269966d158f45749e9a563abf6032369ae0c258a`
+- CrowdyCPP (native core): `0.56.0` at `910ce23082940b570dc02f009d68d31594bd4be3`
 - schema.gql identical to CrowdyJS's: yes
 - Gate mode: strict portable parity (every portable gap is release-blocking)
 

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/native/replication.hpp

@@ -374,8 +374,7 @@ inline nb::tuple row_tuple(const NotificationBatch& b, std::size_t i) {
 
 // ------------------------------------------------------------------ the connection
 
-// Defined in replication_binding.cpp, so this header pulls in no platform socket headers
-// (<windows.h>'s far and near macros break CrowdyCPP's headers included after it).
+// Defined in replication_binding.cpp, so this header pulls in no platform socket headers.
 void write_wake(std::int64_t fd);
 void prepare_wake_fd(std::int64_t fd);
 

{crowdypy-0.5.0.dev1 → crowdypy-0.5.1.dev1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "scikit_build_core.build"
 
 [project]
 name = "crowdypy"
-version = "0.5.0.dev1"
+version = "0.5.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"
@@ -117,19 +117,19 @@ environment = { OPENSSL_ROOT_DIR = "C:/vcpkg/installed/x64-windows-static-md" }
 # --------------------------------------------------------------------------------------
 
 [tool.crowdypy.crowdyjs]
-version = "18.1.0"
-commit = "806b14130786d5b739d6124c0c4c275f8997af15"
+version = "18.2.0"
+commit = "269966d158f45749e9a563abf6032369ae0c258a"
 
 [tool.crowdypy.crowdycpp]
-version = "0.55.0"
-tag = "dev/v0.55.0"
-commit = "344772ad0c2d577003c92fa30903d7fcada29940"
-tree-sha256 = "a930e844afa86b9804a8bd8d7d5a93a830f8ef720aa798f31b6dd89d35eaa3ee"
+version = "0.56.0"
+tag = "910ce23082940b570dc02f009d68d31594bd4be3"
+commit = "910ce23082940b570dc02f009d68d31594bd4be3"
+tree-sha256 = "1e294223900a84c064ba8c50281edfe5cea2c7c2ac042d842fa5a7804ad89cd4"
 
 # schema.gql and operations/ are CrowdyJS's, copied from the commit pinned above by
 # scripts/schema_sync.py, which records these hashes and re-derives them in CI.
 [tool.crowdypy.graphql]
-schema-sha256 = "38c490a70f0bd92977fef5867e0b9e14a10d9467a2008dcd2c02bbc96878d8d3"
+schema-sha256 = "f00952f685420f6c0f4bf58d56debda29aea8cce9b877754393611393ff63db1"
 operations-sha256 = "d5e0c505589ea26ecc3398b12f02ad7bd786457f7010ad87dcb8af2ea9366c77"
 
 # The SDL the docs site publishes. scripts/schema_drift.py compares the snapshot against it