@yargote/artifacts-cli 0.1.0-beta.8 → 0.1.0-beta.9

package/README.md

@@ -11,9 +11,9 @@ Use Node 24 or later. The beta targets macOS and Linux. Windows has not been ver
 Choose one persistent installation:
 
 ```sh
-npm install --global @yargote/artifacts-cli@0.1.0-beta.8
+npm install --global @yargote/artifacts-cli@0.1.0-beta.9
 # Or, with pnpm and an existing global bin directory on PATH:
-pnpm add --global @yargote/artifacts-cli@0.1.0-beta.8
+pnpm add --global @yargote/artifacts-cli@0.1.0-beta.9
 artifacts --version
 ```
 
@@ -22,8 +22,8 @@ If pnpm reports that no global bin directory exists, run `pnpm setup` and reopen
 For one-off execution, pin the same version:
 
 ```sh
-npx --yes @yargote/artifacts-cli@0.1.0-beta.8 --help
-pnpm dlx @yargote/artifacts-cli@0.1.0-beta.8 --help
+npx --yes @yargote/artifacts-cli@0.1.0-beta.9 --help
+pnpm dlx @yargote/artifacts-cli@0.1.0-beta.9 --help
 ```
 
 `@beta` follows future prereleases. Exact versions remain reproducible. No stable `latest` release is part of this beta. An organization's pnpm minimum release age or trust policy can delay a new release. Follow that policy rather than disabling it globally.
@@ -141,8 +141,7 @@ artifacts history ID [--limit N] [--before-sequence N] [--summary]
 artifacts publish ID --revision REV --expected-version N [--request-id ID]
 artifacts publish [ID] --command FILE
 artifacts export ID --revision REV --out FILE
-artifacts move ID --project NAME [--request-id ID]
-artifacts move ID --no-project [--request-id ID]
+artifacts move ID [--project NAME | --no-project] [--slug SLUG | --no-slug] [--request-id ID]
 artifacts share ID --email EMAIL [--notify] [--request-id ID]
 artifacts shares ID
 artifacts unshare ID SHARE_ID [--request-id ID]
@@ -215,7 +214,7 @@ artifacts move ARTIFACT_ID --no-project
 
 Every artifact read and list item includes `project`, a name or null. `projects` prints `{ "items": [{ "name": "Alpha", "artifactCount": 1 }] }`, ordered by name without regard to letter case. A project exists only while it contains an artifact.
 
-`move ID` requires exactly one of `--project NAME` or `--no-project`. It prints `{ "artifactId": "...", "project": "Beta" }` with the stored spelling, or `null` after `--no-project`. Move never creates a revision or changes the publication. Moving to the current project succeeds without change. Move is a retained mutation like the others, so `retry` recovers a lost response.
+`move ID` requires at least one of `--project NAME`, `--no-project`, `--slug SLUG`, or `--no-slug`, and accepts at most one from each pair. An option left out keeps that value. It prints `{ "artifactId": "...", "project": "Beta" }` with the stored spelling, or `null` after `--no-project`. Move never creates a revision or changes the publication. Moving to the current project succeeds without change. Move is a retained mutation like the others, so `retry` recovers a lost response.
 
 Version `0.1.0-beta.4` and earlier parse artifact responses strictly and fail with `invalid_response` against a server that returns `project`. Upgrade the CLI together with the server.
 
@@ -227,10 +226,14 @@ A slug names a page within its project, so `read` can find it without its ID. `c
 artifacts create --snapshot snapshot.json --project Mi-Wiki --slug concepts/rag
 artifacts read --project mi-wiki --slug concepts/rag
 artifacts read --slug index
+artifacts move ARTIFACT_ID --slug concepts/retrieval
+artifacts move ARTIFACT_ID --no-slug
 ```
 
 A slug is unique within the owner's project, matched by the project's stored spelling. Artifacts without a project share one unfiled namespace, which `read --slug` reads without `--project`. `read` takes exactly one of an ID or `--slug`, and `--project` applies only with `--slug`. A used slug fails `create` with `slug_conflict`, status 409, and the holder's `artifactId`. A locator with no artifact fails with `not_found`. Every artifact read and list item includes `slug`, a name or null. Version `0.1.0-beta.7` and earlier reject responses that include `slug` with `invalid_response`.
 
+`move ID --slug SLUG` renames a page in its project, and `move ID --no-slug` clears the slug. A move to another project keeps the slug. A move fails with `slug_conflict`, status 409, and the holder's `artifactId` when the target project already uses the target slug, and then changes nothing. A slug change creates no revision. Verify the new slug with `read`. The move result is unchanged, so published CLI versions keep working against this server.
+
 ## Share publication access
 
 These commands are available from `0.1.0-beta.6`. Check installed help for support.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yargote/artifacts-cli",
-  "version": "0.1.0-beta.8",
+  "version": "0.1.0-beta.9",
   "private": false,
   "type": "module",
   "description": "Command-line client for the Artifacts REST API.",
@@ -27,8 +27,8 @@
     "skills"
   ],
   "dependencies": {
-    "@yargote/artifacts-contracts": "0.1.0-beta.8",
-    "@yargote/artifacts-client": "0.1.0-beta.8",
+    "@yargote/artifacts-contracts": "0.1.0-beta.9",
+    "@yargote/artifacts-client": "0.1.0-beta.9",
     "openid-client": "6.8.8",
     "zod": "4.6.5"
   },

package/skills/artifacts-cli/SKILL.md

@@ -35,7 +35,7 @@ Use `edit` for partial changes that preserve omitted fields. Use `update` for a
 
 When the user names a project for new content, add `--project NAME` to `create`. Run `artifacts projects` first when an existing project may already fit. A name matching an existing project regardless of letter case joins it and keeps the stored spelling. Do not invent a project the user did not ask for. Use `list --project NAME` to find artifacts in a project.
 
-When the user names a page, add `--slug SLUG` such as `concepts/rag` to `create`, and read it later with `read --project NAME --slug SLUG`, or `read --slug SLUG` for an unfiled page, instead of listing for its ID. Omit the `.md` suffix. A `slug_conflict` error names the `artifactId` that already holds the slug in that project.
+When the user names a page, add `--slug SLUG` such as `concepts/rag` to `create`, and read it later with `read --project NAME --slug SLUG`, or `read --slug SLUG` for an unfiled page, instead of listing for its ID. Omit the `.md` suffix. A `slug_conflict` error names the `artifactId` that already holds the slug in that project. Rename a page with `move ID --slug SLUG` and clear its slug with `move ID --no-slug`. A move to another project keeps the slug, and a move into a used slug fails with `slug_conflict` without changing anything.
 
 Use `move ID --project NAME` to file an existing artifact under a project and `move ID --no-project` to remove it from one. A move changes only the project. It creates no revision and leaves the publication unchanged. It is a retained mutation, so recover an uncertain move with `retry`. Verify it with `read` or `list --project NAME`. A project disappears when its last artifact leaves it.
 

package/skills/artifacts-cli/references/commands.md

@@ -104,7 +104,7 @@ artifacts move ARTIFACT_ID --no-project
 
 A project name contains 1 to 80 characters after trimming and NFC normalization, without control characters. A name that matches an existing project regardless of letter case joins it and keeps its stored spelling. Every read and list item includes `project`, a name or null. `projects` prints `{ "items": [{ "name": "Client onboarding", "artifactCount": 1 }] }`, ordered by name without regard to letter case. A project exists only while it contains an artifact.
 
-`move` takes exactly one of `--project NAME` or `--no-project` and prints `{ "artifactId": "...", "project": "Archive" }`, or `null` for the project after `--no-project`. It creates no revision and leaves the publication unchanged. Moving to the current project succeeds without change. A lost move response is recovered with `retry REQUEST_ID` like any other retained mutation.
+`move` takes at least one of `--project NAME`, `--no-project`, `--slug SLUG`, or `--no-slug`, and at most one from each pair. It prints `{ "artifactId": "...", "project": "Archive" }`, or `null` for the project after `--no-project`. An option left out keeps that value. It creates no revision and leaves the publication unchanged. Moving to the current project succeeds without change. A lost move response is recovered with `retry REQUEST_ID` like any other retained mutation.
 
 ## Name pages with slugs
 
@@ -114,11 +114,13 @@ Check that installed help lists `--slug` before using it.
 artifacts create --snapshot snapshot.json --project "Mi wiki" --slug concepts/rag
 artifacts read --project "mi wiki" --slug concepts/rag
 artifacts read --slug index
+artifacts move ARTIFACT_ID --slug concepts/retrieval
+artifacts move ARTIFACT_ID --no-slug
 ```
 
 A slug contains 1 to 160 characters of lowercase ASCII kebab-case segments separated by `/`, such as `concepts/rag` or `index`. It is never normalized, and a trailing `.md` is rejected with a hint to remove it. A slug is unique within the owner's project, matched by the project's stored spelling. Artifacts without a project share one unfiled namespace, which `read --slug` without `--project` reads. Every read and list item includes `slug`, a name or null.
 
-`read` takes exactly one of an ID or `--slug`. `--project` applies only with `--slug`. A used slug fails `create` with `slug_conflict`, status 409, and the holder's `artifactId` in `details`. A locator with no artifact fails with `not_found`. A move keeps the slug and fails with `slug_conflict` when the destination project already uses it.
+`read` takes exactly one of an ID or `--slug`. `--project` applies only with `--slug`. A used slug fails `create` with `slug_conflict`, status 409, and the holder's `artifactId` in `details`. A locator with no artifact fails with `not_found`. `move ID --slug SLUG` renames a page in its project, and `move ID --no-slug` clears the slug. A move to another project keeps the slug unless `--slug` or `--no-slug` changes it. A move fails with `slug_conflict` and changes nothing when the target project already uses the target slug. A slug change creates no revision.
 
 ## Edit without losing retained data
 

package/src/index.js

@@ -48,8 +48,8 @@ Commands:
   publish ID --revision REV --expected-version N [--request-id ID]
   publish [ID] --command FILE
   export ID --revision REV --out FILE
-  move ID --project NAME [--request-id ID]
-  move ID --no-project [--request-id ID]
+  move ID [--project NAME | --no-project] [--slug SLUG | --no-slug]
+         [--request-id ID]
   share ID --email EMAIL [--notify] [--request-id ID]
   shares ID
   unshare ID SHARE_ID [--request-id ID]
@@ -59,10 +59,14 @@ Mutation command files contain the complete create, update, or publish JSON.
 Mutation request IDs default to a random UUID. Commands are retained before
 submission. Retry sends the exact retained command for the same server and owner.
 Projects group artifacts by name without regard to letter case. A project
-exists while it contains an artifact. Move changes the project of an artifact
-without creating a revision; --no-project removes it from its project.
+exists while it contains an artifact. Move changes the project or the slug of
+an artifact without creating a revision. It needs at least one of its four
+options. --no-project removes the artifact from its project, and --no-slug
+clears its slug. An option left out keeps that value, so a move to another
+project keeps the slug.
 A slug such as concepts/rag names an artifact within its project, or within
 the unfiled artifacts without --project. Read --slug finds it without its ID.
+Create or move fails with slug_conflict when the project already uses the slug.
 Read --out saves the returned artifact JSON. Export --out saves the ZIP.
 Read --quiet requires --out and suppresses successful JSON stdout.
 Output files are created exclusively and never overwrite an existing path.
@@ -96,7 +100,7 @@ const commandOptions = {
     edit: ['changes', 'request-id'], history: ['limit', 'before-sequence', 'summary'],
     publish: ['revision', 'expected-version', 'request-id', 'command'],
     share: ['email', 'notify', 'request-id'], shares: [], unshare: ['request-id'],
-    export: ['revision', 'out'], move: ['project', 'no-project', 'request-id'], retry: [],
+    export: ['revision', 'out'], move: ['project', 'no-project', 'slug', 'no-slug', 'request-id'], retry: [],
     skills: ['full', 'all', 'agent', 'global', 'force'],
 };
 async function jsonFile(path) {
@@ -133,7 +137,7 @@ async function main() {
             summary: { type: 'boolean' }, out: { type: 'string' }, quiet: { type: 'boolean' },
             full: { type: 'boolean' }, all: { type: 'boolean' }, agent: { type: 'string' },
             global: { type: 'boolean' }, force: { type: 'boolean' },
-            project: { type: 'string' }, 'no-project': { type: 'boolean' }, slug: { type: 'string' }, email: { type: 'string' }, notify: { type: 'boolean' },
+            project: { type: 'string' }, 'no-project': { type: 'boolean' }, slug: { type: 'string' }, 'no-slug': { type: 'boolean' }, email: { type: 'string' }, notify: { type: 'boolean' },
         },
     });
     const seen = new Set();
@@ -198,6 +202,11 @@ async function main() {
             throw new UsageError(`--${name} requires a nonnegative safe integer`);
         return Number(value);
     }
+    function cleared(name, value, clear) {
+        if (value !== undefined && clear)
+            throw new UsageError(`Specify at most one of --${name} or --no-${name}`);
+        return clear ? null : value;
+    }
     const response = values.response;
     if (response !== undefined && response !== 'full' && response !== 'compact')
         throw new UsageError('--response requires full or compact');
@@ -291,9 +300,11 @@ async function main() {
         }
         case 'move': {
             const artifactId = argument();
-            if ((values.project !== undefined) === (values['no-project'] ?? false))
-                throw new UsageError('Specify exactly one of --project NAME or --no-project');
-            return mutate({ kind: 'move', command: moveSchema.parse({ artifactId, requestId: values['request-id'] ?? randomUUID(), project: values.project ?? null }) });
+            const project = cleared('project', values.project, values['no-project']);
+            const slug = cleared('slug', values.slug, values['no-slug']);
+            if (project === undefined && slug === undefined)
+                throw new UsageError('move requires --project NAME, --no-project, --slug SLUG, or --no-slug');
+            return mutate({ kind: 'move', command: moveSchema.parse({ artifactId, requestId: values['request-id'] ?? randomUUID(), ...(project === undefined ? {} : { project }), ...(slug === undefined ? {} : { slug }) }) });
         }
         case 'share': return mutate({ kind: 'share', command: shareSchema.parse({ artifactId: argument(), requestId: values['request-id'] ?? randomUUID(), email: required('email'), ...(values.notify === undefined ? {} : { notify: values.notify }) }) });
         case 'shares': return client.listShares(listSharesSchema.parse({ artifactId: argument() }));

package/src/operations.d.ts

@@ -95,7 +95,8 @@ export declare const operationSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
     command: z.ZodObject<{
         requestId: z.ZodString;
         artifactId: z.ZodString;
-        project: z.ZodNullable<z.ZodString>;
+        project: z.ZodOptional<z.ZodNullable<z.ZodString>>;
+        slug: z.ZodOptional<z.ZodNullable<z.ZodString>>;
     }, z.core.$strict>;
     version: z.ZodLiteral<1>;
     resource: z.ZodPipe<z.ZodString, z.ZodTransform<string, string>>;