zas-agent 0.9.0 → 0.10.0

package/CHANGELOG.md

@@ -7,6 +7,32 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.10.0] - 2026-09-28
+
+### Added
+
+- Transfer telemetry. File and note sends, item downloads, and Directo sends
+  and receives (live and reliable delivery) report `transfer.started`,
+  `transfer.stage_started`, `transfer.slow` (after 30 s),
+  `transfer.phase_timing` and `transfer.finished`. Each report carries the
+  item category, the transport, byte counts, a size bucket, stage durations and
+  the outcome (success, failure or cancellation), joined by a random
+  per-attempt ID. No file name, content, path or channel name. The same
+  opt-out as `agent.tool_call` covers it. The telemetry notice names the new
+  fields.
+
+- `plan_inactive`. A send, replace or Directo transfer in an organization
+  channel whose plan is inactive now says so, and names who can reactivate
+  it. It used to arrive as `upload_failed`, which told the agent to retry.
+
+### Changed
+
+- Reports never delay or fail a tool call. The `agent.tool_call` report is
+  sent after the answer, on a later tick. Transfer events are queued, at most
+  32 per batch, and sent in one request on a later tick. A report is one
+  request with a 2 s timeout and no retry. It is skipped when there is no
+  valid session, so it never starts or refreshes a sign-in.
+
 ## [0.9.0] - 2026-09-09
 
 ### Added
@@ -333,7 +359,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   two separate identities that cannot read each other's keys.
 - Install snippets for Claude Code and Codex, printed by `zas-agent pair`.
 
-[Unreleased]: https://github.com/soke1556/zas-agent/compare/v0.9.0...HEAD
+[Unreleased]: https://github.com/soke1556/zas-agent/compare/v0.10.0...HEAD
+[0.10.0]: https://github.com/soke1556/zas-agent/compare/v0.9.0...v0.10.0
 [0.9.0]: https://github.com/soke1556/zas-agent/compare/v0.8.0...v0.9.0
 [0.8.0]: https://github.com/soke1556/zas-agent/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/soke1556/zas-agent/compare/v0.6.3...v0.7.0

package/README.md

@@ -159,8 +159,13 @@ The package refuses some of these on its own, before a request is made. The
 ones marked *(server-side)* are enforced by the Zas server.
 
 - **No channel you did not grant.** Not by name, not by id.
-- **No shared channel you merely joined, and no workspace channel.** Grants
-  exist only on channels your account owns and that no organization manages
+- **No shared channel you joined, unless its owner allows it.** You can grant
+  a channel you joined, but the grant stays `grant_pending` until that
+  channel's owner allows this agent in Zas. The plan also caps how many of
+  these channels one agent holds: 2 on Free *(server-side)*.
+- **No workspace channel, unless the organization allows agents.** A channel
+  an organization manages, or one you created inside its workspace, can be
+  granted only while the organization is active and an admin turned agents on
   *(server-side)*.
 - **No reading unless the grant says so.** `read` is a separate switch from
   `send`; without it, `zas_list_items` and `zas_get_item` are refused.
@@ -200,6 +205,7 @@ string ever reaches a terminal.
 | `agent_revoked` | The owner revoked this agent. |
 | `agent_forbidden` | Only the account owner can do that. |
 | `grant_missing` | This agent has no access to that channel. |
+| `grant_pending` | That channel belongs to somebody else, and its owner has not allowed this agent yet. |
 | `send_forbidden` | This agent cannot send to that channel. |
 | `read_forbidden` | This agent cannot read that channel. |
 | `direct_mode` | That channel is in Directo mode. |
@@ -215,6 +221,7 @@ string ever reaches a terminal.
 | `fallback_unavailable` | Reliable delivery is not available right now. |
 | `key_stale` | The channel key changed; the owner refreshes it by opening Zas. |
 | `quota_exceeded` | The account reached its storage limit. |
+| `plan_inactive` | The organization's plan is inactive, so sending to its channels is paused; the owner or a billing admin reactivates it. |
 | `rate_limited` | Too many sends in a row. |
 | `file_too_big` | The file is over the plan limit. |
 | `duplicate` | That item is already in the channel. |
@@ -228,6 +235,12 @@ string ever reaches a terminal.
 | `write_failed` | The download destination could not be written. |
 | `pairing_expired` | The pairing expired; pair again. |
 | `pairing_cancelled` | The owner cancelled the pairing. |
+| `claim_mismatch` | The code does not match. |
+| `pairing_not_approved` | Nobody has approved this pairing yet. |
+| `pairing_claimed` | This pairing was already claimed; pair again. |
+| `agent_limit` | The account cannot take another agent; the owner deletes one from Settings → Agents. |
+| `grant_limit` | The plan allows fewer channels per agent than this pairing grants. |
+| `foreign_limit` | The plan allows this agent fewer channels of other people than this pairing asks for. |
 | `feature_disabled` | Agents are not enabled for this account yet. |
 | `upload_failed` | The upload failed. |
 | `oprf_failed` | Zas did not answer correctly while preparing the file. |
@@ -306,14 +319,16 @@ covers every profile on the machine; pairing again does not reset it.
 
 What one report carries, and nothing else: the tool that ran, whether it
 worked, the closed error code when it did not, which of four duration buckets
-it fell in, and the package version. No file name, no file contents, no path,
+it fell in, and the package version. Item transfers also report item category,
+transport, byte counts, stage durations, and success/failure/cancellation, joined
+by a random per-attempt ID. No file name, no file contents, no path,
 no channel name, no error message, no stack.
 
 Where it goes: to Zas, never to an analytics service directly. This package
 holds no analytics token and opens no connection to a third party, so no
 address of yours reaches one. The report is attributed to the Zas account the
 agent is paired with, which the server reads from the session — the request
-carries no identifier of its own. Nothing is reported before pairing, because
+carries no account or content identifier. Nothing is reported before pairing, because
 until then there is no account it could belong to.
 
 A report is never allowed to matter: it is sent after the answer, waited on