@lotics/cli 0.39.0 → 0.40.0

package/dist/app_commands.js

@@ -96,6 +96,7 @@ function readAppMeta(projectDir) {
         // App row's icon/theme is preserved.
         icon: pkg.lotics.icon,
         theme: pkg.lotics.theme,
+        capabilities: pkg.lotics.capabilities,
     };
 }
 function writeAppMeta(projectDir, meta) {
@@ -349,6 +350,12 @@ export async function appDeploy(client, args) {
                 // declares them (undefined ⇒ omitted ⇒ App row left untouched).
                 icon: meta.icon,
                 theme: meta.theme,
+                // Capabilities are manifest-authoritative (like workflows/queries, not
+                // like icon/theme): always send, defaulting to `{}` when the manifest
+                // declares none — so deleting the `capabilities` block turns every
+                // capability OFF on the next deploy (fail-safe; the declaration is the
+                // grant). The manifest is the only writer of capabilities.
+                capabilities: meta.capabilities ?? {},
                 // Opt into destructive workflow removal. Default false — the server
                 // rejects deploys whose manifest is missing aliases the App row has.
                 force_workflow_sync: args.forceWorkflowSync,

package/dist/client.d.ts

@@ -155,8 +155,10 @@ export declare class LoticsClient {
         offset?: number;
         sort?: AppQuerySortKey[];
         filter?: AppQueryFilter;
+        count?: boolean;
     }): Promise<{
         rows: unknown[];
+        total?: number;
     }>;
     appMembers(app_id: string, group_id?: string): Promise<{
         members: Array<{
@@ -238,6 +240,15 @@ export declare class LoticsClient {
          */
         icon?: string;
         theme?: Record<string, unknown>;
+        /**
+         * Opt-in app capabilities from `package.json#lotics.capabilities`. The CLI
+         * sends this on every deploy (defaulting to `{}`): the manifest is
+         * authoritative, so an empty/absent block turns every capability off.
+         * `comments: true` enables the members-only `useComments` primitive.
+         */
+        capabilities?: {
+            comments?: boolean;
+        };
         /**
          * Opt into destructive workflow removal. When false/absent, the server
          * rejects a deploy whose `workflows` map is missing aliases that exist

package/dist/client.js

@@ -230,6 +230,12 @@ export class LoticsClient {
         if (args.theme !== undefined) {
             formData.append("theme", JSON.stringify(args.theme));
         }
+        // capabilities is manifest-authoritative — the caller always passes it
+        // (`{}` when none declared), so a deploy turns off any capability the
+        // manifest no longer declares. JSON-encoded.
+        if (args.capabilities !== undefined) {
+            formData.append("capabilities", JSON.stringify(args.capabilities));
+        }
         // Only post the override flag when the user explicitly opts in. The
         // server defaults to "honor the guard" — opt-in is loud, opt-out
         // requires intent.

package/dist/dev/rpc_handler.js

@@ -32,6 +32,7 @@ export async function dispatchRpc(client, body) {
                 offset: p.offset,
                 sort: p.sort,
                 filter: p.filter,
+                count: p.count,
             });
         }
         case "workflow": {