@rogatio/cli 6.6.4 → 6.7.1

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.
Files changed (3) hide show
  1. package/README.md +6 -3
  2. package/dist/node/index.js +2456 -301
  3. package/package.json +2 -1
package/README.md CHANGED
@@ -38,9 +38,10 @@ rogatio <command> [options]
38
38
  | --- | --- |
39
39
  | `rogatio edit [path]` | Launch the browser editor for `.rogatio.json`. `--port <n>` fixes the port; `--no-open` skips opening a browser. |
40
40
  | `rogatio verify [path]` | Validate a `.rogatio.json` file (schema + compiler). |
41
+ | `rogatio import requestly <export.json>` | Migrate a Requestly export into `.rogatio.json`. `--out <path>` chooses the file (default `.rogatio.json`); `--merge` appends onto an existing project; `--json` prints the report. |
41
42
  | `rogatio test [path] [url...]` | Run offline dry-run tests against `.rogatio.json`. |
42
43
  | `rogatio ai <setup\|ls\|show\|delete\|test>` | AI provider configuration. `setup` interactive; `ls` list; `show` redacted; `delete` remove; `test` connection. |
43
- | `rogatio runtime <install\|uninstall\|verify>` | Register the native-messaging host with `install --extension-id <id>` and trust the device-local CA in one **transactional** call; it needs elevated privileges (Linux `sudo`, macOS keychain authorization, Windows Administrator) and rolls back with exit `1` and `trust unsupported: <reasons>` when a capability or elevation is missing. `uninstall` removes the host manifest, the device-local CA files, and the CA trust installation (idempotent). `verify` reports whether manifest, `runtime-host` wrapper, allowed origins, and CA trust are all valid. |
44
+ | `rogatio runtime <install\|uninstall\|verify>` | Register the native-messaging host with `install` and trust the device-local CA in one **transactional** call; it needs elevated privileges (Linux `sudo`, macOS keychain authorization, Windows Administrator) and rolls back with exit `1` and `trust unsupported: <reasons>` when a capability or elevation is missing. Release users never pass `--extension-id`. That flag is only for development (a local unpacked build without the release key) and for forks. `uninstall` removes the host manifest, the device-local CA files, and the CA trust installation (idempotent). `verify` reports whether manifest, `runtime-host` wrapper, allowed origins, and CA trust are all valid, and fails when `allowed_origins` omits the release ID. Release users never pass `--extension-id` on verify either. |
44
45
  | `rogatio runtime host [path]` | Run the consolidated native-messaging host for the project (pair/authorize/body transforms over stdio). Normally launched by the browser; run manually only for debugging. `--root <dir>` overrides the confined file root; `--mock-port <n>` binds the loopback mock-response faucet. |
45
46
 
46
47
  Global options: `--help, -h` and `--version, -v`. Run `rogatio <command> --help`
@@ -72,8 +73,10 @@ rogatio runtime host .rogatio.json
72
73
  ## Local runtime
73
74
 
74
75
  ```sh
75
- # Register the native-messaging host and trust the device-local CA (needs elevation)
76
- rogatio runtime install --extension-id <id>
76
+ # Register the native-messaging host and trust the device-local CA (needs elevation).
77
+ # Release users never pass --extension-id. It is only for development
78
+ # (a local unpacked build without the release key) and for forks.
79
+ rogatio runtime install
77
80
 
78
81
  # Check manifest, runtime-host wrapper, allowed origins, and CA trust
79
82
  rogatio runtime verify