@lotics/cli 0.321.37 → 0.321.39

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/AGENTS.md CHANGED
@@ -52,7 +52,7 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
52
52
  (`lotics → <org> / <workspace>`); read it back before trusting a write. Resolution precedence is
53
53
  in README § Organizations.
54
54
  - **A machine with no key can still sign in, and the sign-in never blocks you.** `lotics auth
55
- login <email>` prints the page a person opens (also mailed) and the code that page must show,
55
+ login` takes no argument and sends no mail: it prints the page a person opens and the code that page must show,
56
56
  records the request, and EXITS. They press Confirm whenever they get to it; the next command that
57
57
  NEEDS a credential collects the key before doing its own work, so "sign in" costs you one command
58
58
  and then re-running what you wanted. Never wrap it in a timeout waiting for a human — `--wait`
@@ -76,12 +76,12 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
76
76
  reads inside a workspace the key reaches, runs as before, while managing people, sharing or
77
77
  ownership, creating or deleting a workspace, changing workspace settings, setting credit limits,
78
78
  reading the access log and publishing an app's API answer `403` and name the remedy: an admin signed in, so
79
- `lotics auth login <email>` and run it again. A sign-in acts as that person and is refused none of
79
+ `lotics auth login` and run it again. A sign-in acts as that person and is refused none of
80
80
  them. Do not retry a `403` with the same credential and do not ask for a wider key — no answer on
81
81
  the key's own screen grants this.
82
82
  - **A 401 names its remedy — act on the hint, do not retry.** "This credential expired / was
83
83
  revoked / belongs to a member who is no longer active" carries the one remedy that ends this
84
- credential: run `lotics auth login <email>` for a sign-in, or ask the admin who issued it for a
84
+ credential: run `lotics auth login` for a sign-in, or ask the admin who issued it for a
85
85
  new key. A credential minted before that was recorded carries BOTH, because nothing on the row
86
86
  tells them apart — so on a box with no browser, take the second. Only an UNRECOGNIZED key gets
87
87
  the generic "Invalid or disabled API key", and that one is generic on purpose, so re-sending it
package/README.md CHANGED
@@ -104,7 +104,7 @@ The CLI checks for updates once per day and prints a note on stderr, naming the
104
104
 
105
105
  **Two kinds of credential, and which you hold decides what `logout` does.** `auth signup` / `auth login` give this machine a **sign-in** — it acts as you, carries whatever role you have, and is yours to see and revoke at Settings → Security → *Keys and terminals*; it lapses after 90 days of disuse, and each use pushes that out. `auth api-key` saves an **API key** an admin issued. A key an admin creates in Settings has its own name and its own access, reaching either every app and table or only the ones chosen on the key; an older key created FOR a person carries that person's access and stops working when that person is removed. Either kind often lives on a server and on other people's machines too, and only an admin revokes it. `lotics auth whoami` prints which kind this machine holds — from the saved profile, or from the server when the profile does not say.
106
106
 
107
- When a credential stops working the refusal says which of the three ways it is dead — "… was revoked." / "… expired." / "… belongs to a member who is no longer active in this organization." — and its `hint` names the remedy: `lotics auth login <email>` for a terminal sign-in, ask an admin for a new key for an API key. A credential whose record does not say which of the two it is gets both. A key the server does not recognize at all gets one generic answer, deliberately: an unrecognized key learns nothing from being refused.
107
+ When a credential stops working the refusal says which of the three ways it is dead — "… was revoked." / "… expired." / "… belongs to a member who is no longer active in this organization." — and its `hint` names the remedy: `lotics auth login` for a terminal sign-in, ask an admin for a new key for an API key. A credential whose record does not say which of the two it is gets both. A key the server does not recognize at all gets one generic answer, deliberately: an unrecognized key learns nothing from being refused.
108
108
 
109
109
  **`lotics auth signup`** — Creates a new Lotics account, organization, workspace, and API key in one step. Sends a magic link email so you can access the web app.
110
110
 
@@ -113,15 +113,15 @@ lotics auth signup # interactive prompts
113
113
  lotics auth signup a@b.com --name "Agent" # non-interactive
114
114
  ```
115
115
 
116
- **`lotics auth login`** — Signs in an account that already exists, on a new machine or to add another organization to one that holds a key (the one you pick becomes active). **It does not wait for you.** It prints the page to open (also mailed to you) and the code that page must show, then exits. Sign in there if asked, check the code, press Confirm — and run whatever you wanted to run: the next command that needs a credential collects the key before doing its own work.
116
+ **`lotics auth login`** — Signs in an account that already exists, on a new machine or to add another organization to one that holds a key (the one you pick becomes active). **It does not wait for you.** It takes no argument and sends no mail: it prints the page to open and the code that page must show, then exits. Sign in there if asked, check the code, pick the organization, press Confirm — and run whatever you wanted to run: the next command that needs a credential collects the key before doing its own work.
117
117
 
118
118
  ```bash
119
- lotics auth login a@b.com # prints the page + code, exits — nothing to keep open
119
+ lotics auth login # prints the page + code, exits — nothing to keep open
120
120
  # …press Confirm in the browser…
121
121
  lotics auth whoami # picks up the key, then answers
122
122
 
123
- lotics auth login a@b.com --wait # one command instead: holds the terminal until Confirm
124
- lotics auth login a@b.com --local # pins this directory to that org (implies --wait)
123
+ lotics auth login --wait # one command instead: holds the terminal until Confirm
124
+ lotics auth login --local # pins this directory to that org (implies --wait)
125
125
  ```
126
126
 
127
127
  A command run before you press Confirm names the page and the code again and exits 1; the request is good for 15 minutes, after which the next command says to ask again. Re-running `auth login` is always safe — it replaces the request, so only the newest code is the live one.