@soat/cli 0.33.0 → 0.33.1

package/dist/index.mjs

@@ -13,7 +13,7 @@ import * as os from "node:os";
 import { createHmac, timingSafeEqual } from "node:crypto";
 
 //#region package.json
-var version = "0.33.0";
+var version = "0.33.1";
 
 //#endregion
 //#region src/cli-wrappers/wrappers/formations.ts
@@ -299,22 +299,19 @@ var extractPositionalArgs = args => {
 /**
 * Coerce a raw flag value to the JSON type the spec declares for it.
 *
-* `declaredType` comes from the generated route manifest. A flag the spec
-* declares as `string` is passed through untouched — its content is data, not
-* syntax, so a value that merely *looks* like JSON (a GCP service account key
-* file in `create-secret --value`) or like a number (an account number) must
-* still arrive as a string. Coercing it produced a body the server rejects,
-* with no way to escape it from the shell.
+* A flag the spec declares as `string` is passed through untouched — its
+* content is data, not syntax, so a value that merely *looks* like JSON (a GCP
+* service account key in `create-secret --value`) or like a number must still
+* arrive as a string. Coercing it produced a body the server rejects, with no
+* way to escape it from the shell.
 *
-* The one value a string flag still coerces is the literal `null`: "set it to
-* null to clear" is the documented way to detach a nullable reference
-* (`--default_model_route_id null`, `--ai_provider_id null`), and the shell has
-* no other way to spell JSON null. The cost is that a string whose entire value
-* is `null` cannot be sent — a far rarer need than clearing a field.
+* The one exception is the literal `null`: "set it to null to clear" is the
+* documented way to detach a nullable reference and the shell has no other way
+* to spell JSON null. The cost is that a string whose entire value is `null`
+* cannot be sent.
 *
-* Every other flag keeps the permissive behavior: an undeclared type (a flag
-* the manifest has no entry for) is still sniffed, since that is the only
-* signal available.
+* Every other flag keeps the permissive behavior — an undeclared type is still
+* sniffed, since that is the only signal available.
 */
 var parseFlagValue = (value, declaredType) => {
   if (declaredType === "string") return value.trim() === "null" ? null : value;
@@ -8556,23 +8553,19 @@ var suggestionFor = args => {
   return near ? ` Did you mean --${toKebab(near)}?` : "";
 };
 /**
-* Reject an unrecognized flag **only where the server cannot catch it** — a flag
-* the CLI would otherwise append to the query string.
+* Reject an unrecognized flag **only where the server cannot catch it** — a
+* flag the CLI would otherwise append to the query string.
 *
 * An undeclared query param never reaches a check: the server ignores what it
-* does not know, so `list-agents --limitt 1` returned every row instead of one.
-* The filter failed **open**, with exit 0 and no warning, and the caller acted on
-* a superset it never asked for. The name does not survive the request, so only
+* does not know, so `list-agents --limitt 1` returned every row instead of one,
+* with exit 0 and no warning. The name does not survive the request, so only
 * the client can catch it.
 *
-* An unrecognized flag on a **write** is deliberately still forwarded. The server
-* already answers `400 VALIDATION_FAILED` naming the field (`strictFields`), and
-* that check is the authority on what a body may contain — rejecting locally
-* would front-run it, hide the real error, and make an older CLI refuse a field a
-* newer server accepts. It would also make the behavior untestable through the
-* CLI: `tests/smoke-tests.sh` asserts precisely that the server rejects
-* `update-agent --reasoning` with a 400, which a client-side refusal turns into a
-* usage error the assertion cannot read.
+* An unrecognized flag on a **write** is deliberately still forwarded. The
+* server already answers `400 VALIDATION_FAILED` naming the field, and that
+* check is the authority on what a body may contain — rejecting locally would
+* hide the real error and make an older CLI refuse a field a newer server
+* accepts. `tests/smoke-tests.sh` asserts precisely that server-side 400.
 *
 * Returns the error lines to print; empty when every flag is recognized.
 */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@soat/cli",
-  "version": "0.33.0",
+  "version": "0.33.1",
   "description": "CLI for SOAT — open-source infrastructure for production-ready AI agents.",
   "keywords": [
     "ai-agents",
@@ -22,7 +22,7 @@
   "dependencies": {
     "@inquirer/input": "^5.1.2",
     "@inquirer/password": "^5.1.1",
-    "@soat/sdk": "0.33.0",
+    "@soat/sdk": "0.33.1",
     "@ttoss/logger": "^0.8.19",
     "commander": "^15.0.0",
     "js-yaml": "^5.2.1"