@yargote/artifacts-client 0.1.0-beta.7 → 0.1.0-beta.9

package/README.md

@@ -3,7 +3,7 @@
 `@yargote/artifacts-client` is a typed Fetch client for the Artifacts REST API. It depends on `@yargote/artifacts-contracts` and Zod. It does not install the artifact store or a database driver. Node 24 or later is required.
 
 ```sh
-npm install @yargote/artifacts-client@0.1.0-beta.7
+npm install @yargote/artifacts-client@0.1.0-beta.9
 ```
 
 ```ts
@@ -38,17 +38,17 @@ Every method makes one HTTP request. The client does not retry, follow redirects
 | Method | Input | Result |
 | --- | --- | --- |
 | `identity()` | None | Verified user, session, client, and scopes |
-| `create(command)` | `requestId`, complete `snapshot`, optional `project` and `response` | Artifact receipt |
+| `create(command)` | `requestId`, complete `snapshot`, optional `project`, `slug`, and `response` | Artifact receipt |
 | `list(query?)` | Optional `limit`, `cursor`, and `project` | Artifact summaries and `nextCursor` |
 | `projects()` | None | `{ items: [{ name, artifactCount }] }` |
-| `read(query)` | `artifactId`, optional `revisionId` and `response` | Artifact revision |
+| `read(query)` | Exactly one of `artifactId` or `slug` with optional `project`, optional `revisionId` and `response` | Artifact revision |
 | `update(command)` | `requestId`, `artifactId`, `expectedRevisionId`, complete `snapshot`, optional `response` | Artifact receipt |
 | `history(query)` | `artifactId`, optional `limit`, `beforeSequence`, and `response` | Revisions and `nextBeforeSequence` |
 | `publish(command)` | `requestId`, `artifactId`, `revisionId`, `expectedPublicationVersion` | Publication receipt |
 | `share(command)` | `requestId`, `artifactId`, `email`, optional `notify` and `requireNew: true` | Share receipt with optional notification disposition |
 | `listShares(query)` | `artifactId` | `{ items: Share[] }` |
 | `unshare(command)` | `requestId`, `artifactId`, `shareId` | `void` after an empty HTTP 204 |
-| `move(command)` | `requestId`, `artifactId`, `project` name or null | `{ artifactId, project }` |
+| `move(command)` | `requestId`, `artifactId`, and at least one of `project` (name or null) and `slug` (slug or null) | `{ artifactId, project }` |
 | `export(query)` | `artifactId`, `revisionId` | `{ filename, mediaType, bytes, sha256 }` |
 
 Create, read, and update accept `response: 'compact'`. The returned revision contains metadata and file summaries. Omitted response and `response: 'full'` return the complete snapshot. History accepts `response: 'summary'` or `response: 'full'`. Its page limit is ten revisions. Overloads reflect these projections in the return type.
@@ -59,6 +59,8 @@ All sharing methods require `artifacts:publish` and artifact ownership. `share`
 
 Artifact reads and list items include `project`, a name or null. A project name matches an existing project regardless of letter case and keeps its stored spelling. `move` never creates a revision or changes the publication. `projects()` lists only projects that contain artifacts, ordered by name. Because response schemas are strict, this client requires a server that returns `project`. Version `0.1.0-beta.4` and earlier reject responses from such a server with `invalid_response`.
 
+Artifact reads and list items also include `slug`, a page name or null. `read({ project, slug })` calls `GET /lookup` and `read({ artifactId })` calls `GET /artifacts/:artifactId`. An omitted `project` reads the unfiled namespace. A used slug fails `create` with an `HttpError` whose code is `slug_conflict`, status 409, and whose details name the holder's `artifactId`. Version `0.1.0-beta.7` and earlier reject responses that include `slug` with `invalid_response`. `move` sets, changes, or clears the slug: an omitted field keeps its value and `null` clears it. A move into a used slug fails with the same `slug_conflict`. The move result is unchanged, so published clients keep parsing it. Read the artifact to see its new slug.
+
 `prepareArtifactEdit(client, { artifactId, requestId, changes })` reads the current full snapshot and prepares an immutable update command. Metadata and content changes merge into that snapshot. An explicit `files` array replaces the attachments. The helper does not submit the update. Retain its exact output before sending it.
 
 ## Errors and retries

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yargote/artifacts-client",
-  "version": "0.1.0-beta.7",
+  "version": "0.1.0-beta.9",
   "private": false,
   "type": "module",
   "description": "Typed HTTP client for the Artifacts REST API.",
@@ -26,7 +26,7 @@
     "LICENSE"
   ],
   "dependencies": {
-    "@yargote/artifacts-contracts": "0.1.0-beta.7",
+    "@yargote/artifacts-contracts": "0.1.0-beta.9",
     "zod": "4.6.5"
   },
   "publishConfig": {

package/src/index.js

@@ -143,7 +143,7 @@ export function createArtifactHttpClient(options) {
         projects: () => json('/projects', 'GET', projectsResultSchema),
         read(value) {
             const { artifactId, ...parameters } = readSchema.parse(value);
-            return json(`/artifacts/${encodeURIComponent(artifactId)}${query(parameters)}`, 'GET', parameters.response === 'compact' ? compactArtifactReadSchema : artifactReadSchema);
+            return json(`${artifactId === undefined ? '/lookup' : `/artifacts/${encodeURIComponent(artifactId)}`}${query(parameters)}`, 'GET', parameters.response === 'compact' ? compactArtifactReadSchema : artifactReadSchema);
         },
         update(value) {
             const input = updateSchema.parse(value);