ms-tau-sdk 2.0.14.dev57__tar.gz → 2.0.14.dev59__tar.gz

{ms_tau_sdk-2.0.14.dev57 → ms_tau_sdk-2.0.14.dev59}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-tau-sdk
-Version: 2.0.14.dev57
+Version: 2.0.14.dev59
 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
@@ -139,12 +139,6 @@ and call the platform or another platform application with `platform_client()`,
 person's delegation by default while the turn serves one; neither exposes a proof or a token. See
 the [public API](docs/reference/public-api.md#current_requester-and-platform_client).
 
-Job-hosted batch execution is an [accepted design](docs/adrs/0015-job-hosted-batch-execution.md)
-with implementation pending. It will run this SDK's configured Tau composition for one assignment
-inside a project Job, close it, and exit without starting Uvicorn. The Job continues to own its
-status and logs. See the [batch guide](docs/guides/job-hosted-batch-execution.md) for the target
-Python integration; the current release does not expose that batch API.
-
 ## Local development without platform sessions
 
 Local mode runs the same workspace Tau runtime without registering an Agent or AgentSession. The
@@ -305,8 +299,8 @@ Kubernetes manifest, runtime image, executor bundle, or container-publication pi
 consuming project owns its dependency lock, deployable artifact, system dependencies, project
 code, prompts, skills, hooks, and extensions.
 
-The project identity and migration are defined by
-[ADR 56](./docs/adrs/adr-56-main-sequence-tau-sdk-workspace-bound-library-deployment.md). See the
+The project identity is defined by
+[ADR 0001](./docs/adrs/0001-workspace-bound-python-sdk.md). See the
 [quickstart](./docs/getting-started/quickstart.md), [documentation index](./docs/README.md), and
 [release guide](./docs/reference/releasing.md) for the complete contracts.
 
@@ -315,12 +309,12 @@ The project identity and migration are defined by
 The repository uses Python 3.13 and `uv`:
 
 ```bash
-uv sync --frozen
+uv sync --frozen --extra tau-board
 uv run pytest
-uv run ruff check .
-uv run mypy
 ```
 
+[Testing and release gates](docs/reference/testing.md) lists every check CI runs.
+
 Releases are immutable, and a merge to `main` is the release. Merging `development` into `main`
 builds and verifies the wheel and source distribution of the version `pyproject.toml` declares,
 publishes them to PyPI through OIDC trusted publishing, and tags the merge—for example, `v1.0.0`.

{ms_tau_sdk-2.0.14.dev57 → ms_tau_sdk-2.0.14.dev59}/README.md

@@ -106,12 +106,6 @@ and call the platform or another platform application with `platform_client()`,
 person's delegation by default while the turn serves one; neither exposes a proof or a token. See
 the [public API](docs/reference/public-api.md#current_requester-and-platform_client).
 
-Job-hosted batch execution is an [accepted design](docs/adrs/0015-job-hosted-batch-execution.md)
-with implementation pending. It will run this SDK's configured Tau composition for one assignment
-inside a project Job, close it, and exit without starting Uvicorn. The Job continues to own its
-status and logs. See the [batch guide](docs/guides/job-hosted-batch-execution.md) for the target
-Python integration; the current release does not expose that batch API.
-
 ## Local development without platform sessions
 
 Local mode runs the same workspace Tau runtime without registering an Agent or AgentSession. The
@@ -272,8 +266,8 @@ Kubernetes manifest, runtime image, executor bundle, or container-publication pi
 consuming project owns its dependency lock, deployable artifact, system dependencies, project
 code, prompts, skills, hooks, and extensions.
 
-The project identity and migration are defined by
-[ADR 56](./docs/adrs/adr-56-main-sequence-tau-sdk-workspace-bound-library-deployment.md). See the
+The project identity is defined by
+[ADR 0001](./docs/adrs/0001-workspace-bound-python-sdk.md). See the
 [quickstart](./docs/getting-started/quickstart.md), [documentation index](./docs/README.md), and
 [release guide](./docs/reference/releasing.md) for the complete contracts.
 
@@ -282,12 +276,12 @@ The project identity and migration are defined by
 The repository uses Python 3.13 and `uv`:
 
 ```bash
-uv sync --frozen
+uv sync --frozen --extra tau-board
 uv run pytest
-uv run ruff check .
-uv run mypy
 ```
 
+[Testing and release gates](docs/reference/testing.md) lists every check CI runs.
+
 Releases are immutable, and a merge to `main` is the release. Merging `development` into `main`
 builds and verifies the wheel and source distribution of the version `pyproject.toml` declares,
 publishes them to PyPI through OIDC trusted publishing, and tags the merge—for example, `v1.0.0`.

{ms_tau_sdk-2.0.14.dev57 → ms_tau_sdk-2.0.14.dev59}/pyproject.toml

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

{ms_tau_sdk-2.0.14.dev57 → ms_tau_sdk-2.0.14.dev59}/src/ms_tau_sdk/agent_skills/tau_security_and_access/SKILL.md

@@ -178,7 +178,13 @@ What makes it safe:
 
 A delegated read returns anything the person can view in the Agent's Environment: what they
 created and what others shared with them, directly or through a team. This holds for Secrets and
-every other object. The platform enforces sharing; which of those objects a tool uses is part of
+other shared resources. Ordinary Teams use explicit membership: the creator is added once and
+can be removed; current Organization admins are protected writer members. Removing the admin
+role keeps membership and writer access but ends protection. Only Organization admins manage
+membership, and managing a workload that created a Team does not grant Team control. A Team's
+members still receive the resources shared with it. The Full directory remains unchanged.
+See the SDK Security and access guide's **Teams and membership** section for platform rollout.
+The platform enforces sharing; which of those objects a tool uses is part of
 the tool's design. For Secrets, the naming convention states that design:
 
 - **A personal credential:** a name tied to the person, such as `QUOTES_API_KEY__<person uid>`.