@myna-sh/cli 0.2.0 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -14,6 +14,19 @@ Or run it without installing:
14
14
  npx @myna-sh/cli --help
15
15
  ```
16
16
 
17
+ ## Versioning
18
+
19
+ `@myna-sh/cli`, `@myna-sh/sdk`, and `@myna-sh/mcp` are released in lockstep: the same version number always means the same commit. This CLI bundles the matching SDK, so installing them at the same version is all that compatibility requires.
20
+
21
+ If a command in the [documentation](https://docs.myna.sh/cli/commands) is missing locally, compare versions before assuming a bug — docs.myna.sh is generated from the repository, which can be ahead of npm:
22
+
23
+ ```sh
24
+ myna --version
25
+ npm view @myna-sh/cli version
26
+ ```
27
+
28
+ The API publishes what it supports at `GET /v1/meta` (public, unauthenticated), including the oldest client release it accepts. See [versioning and compatibility](https://docs.myna.sh/platform/compatibility).
29
+
17
30
  ## Authenticate
18
31
 
19
32
  ```sh
@@ -22,6 +35,22 @@ myna login
22
35
 
23
36
  The CLI opens `app.myna.sh/device`, where you sign in with GitHub and approve the one-time device code. The resulting credential is stored in the macOS Keychain when available, otherwise in a user-only configuration file.
24
37
 
38
+ For automation, split the flow so nothing blocks on a human, and check a credential without guessing:
39
+
40
+ ```sh
41
+ myna login start --json # prints the device code and verification URL, exits
42
+ myna login poll <device-code> # add --wait to block until approved
43
+ myna auth verify --json # { credentialPresent, credentialValid, identity, ... }
44
+ ```
45
+
46
+ ## Diagnose problems
47
+
48
+ ```sh
49
+ myna doctor --origin http://localhost:5173
50
+ ```
51
+
52
+ One pass over CLI version, API reachability and compatibility, credential validity, key scopes, project access, schema drift, generated-type freshness, and browser origins. Each check reports a status and the command that fixes it; `--json` makes it a CI gate.
53
+
25
54
  ## Start a project
26
55
 
27
56
  ```sh
package/dist/main.d.ts CHANGED
@@ -1,6 +1,8 @@
1
1
  import { Command } from 'commander';
2
2
 
3
+ declare const VERSION: string;
4
+
3
5
  declare function buildProgram(): Command;
4
6
  declare function main(argv?: string[]): Promise<void>;
5
7
 
6
- export { buildProgram, main };
8
+ export { VERSION, buildProgram, main };