ms-tau-sdk 1.2.6.dev2__tar.gz → 1.2.6.dev4__tar.gz

{ms_tau_sdk-1.2.6.dev2 → ms_tau_sdk-1.2.6.dev4}/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 ## Unreleased
 
+- Stopped sending `execution_context` in local-mode provider hydration. The backend never declared
+  the field on `POST /api/v1/model-provider-credentials/hydrate/` and dropped it silently;
+  authentication already distinguishes local development from runtime execution, so the request
+  carries no execution-context discriminator.
 - Moved durable Tau runtime state out of the installed package. Built-in extension state, provider
   credentials, project trust, and agent-call diagnostics now live under
   `MAINSEQUENCE_TAU_STATE_ROOT/<workspace-hash>`, defaulting to an XDG-style user state directory,
@@ -11,7 +15,6 @@
 - Made the release gate reject runtime residue. `scripts/verify_distribution.py` now holds an
   explicit allowlist of the entries and file types the package ships, and refuses any `state/`
   directory, so this class of leak fails the gate instead of shipping.
-
 - Adopted one branch and release standard. A final release is a `vX.Y.Z` tag on `main`, and the
   publish workflow refuses a tag whose commit `main` does not contain. Every push to `development`
   publishes one `X.Y.Z.devN` release automatically, after the same quality gate as `quality.yml`

{ms_tau_sdk-1.2.6.dev2 → ms_tau_sdk-1.2.6.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-tau-sdk
-Version: 1.2.6.dev2
+Version: 1.2.6.dev4
 Summary: Workspace-bound Tau application primitives for Main Sequence projects
 Project-URL: Changelog, https://github.com/mainsequence-sdk/ms-tau-sdk/blob/development/CHANGELOG.md
 Project-URL: Documentation, https://github.com/mainsequence-sdk/ms-tau-sdk/tree/development/docs
@@ -43,6 +43,7 @@ Description-Content-Type: text/markdown
   <a href="https://pypi.org/project/ms-tau-sdk/"><img src="https://img.shields.io/pypi/pyversions/ms-tau-sdk.svg" alt="Supported Python versions"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/quality.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/quality.yml/badge.svg?branch=development" alt="Quality checks"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-to-pipy.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-to-pipy.yml/badge.svg" alt="PyPI publication"></a>
+  <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-development-release.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-development-release.yml/badge.svg?branch=development" alt="Development release publication"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/issues"><img src="https://img.shields.io/github/issues/mainsequence-sdk/ms-tau-sdk.svg" alt="Open issues"></a>
 </p>
 
@@ -68,6 +69,16 @@ Add the SDK to the project that will host the agent:
 uv add ms-tau-sdk
 ```
 
+Every push to `development` also publishes one `X.Y.Z.devN` release to the same PyPI project.
+`pip` and `uv` skip development releases, so take one only on purpose:
+
+```bash
+uv add --prerelease=allow ms-tau-sdk   # or pin one exactly: uv add "ms-tau-sdk==X.Y.Z.devN"
+```
+
+See the [release process](docs/reference/releasing.md#registry-publication) for what each workflow
+publishes.
+
 Provide the runtime credential that Main Sequence assigned to the deployment:
 
 ```bash

{ms_tau_sdk-1.2.6.dev2 → ms_tau_sdk-1.2.6.dev4}/README.md

@@ -15,6 +15,7 @@
   <a href="https://pypi.org/project/ms-tau-sdk/"><img src="https://img.shields.io/pypi/pyversions/ms-tau-sdk.svg" alt="Supported Python versions"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/quality.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/quality.yml/badge.svg?branch=development" alt="Quality checks"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-to-pipy.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-to-pipy.yml/badge.svg" alt="PyPI publication"></a>
+  <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-development-release.yml"><img src="https://github.com/mainsequence-sdk/ms-tau-sdk/actions/workflows/publish-development-release.yml/badge.svg?branch=development" alt="Development release publication"></a>
   <a href="https://github.com/mainsequence-sdk/ms-tau-sdk/issues"><img src="https://img.shields.io/github/issues/mainsequence-sdk/ms-tau-sdk.svg" alt="Open issues"></a>
 </p>
 
@@ -40,6 +41,16 @@ Add the SDK to the project that will host the agent:
 uv add ms-tau-sdk
 ```
 
+Every push to `development` also publishes one `X.Y.Z.devN` release to the same PyPI project.
+`pip` and `uv` skip development releases, so take one only on purpose:
+
+```bash
+uv add --prerelease=allow ms-tau-sdk   # or pin one exactly: uv add "ms-tau-sdk==X.Y.Z.devN"
+```
+
+See the [release process](docs/reference/releasing.md#registry-publication) for what each workflow
+publishes.
+
 Provide the runtime credential that Main Sequence assigned to the deployment:
 
 ```bash

{ms_tau_sdk-1.2.6.dev2 → ms_tau_sdk-1.2.6.dev4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-tau-sdk"
-version = "1.2.6.dev2"
+version = "1.2.6.dev4"
 description = "Workspace-bound Tau application primitives for Main Sequence projects"
 readme = "README.md"
 requires-python = ">=3.13"

{ms_tau_sdk-1.2.6.dev2 → ms_tau_sdk-1.2.6.dev4}/src/ms_tau_sdk/backend/client.py

@@ -560,7 +560,6 @@ class MainSequenceClient:
                 "holder_id": holder_id,
                 "supported_provider_control_schema_versions": [1],
                 "execution_selection": selection,
-                "execution_context": "local_development",
             },
             idempotent=True,
         )