@lotics/cli 0.321.35 → 0.321.37

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
@@ -65,7 +65,7 @@ something exists, read `lotics --help` § COMMANDS — the whole section, not a
65
65
  logout` revokes it server-side, and it lapses on its own after 90 idle days (each use pushes that
66
66
  out). A profile from `auth api-key` holds a key an ADMIN issued. A key created in Settings carries
67
67
  its OWN access — every app and table, or only the ones chosen on the key, so a listing that comes
68
- back short is the key's reach, not a bug — while a key created FOR a person carries that
68
+ back short is the key's reach, not a bug — while an older key created FOR a person carries that
69
69
  person's access and dies with their membership. Either is routinely also on a server and on
70
70
  other machines, so logout only forgets it locally and says so; only an admin revokes it. A profile that states no kind (saved before the field existed) is resolved against the SERVER
71
71
  and revoked only if the answer is a sign-in; a bare `--api-key` / `LOTICS_API_KEY` names no
package/README.md CHANGED
@@ -102,7 +102,7 @@ The CLI checks for updates once per day and prints a note on stderr, naming the
102
102
 
103
103
  ## Authentication
104
104
 
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; a 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.
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
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.
108
108