healthcloud-cli 3.7.6__tar.gz → 3.7.7__tar.gz

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: healthcloud-cli
-Version: 3.7.6
+Version: 3.7.7
 Summary: Command-line interface for the HealthCloud MCP gateway, generated from the shared MCP tool manifest.
 Project-URL: Issues, https://github.com/healthcloudservices/healthcloud-services/issues
 Project-URL: Repository, https://github.com/healthcloudservices/healthcloud-services
@@ -1082,9 +1082,14 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 
 - `list` emits `operation: "sessions.list"`, `data.sessions` (bounded projections
   of session ID, agent ID, operation, mode, status and audit timestamps) and a
-  `page` block (`{"kind": "limit", "limit": N, "returned_count": N,
-  "continuation": null}`). `get` emits `operation: "sessions.get"` and
-  `data.session`. The projections never include the session's protected
+  `page` block. These routes page with a limit only, so the block always says
+  which limit was in force: with `--limit N` it is
+  `{"kind": "limit", "limit": N, "returned_count": N, "continuation": null}`,
+  and without it the server's own default page was applied, which the block
+  reports as `{"kind": "server_default", "server_default_limit": 50,
+  "returned_count": N, "continuation": null}` (50 sessions, 100 messages) — so
+  a truncated page is never mistaken for a complete list. `get` emits
+  `operation: "sessions.get"` and `data.session`. The projections never include the session's protected
   `initial_prompt`, tenant or user identity, or arbitrary response fields.
 - Default `pretty` output prints `list` as a table with honest headers —
   `ID`, `AGENT ID`, `OPERATION`, `STATUS`, `EXPIRES AT` for sessions and `ID`,
@@ -1133,7 +1138,11 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 - `--initial-prompt` becomes the session's first `user` message in the same
   server transaction; `hc ams sessions messages list` shows it afterwards.
 - `--mode implement` is not available from the server yet: `create` reports one
-  `unsupported` refusal (the server answers 501) and creates nothing. A message
+  `unsupported` refusal (the server answers 501) and creates nothing, and a
+  `messages add` the server answers 501 for is the same `unsupported` refusal
+  with no message added. Both refusals report the 501 the server actually sent
+  and name implement mode as the documented reason, rather than asserting the
+  requested mode was the cause. A message
   whose `--mode` differs from its session's mode is refused by the server with
   409 and reported as one write-worded `conflict` refusal that names the
   session, mentions a mode mismatch as one possible cause, and points at
@@ -1156,9 +1165,14 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 - Reads refuse target files, root credentials or base URLs, raw output, blank or
   dot-segment session IDs, out-of-range limits, and installed SDKs without the
   session list/get and message list methods before tenant-admin login or any
-  read; `messages list` needs only `messages.list` — the write method `add` is
-  not required for the read, and `messages add` still refuses `unsupported`
-  without it. The existing `hc ams plan|show|apply|restore` tuning commands and their
+  read. `messages list` needs only `messages.list` — the write method `add` is
+  not required for the read. The writes check their own methods in the same
+  preflight — each command requires exactly the write method it calls, so
+  `create` refuses an installed SDK without `sessions.create` and `messages add`
+  one without `messages.add` before tenant-admin login and before any read or
+  write, and neither is refused for the write the other command performs. A single-object route whose 2xx body is not a JSON
+  object is refused as a `validation` error, never reported as an internal
+  failure. The existing `hc ams plan|show|apply|restore` tuning commands and their
   signatures are unchanged.
 - These session and message commands do not attach files, apply or roll back
   configuration, or send session history to a model. Plan review is its own

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/README.md

@@ -1064,9 +1064,14 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 
 - `list` emits `operation: "sessions.list"`, `data.sessions` (bounded projections
   of session ID, agent ID, operation, mode, status and audit timestamps) and a
-  `page` block (`{"kind": "limit", "limit": N, "returned_count": N,
-  "continuation": null}`). `get` emits `operation: "sessions.get"` and
-  `data.session`. The projections never include the session's protected
+  `page` block. These routes page with a limit only, so the block always says
+  which limit was in force: with `--limit N` it is
+  `{"kind": "limit", "limit": N, "returned_count": N, "continuation": null}`,
+  and without it the server's own default page was applied, which the block
+  reports as `{"kind": "server_default", "server_default_limit": 50,
+  "returned_count": N, "continuation": null}` (50 sessions, 100 messages) — so
+  a truncated page is never mistaken for a complete list. `get` emits
+  `operation: "sessions.get"` and `data.session`. The projections never include the session's protected
   `initial_prompt`, tenant or user identity, or arbitrary response fields.
 - Default `pretty` output prints `list` as a table with honest headers —
   `ID`, `AGENT ID`, `OPERATION`, `STATUS`, `EXPIRES AT` for sessions and `ID`,
@@ -1115,7 +1120,11 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 - `--initial-prompt` becomes the session's first `user` message in the same
   server transaction; `hc ams sessions messages list` shows it afterwards.
 - `--mode implement` is not available from the server yet: `create` reports one
-  `unsupported` refusal (the server answers 501) and creates nothing. A message
+  `unsupported` refusal (the server answers 501) and creates nothing, and a
+  `messages add` the server answers 501 for is the same `unsupported` refusal
+  with no message added. Both refusals report the 501 the server actually sent
+  and name implement mode as the documented reason, rather than asserting the
+  requested mode was the cause. A message
   whose `--mode` differs from its session's mode is refused by the server with
   409 and reported as one write-worded `conflict` refusal that names the
   session, mentions a mode mismatch as one possible cause, and points at
@@ -1138,9 +1147,14 @@ uv run --frozen hc ams sessions messages add --environment dev --tenant-id TENAN
 - Reads refuse target files, root credentials or base URLs, raw output, blank or
   dot-segment session IDs, out-of-range limits, and installed SDKs without the
   session list/get and message list methods before tenant-admin login or any
-  read; `messages list` needs only `messages.list` — the write method `add` is
-  not required for the read, and `messages add` still refuses `unsupported`
-  without it. The existing `hc ams plan|show|apply|restore` tuning commands and their
+  read. `messages list` needs only `messages.list` — the write method `add` is
+  not required for the read. The writes check their own methods in the same
+  preflight — each command requires exactly the write method it calls, so
+  `create` refuses an installed SDK without `sessions.create` and `messages add`
+  one without `messages.add` before tenant-admin login and before any read or
+  write, and neither is refused for the write the other command performs. A single-object route whose 2xx body is not a JSON
+  object is refused as a `validation` error, never reported as an internal
+  failure. The existing `hc ams plan|show|apply|restore` tuning commands and their
   signatures are unchanged.
 - These session and message commands do not attach files, apply or roll back
   configuration, or send session history to a model. Plan review is its own

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/healthcloud_cli/ams/context.py

@@ -2,7 +2,7 @@
 
 from __future__ import annotations
 
-from collections.abc import Callable
+from collections.abc import Callable, Sequence
 from contextlib import AbstractContextManager
 from dataclasses import dataclass
 from pathlib import Path
@@ -236,8 +236,20 @@ def preflight_policies(invocation: AmsContext, target: TenantTarget) -> None:
         sdk.close()
 
 
-def preflight_sessions(invocation: AmsContext, target: TenantTarget) -> None:
-    """Validate local session-read compatibility before login or any read."""
+def preflight_sessions(
+    invocation: AmsContext,
+    target: TenantTarget,
+    *,
+    write_methods: Sequence[str] = (),
+) -> None:
+    """Validate local session compatibility before login or any request.
+
+    ``write_methods`` names exactly the write methods the calling command will
+    call, as ``"<resource>.<method>"`` (``sessions.create``, ``messages.add``),
+    so a write command is refused here — before tenant-admin login and before any
+    read or write — only for a method it actually needs; a write it never
+    performs is never required of the installed SDK.
+    """
 
     _check_root(invocation)
     if invocation.target_file is not None:
@@ -245,12 +257,16 @@ def preflight_sessions(invocation: AmsContext, target: TenantTarget) -> None:
     sdk = _public_sdk(target.environment, target.tenant_id)
     try:
         resource = getattr(getattr(sdk, "ams_admin", None), "sessions", None)
-        if (
-            resource is None
-            or not callable(getattr(resource, "list", None))
-            or not callable(getattr(resource, "get", None))
-            or not callable(getattr(getattr(resource, "messages", None), "list", None))
-        ):
+        messages = getattr(resource, "messages", None)
+        resources = {"sessions": resource, "messages": messages}
+        required = (resource, "list"), (resource, "get"), (messages, "list")
+        missing = any(not callable(getattr(holder, method, None)) for holder, method in required)
+        for qualified in write_methods:
+            owner, _, method = qualified.partition(".")
+            holder = resources.get(owner)
+            if not method or not callable(getattr(holder, method, None)):
+                missing = True
+        if missing:
             raise click.ClickException(
                 "SDK missing ams_admin sessions; use the reviewed SDK version required by this CLI."
             )

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/healthcloud_cli/ams/sessions/commands.py

@@ -125,7 +125,7 @@ def create_create_command(dependencies: AmsDependencies) -> click.Command:
             _require_login()
             target = resolve_tenant_target(environment, tenant_id)
             target_data.update(environment=target.environment, tenant_id=target.tenant_id)
-            preflight_sessions(invocation, target)
+            preflight_sessions(invocation, target, write_methods=("sessions.create",))
             return create_session(
                 dependencies,
                 target,
@@ -561,7 +561,7 @@ def create_messages_add_command(dependencies: AmsDependencies) -> click.Command:
             _require_login()
             target = resolve_tenant_target(environment, tenant_id)
             target_data.update(environment=target.environment, tenant_id=target.tenant_id)
-            preflight_sessions(invocation, target)
+            preflight_sessions(invocation, target, write_methods=("messages.add",))
             return add_message(
                 dependencies,
                 target,

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/healthcloud_cli/ams/sessions/operations.py

@@ -25,7 +25,11 @@ from .projections import (
 )
 
 SESSION_LIMIT_MAX = 100
+# The server's own defaults when ``--limit`` is omitted: an omitted limit is a
+# real, truncating page, so the envelope reports which default was applied.
+SESSION_LIMIT_DEFAULT = 50
 MESSAGE_LIMIT_MAX = 200
+MESSAGE_LIMIT_DEFAULT = 100
 # Mirror the server's own bounds so an obviously unacceptable file is never
 # put on the wire; the server's refusal still wins when it disagrees.
 ATTACHMENT_MAX_BYTES = 5 * 1024 * 1024
@@ -562,6 +566,26 @@ def _identity(session, target: TenantTarget, session_id: str | None) -> None:
         )
 
 
+def _page(limit: int | None, server_default: int, returned: int) -> dict:
+    """The page block, honest about an omitted ``--limit``.
+
+    These routes page with a limit only: an omitted limit is not "unpaged", it
+    is the server's own default page, which can truncate the list. The block
+    therefore reports either the limit that was sent, or the server default
+    that was applied instead, so a consumer can always tell whether more rows
+    may exist.
+    """
+
+    if limit is None:
+        return {
+            "kind": "server_default",
+            "server_default_limit": server_default,
+            "returned_count": returned,
+            "continuation": None,
+        }
+    return {"kind": "limit", "limit": limit, "returned_count": returned, "continuation": None}
+
+
 def list_sessions(dependencies: AmsDependencies, target: TenantTarget, *, limit: int | None = None) -> dict:
     """`hc ams sessions list`: the caller's non-expired sessions, newest first."""
 
@@ -576,12 +600,7 @@ def list_sessions(dependencies: AmsDependencies, target: TenantTarget, *, limit:
         _target(target),
         {
             "sessions": projections,
-            "page": {
-                "kind": "limit",
-                "limit": limit,
-                "returned_count": len(projections),
-                "continuation": None,
-            },
+            "page": _page(limit, SESSION_LIMIT_DEFAULT, len(projections)),
         },
         read_only=True,
     )
@@ -653,13 +672,26 @@ def _message_conflict(error: BaseException, session_id: str) -> SessionWriteRefu
 
 
 def _not_implemented(error: BaseException, *, session: bool) -> SessionWriteRefused | None:
+    """A 501 is the server saying it does not serve this write yet.
+
+    Both routes report the 501 the server actually sent rather than asserting
+    the requested mode was the cause; implement mode is named as the documented
+    reason, not as a certainty.
+    """
+
     if getattr(error, "status_code", None) != 501:
         return None
-    what = "Sessions in" if session else "Messages in"
+    if session:
+        return SessionWriteRefused(
+            "unsupported",
+            "The server does not serve this session write yet (it answered 501, not implemented); the "
+            "write was refused and no changes were made. Implement mode is the documented reason: "
+            "implement-mode authoring is not available from this server yet.",
+        )
     return SessionWriteRefused(
         "unsupported",
-        f"{what} implement mode are not available from this server yet; the write was refused and "
-        "no changes were made.",
+        "The server does not serve this message write yet (it answered 501, not implemented); no "
+        "message was added. Implement-mode messages are not available from this server yet.",
     )
 
 
@@ -748,12 +780,7 @@ def list_messages(
         _target(target, session_id),
         {
             "messages": projections,
-            "page": {
-                "kind": "limit",
-                "limit": limit,
-                "returned_count": len(projections),
-                "continuation": None,
-            },
+            "page": _page(limit, MESSAGE_LIMIT_DEFAULT, len(projections)),
         },
         read_only=True,
     )

{healthcloud_cli-3.7.6 → healthcloud_cli-3.7.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "healthcloud-cli"
-version = "3.7.6"
+version = "3.7.7"
 description = "Command-line interface for the HealthCloud MCP gateway, generated from the shared MCP tool manifest."
 readme = "README.md"
 requires-python = ">=3.14"