@alter-ai/cli 0.7.3 → 0.9.0

package/README.md

@@ -14,8 +14,11 @@ alter --version
 ## Sign in
 
 ```bash
-alter auth login                          # interactive browser flow
-ALTER_PAT=alter_pat_... alter apps list   # headless / CI
+alter auth login                # interactive browser flow
+alter auth login --token-stdin  # pre-minted PAT; prompts, input hidden
+
+# CI: configure a masked ALTER_PAT secret in the provider, then run normally
+alter apps list
 ```
 
 ## Commands

package/dist/cli.d.ts

@@ -62,11 +62,20 @@
  *
  * Scope: this pre-parser ONLY touches argv when the ``self-update``
  * subcommand is present. Every other subcommand sees argv verbatim.
- * The rewrite handles both ``--version <value>`` (space form) and
- * ``--version=<value>`` (equals form). A bare ``--version`` without a
- * follow-up value is LEFT ALONE — that's the legitimate "print CLI
- * version" invocation, and rewriting it to ``--to`` (which requires a
- * value) would surface a confusing error.
+ * The rewrite handles every form the legacy flag was typed in:
+ * ``--version <value>`` (space), ``--version=<value>`` (equals), and
+ * bare ``--version`` with no value.
+ *
+ * The bare form used to be left alone so Commander's program-wide
+ * ``-V/--version`` would service it as a "print CLI version" request.
+ * It no longer can: ``buildProgram`` confines each command's option
+ * scan to its own argv, so a flag typed after ``self-update`` belongs
+ * to ``self-update`` — which is what ``gh``, ``git``, ``docker``, and
+ * ``kubectl`` all do with a post-subcommand ``--version``. Rewriting
+ * the bare form keeps the deprecation path pointing operators at
+ * ``--to`` (``option '--to <version>' argument missing``) instead of
+ * dead-ending them on ``unknown option '--version'``. The CLI's own
+ * version stays one token away, at ``alter --version``.
  *
  * Returns the (possibly rewritten) argv array. Pure function modulo
  * the stderr write on rewrite; safe to call on every CLI startup.