@lotics/cli 0.205.1 → 0.205.2

package/AGENTS.md

@@ -95,12 +95,15 @@ response there is *not* evidence the subcommand is absent. To find out whether s
   findings. An unrecognized status exits 0 — the list is an allowlist of failure, so a status added
   later never turns a working script red — and a parked run (`awaiting_input`) is not a failure.
 - **An app that PUBLISHES an API turns every later manifest write into a release.** `lotics app api
-  publish` snapshots what the app's queries and workflows promise to callers outside it — a
+  publish` snapshots what the app's queries, workflows and agents promise to callers outside it — a
   customer's own site or server, which nobody here can redeploy. From then on an additive change
   re-snapshots silently and a breaking one is REFUSED, naming each change;
-  `--acknowledge-breaking-api` (on `app deploy`, `app query set`, `app workflow set`, `app upgrade`)
-  is the answer that carries it out and snapshots the break as a new contract version. An app that
-  publishes nothing is untouched by any of it.
+  `--acknowledge-breaking-api` (on `app deploy`, `app query set`, `app workflow set`,
+  `app agent set`, `app upgrade`) is the answer that carries it out and snapshots the break as a new
+  contract version. An app that publishes nothing is untouched by any of it.
+- **Exposure is per app, all or nothing** — a public share or a key reaches every alias an app
+  declares, so what outsiders may call is a second app over the same tables, scaffolded with
+  `lotics app create "<name>" --api` ([docs/building_an_app.md](./docs/building_an_app.md) § 9).
 - **`--print-created` / `--cleanup` on any call that reports `side_effects`.** The first prints the
   records created plus a paste-ready cleanup plan and what cannot be auto-undone; the second runs
   those deletes (records only — never files, integrations or notifications). Neither is a rollback.

package/README.md

@@ -341,6 +341,8 @@ lotics knowledge rm kdc_...                                   # archive
 ```bash
 # Scaffold / pull / deploy a Vite+React+TS app project
 lotics app create "Sales Desk"            # scaffold + deploy v1
+lotics app create "Orders API" --api       # no screens: its declarations are the whole surface,
+                                           # so nothing is built and nothing is deployed
 lotics app pull app_...                    # bootstrap an existing app locally (incl. .lotics/*)
 lotics app deploy -m "Add quote drawer"    # typecheck + build + upload a new version
 lotics app versions                        # deploy history: version, when, who, -m message (* = live)
@@ -353,13 +355,14 @@ lotics app versions app_...                # ...for any app, without pulling it
 lotics app upgrade                         # the app this directory's manifest names
 lotics app upgrade app_...                 # ...for any app, without pulling it first
 
-# The app's API: what its declared queries and workflows promise to a caller
-# OUTSIDE the app — a customer's own site or server. Publishing snapshots that
-# promise as a numbered contract; from then on a manifest write that would break
-# it is refused and every breaking change is named, unless the write carries
+# The app's API: what its declared queries, workflows and agents promise to a
+# caller OUTSIDE the app — a customer's own site or server. Publishing snapshots
+# that promise as a numbered contract; from then on a manifest write that would
+# break it is refused and every breaking change is named, unless the write carries
 # --acknowledge-breaking-api (app deploy / app query set / app workflow set /
-# app upgrade). A query that does not name the columns it returns is refused at
-# publish: those field names are the table's, not the app's to promise.
+# app agent set / app upgrade). A query that does not name the columns it returns
+# is refused at publish: those field names are the table's, not the app's to
+# promise.
 lotics app api publish                     # snapshot the contract; prints the version + warnings
 lotics app api status                      # is one published, and which version callers hold
 lotics app api spec -o api.openapi.json    # the OpenAPI 3.1 document, for the consumer's generator