chore: update cloudly dependency stack

Align Cloudly with the current typedserver, smartconfig, smartstate, and Docker tooling releases so builds and Docker output stay compatible with the upgraded stack.

ts_cliclient/plugins.ts

@@ -14,4 +14,4 @@ import * as qenv from '@push.rocks/qenv';
 export {
   projectinfo,
   qenv,
-}
+}

ts_cliclient/readme.md

@@ -23,7 +23,7 @@ It is not currently a full command tree for services, secrets, deployments, logs
 The package is published from `cloudly/ts_cliclient` via `tspublish.json` under the name `@serve.zone/cli` with the `servezone` binary.
 
 ```sh
-pnpm add -g @serve.zone/cli
+pnpm add --global @serve.zone/cli
 ```
 
 For local development inside the Cloudly repository, build the parent package:
@@ -56,7 +56,7 @@ When `CLOUDLY_TOKEN` is present, the CLI requests a stateful identity and asks C
 
 ## Programmatic Use
 
-The submodule exports the `runCli()` entry point and uses `CliClient` internally:
+The published submodule exports the `runCli()` entry point. For automation, most callers should use `@serve.zone/api` directly; the internal `CliClient` currently wraps `CloudlyApiClient` only to run the default cluster-list action:
 
 ```ts
 import { CloudlyApiClient } from '@serve.zone/api';

ts_cliclient/tspublish.json

@@ -11,5 +11,6 @@
     "registry.npmjs.org:public",
     "verdaccio.lossless.digital:public"
   ],
-  "bin": ["servezone"]
-}
+  "bin": ["servezone"],
+  "order": 10
+}