@@ -113,46 +113,72 @@ also accepts its singular form: for example, `sim table list`,
113113spellings.
114114
115115``` bash
116- sim workflows list [--folder < id> ] [--deployed] [--limit < n> ]
116+ sim workflows ls [--folder < /path> ] [--search < text> ] [--limit < n> ]
117+ sim workflows list [--folder < /path> ] [--deployed-only] [--limit < n> ]
117118sim workflows get < id>
119+ sim workflows mv < id> --folder < /path>
118120sim workflows deploy| undeploy| rollback < id>
119121
120122sim logs list [--level error] [--workflow < id> …] [--trigger < name> …] [--start < date> ]
121123sim logs get < id>
122124sim logs execution < executionId>
123125
124- sim tables list
126+ sim tables ls [--folder < /path> ] [--search < text> ] [--limit < n> ]
127+ sim tables list [--folder < /path> ]
125128sim tables get < tableId>
129+ sim tables mv < tableId> --folder < /path>
126130sim tables columns < tableId>
127131sim tables rows list < tableId> [--limit < n> ]
128132sim tables rows query < tableId> [--filter < json> ] [--sort < json> ] [--limit < n> ]
129133sim tables upsert < tableId> --data < json>
130134sim tables rows batch-delete < tableId> (--row < id> … | --filter < json> ) --yes
131135
132- sim files list
133- sim files create --name < name> [--content < value> ] [--encoding utf-8| base64]
134- sim files upload < path> [--name < name> ] [--folder-id < id> ]
136+ sim files ls [--folder < /path> ] [--search < text> ] [--limit < n> ]
137+ sim files list [--folder < /path> ]
138+ sim files get < fileId>
139+ sim files create --name < name> [--folder < /path> ] [--content < value> ] [--encoding utf-8| base64]
140+ sim files upload < path> [--name < name> ] [--folder < /path> ]
135141sim files download < fileId> [-o < path> ]
136- sim files move [ --file-ids < id> …] [--folder-ids < id > …] [--target-folder-id < id > ]
137- sim files batch-archive [ --file-ids < id> …] [--folder-ids < id > …] --yes
142+ sim files mv --file-ids < id> … [--to < /path > ]
143+ sim files batch-delete --file-ids < id> … --yes
138144sim files delete < fileId>
139145
140- sim knowledge list
146+ sim knowledge ls [--folder < /path> ] [--search < text> ] [--limit < n> ]
147+ sim knowledge list [--folder < /path> ]
141148sim knowledge get < id>
149+ sim knowledge mv < id> --folder < /path>
142150sim knowledge documents < id> [--search < text> ]
143151sim knowledge documents upload < id> < path> [--tag < value> ...]
144152sim knowledge search --query < text> --kb < id> … [--search-mode vector| hybrid]
145153```
146154
155+ ` ls ` is a directory view: it combines the resources at ` --folder ` with that
156+ folder's direct child folders. Its ` ref ` column is the resource ID or canonical
157+ folder path to pass to the next command. Use ` list ` when you want resources only,
158+ or ` folders ls ` when you want folders only.
159+
160+ Each folder-backed resource has the same path commands:
161+
162+ ``` bash
163+ sim tables folders ls --parent /Reports
164+ sim tables folders create /Reports/Quarterly
165+ sim tables folders mv /Reports/Quarterly /Archive/Quarterly
166+ sim tables folders delete /Archive/Quarterly --recursive false --yes
167+ ```
168+
169+ Replace ` tables ` with ` files ` , ` workflows ` , or ` knowledge ` . Paths are canonical,
170+ start with ` / ` , and use ` / ` for root. A slash that belongs to a folder name is
171+ percent-encoded as ` %2F ` rather than treated as a separator.
172+
147173### List inputs
148174
149175Primitive lists take space-separated values. Prefix a path with ` @ ` to read
150176one value per line, or use ` @- ` to read the list from stdin.
151177
152178``` bash
153- sim files move --file-ids file_1 file_2 --target-folder-id folder_1
154- sim files move --file-ids @file-ids.txt --target-folder-id folder_1
155- printf ' file_1\nfile_2\n' | sim files move --file-ids @- --target-folder-id folder_1
179+ sim files mv --file-ids file_1 file_2 --to /Archive
180+ sim files mv --file-ids @file-ids.txt --to /Archive
181+ printf ' file_1\nfile_2\n' | sim files mv --file-ids @- --to /Archive
156182```
157183
158184Arrays of objects remain JSON inputs because they cannot be represented as a
0 commit comments