lua-cli 3.51.0 → 3.52.0

package/docs/README.md

@@ -1,6 +1,6 @@
-# lua-cli v3.51.0
+# lua-cli v3.52.0
 
-Welcome to the comprehensive API documentation for lua-cli v3.51.0. This guide covers every API, class, and function exported by the package.
+Welcome to the comprehensive API documentation for lua-cli v3.52.0. This guide covers every API, class, and function exported by the package.
 
 ## 📚 Documentation Index
 
@@ -263,7 +263,7 @@ Each API doc includes:
 
 ---
 
-**Version:** 3.51.0
+**Version:** 3.52.0
 **Last Updated:** October 2026
 
 ---

package/docs/api/Data.md

@@ -318,7 +318,12 @@ const names = await map.collections();
 ### Managing shared collections (org admins)
 
 Created and managed through the admin API (`members:manage` to list, `members:assign-role` to change). Every id in
-`readers` / `writers` must be a live agent of the organization; explicit ids only, never `*`.
+`readers` / `writers` must be a live agent of the organization; explicit ids only, never `*`. On `PUT` that applies to
+ids being added: an id already on the same list is exempt, so sending the lists back as read always works. If its
+agent has been deleted it is dropped from the saved list (and named in the audit row); if it was archived or moved to
+another organization it stays, has no access while it is, and works again if the agent is restored or moved back.
+A `PUT` that races another change to the same collection answers 409 `shared_data_collection_changed`: read the
+lists again and resend.
 
 ```http
 GET    /admin/orgs/:orgId/shared-collections
@@ -327,6 +332,38 @@ PUT    /admin/orgs/:orgId/shared-collections/:name  { "readers": [...], "writers
 DELETE /admin/orgs/:orgId/shared-collections/:name  (access ends at once; entries are purged; irreversible)
 ```
 
+`installableBy` (optional on `POST` and `PUT`) lists the marketplace templates whose installs may join the collection
+by themselves, each up to a `maxAccess` of `read` or `write`:
+
+```json
+{
+  "readers": [],
+  "writers": ["<admin-agent-id>"],
+  "installableBy": [{ "templateId": "<template-id>", "maxAccess": "read" }]
+}
+```
+
+A template that is not listed never joins on its own. A `write` join also needs the installing user to hold
+`members:assign-role` on the organization. Omitting `installableBy` on `PUT` keeps the stored list; `[]` clears it.
+Changing it does not touch agents already on `readers` / `writers`.
+
+A template declares the collections its installed copies need in `lua.skill.yaml`:
+
+```yaml
+template:
+  sharedData:
+    - name: firm_admin
+      access: read # or write
+```
+
+On install the platform adds the new agent to each listed collection when an org admin has put the template on its
+`installableBy` (and, for `write`, the installing user holds `members:assign-role`). Anything else is reported as
+`needs-approval` with a reason in the install result and on the installed template's setup status; once an admin fixes
+it, `POST /agents/:agentId/templates/:templateId/setup/retry` (run by an admin for a `write` join) joins it. A template
+never creates a collection. Uninstall removes only what that install added. Changing `sharedData` in a new template
+version asks installers to consent again; the change applies on their next install or setup retry. Older lua-cli
+versions drop the section when publishing.
+
 A change applies to the next `Data.shared` call. Re-creating a deleted name starts an empty collection.
 
 ## DataEntryInstance

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lua-cli",
-  "version": "3.51.0",
+  "version": "3.52.0",
   "description": "Build, test, and deploy AI agents with custom tools, webhooks, and scheduled jobs. Features LuaAgent unified configuration, streaming chat, and batch deployment.",
   "readmeFilename": "README.md",
   "main": "dist/api-exports.js",

package/template/package.json

@@ -20,7 +20,7 @@
     "inquirer": "^12.9.6",
     "stripe": "^17.5.0",
     "js-yaml": "^4.1.0",
-    "lua-cli": "^3.51.0",
+    "lua-cli": "^3.52.0",
     "openai": "^5.23.0",
     "uuid": "^13.0.0",
     "zod": "^3.24.1"