@carthooks/arcubase-cli 0.1.7 → 0.1.8

package/sdk-dist/docs/runtime-reference/search-and-bulk-actions.md

@@ -14,9 +14,9 @@ Use this page for:
 Use:
 
 ```bash
-arcubase rows query-entity \
+arcubase row query \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --body-file query.json
 ```
 
@@ -83,9 +83,9 @@ Archived view requires both:
 Command:
 
 ```bash
-arcubase rows query-entity \
+arcubase row query \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --query-file archived-query.json \
   --body-file archived-body.json
 ```
@@ -195,9 +195,9 @@ Rules:
 Command:
 
 ```bash
-arcubase rows query-entity-selection \
+arcubase row selection-action \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --action query \
   --body-file query-selection.json
 ```
@@ -235,9 +235,9 @@ Rules:
 Command:
 
 ```bash
-arcubase rows query-entity-selection \
+arcubase row selection-action \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --action archive \
   --body-file archive-selection.json
 ```
@@ -253,9 +253,9 @@ Rules:
 Command:
 
 ```bash
-arcubase rows query-entity-selection \
+arcubase row selection-action \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --action batch_print \
   --body-file batch-print-selection.json
 ```
@@ -280,9 +280,9 @@ Working shape:
 Command:
 
 ```bash
-arcubase entity update-entity-bulk \
+arcubase row bulk-update \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --body-file bulk-update.json
 ```
 
@@ -387,7 +387,7 @@ Get tags:
 ```bash
 arcubase-admin entity-tags get-selection-tags \
   --appId <app_id> \
-  --entityId <entity_id> \
+  --entityId <table_id> \
   --body-file get-tags.json
 ```
 
@@ -409,7 +409,7 @@ Add tags:
 ```bash
 arcubase-admin entity-tags batch-add-entity-tags \
   --appId <app_id> \
-  --entityId <entity_id> \
+  --entityId <table_id> \
   --body-file add-tags.json
 ```
 
@@ -432,7 +432,7 @@ Remove tags:
 ```bash
 arcubase-admin entity-tags batch-remove-entity-tags \
   --appId <app_id> \
-  --entityId <entity_id> \
+  --entityId <table_id> \
   --body-file remove-tags.json
 ```
 
@@ -458,37 +458,6 @@ Rules:
 
 ## Invoke batch operator
 
-Command:
-
-```bash
-arcubase entity invoke-entity-batch-operator \
-  --app-id <app_id> \
-  --entity-id <entity_id> \
-  --body-file invoke-batch-operator.json
-```
-
-Current writable shape:
-
-```json
-{
-  "id": "test-action-id",
-  "data": {
-    "action_id": "non-existent-action",
-    "policy_id": "",
-    "selection": {
-      "type": "ids",
-      "ids": [4000000127],
-      "length": 1
-    }
-  },
-  "params": {}
-}
-```
-
-Rules:
-
-- `id` is the frontend event id inside the custom action
-- `data.action_id` is the custom action id
-- `data.selection` is required
+`invoke-batch-operator` is not part of the reset CLI white list.
 - `params` is optional and should be an object
 - if the entity has no matching custom action or event, the server returns an upstream error

package/sdk-dist/docs/runtime-reference/table-lifecycle.md

@@ -2,7 +2,6 @@
 
 Use this page when the goal is:
 
-- find the target app
 - create an app
 - create a table
 - save the schema
@@ -10,12 +9,11 @@ Use this page when the goal is:
 
 The successful path is command-first:
 
-1. identify the target app
-2. create the app
-3. create the entity shell
-4. fetch the current shell
-5. save the full schema
-6. probe rows with `query-entity`
+1. create the app
+2. create the entity shell
+3. fetch the current shell
+4. save the full schema
+5. probe rows with `query-entity`
 
 Do not stop at shell creation.
 
@@ -26,20 +24,6 @@ CLI phase split:
 - the switch happens immediately after `admin-save-entity`
 - do not use `arcubase-admin` for row insert or row query
 
-## Step 0: identify the target app
-
-Command:
-
-```bash
-arcubase-admin app inventory
-```
-
-Rules:
-
-- always resolve the app first when the user refers to an existing app by name
-- do not ask for `app_id` unless there is no match or more than one match
-- do not ask for `entity_id` when creating a new table
-
 ## Step 1: create the app
 
 Command:
@@ -91,7 +75,7 @@ Command:
 ```bash
 arcubase-admin entity admin-get-entity-info \
   --app-id <app_id> \
-  --entity-id <entity_id>
+  --table-id <table_id>
 ```
 
 Use the returned shell as the base for `save-entity.json`.
@@ -110,7 +94,7 @@ Command:
 ```bash
 arcubase-admin entity admin-save-entity \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --body-file save-entity.json
 ```
 
@@ -122,17 +106,17 @@ Read before writing `save-entity.json`:
 
 After `admin-save-entity`, switch binaries:
 
-- use `arcubase rows insert-entity` for row insertion
-- use `arcubase rows query-entity` for readiness and row reads
+- use `arcubase row create` for row insertion
+- use `arcubase row query` for readiness and row reads
 
 ## Step 5: probe readiness
 
 Command:
 
 ```bash
-arcubase rows query-entity \
+arcubase row query \
   --app-id <app_id> \
-  --entity-id <entity_id> \
+  --table-id <table_id> \
   --body-file query.json
 ```
 

package/sdk-dist/docs/runtime-reference/uploads.md

@@ -6,7 +6,7 @@ The successful path is:
 
 1. run `arcubase upload <local-file>`
 2. use the returned JSON array directly as the field value
-3. insert or update the row with `arcubase rows insert-entity` or `arcubase rows update-entity-row`
+3. insert or update the row with `arcubase row create` or `arcubase row update`
 
 Do not construct `upload_id`, `assets_id`, or OSS form fields by hand.
 

package/sdk-dist/docs/runtime-reference/workflow/README.md

@@ -0,0 +1,19 @@
+# Workflow Runtime Reference
+
+This directory is reserved for future workflow runtime docs.
+
+It will follow the same single-path distribution model as entity schema docs:
+
+- Development source of truth:
+  - `misc/packages/@carthooks/arcubase-cli/docs/runtime-reference/workflow/`
+- Runtime location:
+  - `/opt/arcubase-sdk/docs/runtime-reference/workflow/`
+- Distribution path:
+  - `sdk-dist/docs/runtime-reference/workflow/`
+
+Expected coverage later:
+
+- workflow configuration lifecycle
+- real writable structure for nodes, edges, actions, and conditions
+- integration points between workflow and entity schema
+- common failure cases and debugging guidance