@gobi-ai/cli 2.0.34 → 2.0.36

package/dist/commands/utils.js

@@ -5,8 +5,17 @@ import { getSpaceSlug, getVaultSlug } from "./init.js";
 export function readStdin() {
     return readFileSync(0, "utf8");
 }
+// The global `--json` flag lives on the root program. Walk up the ancestry so
+// this works regardless of how deeply the calling command is nested (e.g. a
+// leaf under `gobi space artifact …`, not just a direct child of the program).
 export function isJsonMode(cmd) {
-    return !!cmd.parent?.opts().json;
+    let cur = cmd;
+    while (cur) {
+        if (cur.opts().json)
+            return true;
+        cur = cur.parent;
+    }
+    return false;
 }
 export function jsonOut(data) {
     console.log(JSON.stringify({ success: true, data }));
@@ -38,6 +47,89 @@ export function formatReactionChips(m) {
         .map((r) => `${r.emoji}${r.count}${r.reactedByMe ? "*" : ""}`)
         .join(" ");
 }
+// Build a userId -> name lookup from a list/feed/thread response's `mentions`
+// block. Returns an empty map when absent, so callers can pass it through
+// unconditionally and mentions just fall back to `@<id>`.
+export function buildMentionMap(resp) {
+    const map = new Map();
+    // `mentions` sits at the top level on raw list/feed responses but under
+    // `data` on unwrapped thread/topic payloads — accept either.
+    const data = resp?.data;
+    const mentions = (resp?.mentions || data?.mentions);
+    const users = mentions?.users;
+    if (Array.isArray(users)) {
+        for (const u of users) {
+            if (u && typeof u.id === "number" && typeof u.name === "string") {
+                map.set(u.id, u.name);
+            }
+        }
+    }
+    return map;
+}
+// Flatten a richText node array into a plain-text string for display. Posts
+// commonly carry an empty `content` with the real body living only in
+// `richText`, so list/feed labels go blank without this. Renders text nodes
+// verbatim, user mentions as `@<name>` (resolved via `mentions`, else `@<id>`),
+// and link nodes as their label or URL.
+export function flattenRichText(richText, mentions) {
+    if (!Array.isArray(richText))
+        return "";
+    const parts = [];
+    for (const node of richText) {
+        if (!node || typeof node !== "object")
+            continue;
+        const n = node;
+        if (typeof n.text === "string" && n.text) {
+            parts.push(n.text);
+        }
+        else if (n.type === "user") {
+            const id = n.userId;
+            const resolved = n.name ||
+                (typeof id === "number" ? mentions?.get(id) : undefined) ||
+                "";
+            parts.push(resolved ? `@${resolved.replace(/^@/, "")}` : id != null ? `@${id}` : "");
+        }
+        else if (n.type === "link") {
+            parts.push(n.text || n.url || n.href || "");
+        }
+    }
+    return parts.join("");
+}
+// Best available plain-text body for a post or reply: explicit `content` first,
+// then flattened `richText`. Empty string if neither has text.
+export function postBodyText(m, mentions) {
+    const content = m.content || "";
+    if (content.trim())
+        return content;
+    return flattenRichText(m.richText, mentions);
+}
+// Single-line display label for a post: its title, else a body snippet, else
+// "(untitled)". Falls through title -> content -> richText so titleless posts
+// (the common case) read sensibly instead of printing "null"/blank. Body
+// snippets are collapsed to one line and truncated; titles are left intact.
+export function formatPostLabel(m, mentions, maxLen = 100) {
+    const title = m.title || "";
+    if (title.trim())
+        return title;
+    const body = postBodyText(m, mentions).replace(/\s+/g, " ").trim();
+    if (!body)
+        return "(untitled)";
+    return body.length > maxLen ? body.slice(0, maxLen) + "…" : body;
+}
+// Compact one-line rendering of a reply for nested display under a post (used
+// by `list-posts`). Indented two levels so it reads as a child of the post
+// line; surfaces attachments/artifacts and reactions on the reply.
+export function formatReplyLine(r, mentions, maxLen = 200) {
+    const author = r.author?.name ||
+        `User ${r.authorId ?? "?"}`;
+    const text = postBodyText(r, mentions).replace(/\s+/g, " ").trim();
+    const body = text.length > maxLen ? text.slice(0, maxLen) + "…" : text;
+    const attach = formatAttachmentSummary(r);
+    const chips = formatReactionChips(r);
+    return (`    - [r:${r.id}] ${author}: ${body} (${r.createdAt})` +
+        (attach ? `  ${attach}` : "") +
+        (chips ? `  ${chips}` : ""));
+}
 // Classify a wire attachment the way the clients do: declared mimeType first,
 // then the media-url extension (covers rows that predate the mimeType field).
 function attachmentKind(a) {
@@ -78,9 +170,12 @@ export function formatAttachmentSummary(m) {
     }
     return `📎 ${parts.join(", ")}`;
 }
-// One line per attachment with the fetchable URL — used by `get-post` so an
-// agent can download/describe the media without re-querying in --json mode.
-export function formatAttachmentLines(m, indent = "  ") {
+// One line per attachment with a fetchable reference — a `mediaUrl` for files
+// and media, or the `artifactId` for artifacts (retrievable via
+// `gobi artifact get <id>`). Used by `get-post` and nested under posts in
+// `list-posts` so an agent can fetch/describe the data without re-querying.
+// `marker` is the bullet prefix (e.g. "-" or "📎").
+export function formatAttachmentLines(m, indent = "  ", marker = "-") {
     const attachments = m.attachments || [];
     if (!Array.isArray(attachments) || !attachments.length)
         return [];
@@ -90,11 +185,11 @@ export function formatAttachmentLines(m, indent = "  ") {
             const art = a.artifact;
             const title = art.title ? ` "${art.title}"` : "";
             const status = art.isPublished ? "published" : "unpublished";
-            return `${indent}- artifact [${art.kind}]${title} (${art.artifactId}, ${status})${art.mediaUrl ? ` — ${art.mediaUrl}` : ""}`;
+            return `${indent}${marker} artifact [${art.kind}]${title} (${art.artifactId}, ${status})${art.mediaUrl ? ` — ${art.mediaUrl}` : ""}`;
         }
         const dims = a.width && a.height ? ` ${a.width}×${a.height}` : "";
         const name = a.fileName ? ` "${a.fileName}"` : "";
         const mime = a.mimeType ? ` (${a.mimeType})` : "";
-        return `${indent}- ${kind}${name}${dims}${mime} — ${a.mediaUrl}`;
+        return `${indent}${marker} ${kind}${name}${dims}${mime} — ${a.mediaUrl}`;
     });
 }

package/dist/main.js

@@ -11,7 +11,6 @@ import { registerVaultCommand } from "./commands/vault.js";
 import { registerSenseCommand } from "./commands/sense.js";
 import { registerUpdateCommand } from "./commands/update.js";
 import { registerMediaCommand } from "./commands/media.js";
-import { registerArtifactCommand } from "./commands/artifact.js";
 const require = createRequire(import.meta.url);
 const { version } = require("../package.json");
 function hasParentOption(cmd, key) {
@@ -64,7 +63,8 @@ export async function cli() {
     registerSenseCommand(program);
     registerUpdateCommand(program);
     registerMediaCommand(program);
-    registerArtifactCommand(program);
+    // Artifact subcommands live under `gobi space` and `gobi personal` (registered
+    // by those groups), not as a top-level `gobi artifact` group.
     // Propagate helpWidth to all subcommands
     const helpWidth = process.stdout.columns || 200;
     for (const cmd of program.commands) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gobi-ai/cli",
-  "version": "2.0.34",
+  "version": "2.0.36",
   "description": "CLI client for the Gobi collaborative knowledge platform",
   "license": "MIT",
   "type": "module",

package/skills/gobi-artifact/SKILL.md

@@ -4,20 +4,38 @@ description: >-
   Gobi artifact commands for versioned creations attached to posts: create,
   revise, publish, revert, history, download, delete, get, list. An artifact
   is a human-owned creation (image, video, gif, markdown, or meeting_summary)
-  whose revisions form a draft/published tree. Use when the user wants to
-  author, version, publish, or attach an artifact to a post.
+  whose revisions form a draft/published tree. Artifacts are scoped to a space:
+  `gobi personal artifact …` (your personal space) or `gobi space artifact …`
+  (the active team space). Use when the user wants to author, version, publish,
+  or attach an artifact to a post.
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # gobi-artifact
 
-Gobi artifact commands for versioned, post-attachable creations (v2.0.34).
+Gobi artifact commands for versioned, post-attachable creations (v2.0.36).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
+## Scope: personal vs space
+
+Artifacts live in a **space** — either your **personal space** or a **team space** —
+just like posts. The commands are the same under each scope; pick the group that
+matches where the artifact should live:
+
+- `gobi personal artifact …` — your personal space (visible only to you).
+- `gobi space artifact …` — the active team space (visible to its members). The
+  space comes from `.gobi/settings.yaml` (set with `gobi space warp <slug>`) or
+  `gobi space --space-slug <slug> artifact …`.
+
+The examples below use `personal`; swap in `space` to operate on a team space.
+The by-id subcommands (`revise`, `publish`, `revert`, `history`, `download`,
+`delete`, `get`) work the same under either group — they're authorized off the
+artifact itself — but keep using the same scope you created the artifact in.
+
 ## What is an artifact?
 
 An artifact is a versioned creation that can be attached to one or more posts. Each artifact has:
@@ -25,6 +43,7 @@ An artifact is a versioned creation that can be attached to one or more posts. E
 - **kind** — one of `image | video | gif | markdown | meeting_summary`. `markdown` and `meeting_summary` carry a markdown **body**; `image`, `gif`, and `video` carry an uploaded **media file**.
 - **title** — optional display title.
 - **owner** — always a human (the calling user). Even when an agent runs the CLI, the artifact is owned by the agent's owner.
+- **scope** — the personal space or team space it lives in (set by the command group, see above).
 - **revisions** — a draft/published tree. New revisions start as `draft`; publishing one makes it the artifact's single `published` revision (at most one published per artifact). `revise --from <revisionId>` branches off an earlier revision instead of the latest, so the history can fork.
 - **metadata** — per-kind extras. For markdown kinds, `metadata.vaultSlug` is the anchor vault used to resolve `[[wikilinks]]` in the body.
 
@@ -32,12 +51,12 @@ Markdown bodies can reference vault notes with `[[wikilinks]]`. Resolution again
 
 ## Important: JSON Mode
 
-For programmatic/agent usage, always pass `--json` as a **global** option (before the subcommand):
+For programmatic/agent usage, always pass `--json` as a **global** option (before everything else):
 
 ```bash
-gobi --json artifact list --limit 20
-gobi --json artifact create --kind markdown --content "# Notes" --title "My note"
-gobi --json artifact get <artifactId>
+gobi --json personal artifact list --limit 20
+gobi --json personal artifact create --kind markdown --content "# Notes" --title "My note"
+gobi --json space artifact get <artifactId>
 ```
 
 JSON mode wraps the response as `{"success": true, "data": <artifact|revision|...>}` (or `{"success": false, "error": "..."}`).
@@ -47,7 +66,7 @@ JSON mode wraps the response as `{"success": true, "data": <artifact|revision|..
 Create a markdown artifact, attaching it to a post in the same call:
 
 ```bash
-gobi --json artifact create --kind markdown --file notes.md --title "Design notes" \
+gobi --json personal artifact create --kind markdown --file notes.md --title "Design notes" \
   --vault-slug my-vault --post-id 12345
 ```
 
@@ -56,14 +75,14 @@ The body can come from `--file <path>`, `--content <md>` inline, or stdin (`--co
 Add `--auto-attachments` (markdown kinds only) to upload any `[[wiki-linked files]]` in the body to the `--vault-slug` vault on webdrive before creating:
 
 ```bash
-gobi --json artifact create --kind markdown --file notes.md --vault-slug my-vault --auto-attachments
+gobi --json personal artifact create --kind markdown --file notes.md --vault-slug my-vault --auto-attachments
 ```
 
 Revise it (adds a new draft revision), then publish that revision:
 
 ```bash
-gobi --json artifact revise <artifactId> --file notes-v2.md --change-note "Tighten intro"
-gobi --json artifact publish <artifactId> --revision <revisionId>
+gobi --json personal artifact revise <artifactId> --file notes-v2.md --change-note "Tighten intro"
+gobi --json personal artifact publish <artifactId> --revision <revisionId>
 ```
 
 `revise --auto-attachments` reuses the artifact's stored `metadata.vaultSlug` (it GETs the artifact first), so you don't repeat `--vault-slug`.
@@ -71,8 +90,8 @@ gobi --json artifact publish <artifactId> --revision <revisionId>
 Inspect and roll back:
 
 ```bash
-gobi --json artifact history <artifactId>          # full revision tree (owner only)
-gobi --json artifact revert <artifactId> --to <revisionId>
+gobi --json personal artifact history <artifactId>          # full revision tree (owner only)
+gobi --json personal artifact revert <artifactId> --to <revisionId>
 ```
 
 ## Typical Workflow (media artifact)
@@ -80,13 +99,13 @@ gobi --json artifact revert <artifactId> --to <revisionId>
 Image / gif / video kinds upload a local file (init → PUT → create) instead of a body:
 
 ```bash
-gobi --json artifact create --kind image --file diagram.png --title "Architecture" --post-id 12345
+gobi --json personal artifact create --kind image --file diagram.png --title "Architecture" --post-id 12345
 ```
 
 Media-file size ceilings mirror post media: 5MB photos / 15MB GIFs / 512MB video, derived from the file's content type. Revise a media artifact by uploading a replacement file:
 
 ```bash
-gobi --json artifact revise <artifactId> --file diagram-v2.png --change-note "Add cache layer"
+gobi --json personal artifact revise <artifactId> --file diagram-v2.png --change-note "Add cache layer"
 ```
 
 ## Download
@@ -97,15 +116,15 @@ gobi --json artifact revise <artifactId> --file diagram-v2.png --change-note "Ad
 - media → fetches the `mediaUrl` bytes to `--out <path>` (defaults to `<artifactId>.<ext>`).
 
 ```bash
-gobi artifact download <artifactId> --out notes.md
-gobi artifact download <artifactId> --revision <revisionId> --out image.png
+gobi personal artifact download <artifactId> --out notes.md
+gobi personal artifact download <artifactId> --revision <revisionId> --out image.png
 ```
 
 ## Attaching to a post
 
-Three ways to attach an artifact, depending on what already exists:
+Three ways to attach an artifact, depending on what already exists (`<scope>` is `personal` or `space`):
 
-1. **At artifact-create time** — `gobi artifact create … --post-id <id>` attaches the new artifact to an existing post **without clobbering** its current artifacts: the CLI reads the post's current artifact attachments, appends the new id, and writes the merged set via `PATCH /posts/:id` (`artifactIds`).
+1. **At artifact-create time** — `gobi <scope> artifact create … --post-id <id>` attaches the new artifact to an existing post **without clobbering** its current artifacts: the CLI reads the post's current artifact attachments, appends the new id, and writes the merged set via `PATCH /posts/:id` (`artifactIds`).
 2. **At post-create time** — `gobi <lane> create-post … --artifact <artifactId>` attaches one or more **already-created** artifacts to the new post (`--artifact` is repeatable).
 3. **Editing an existing post** — `gobi <lane> edit-post <id> --artifact <artifactId>` sets the post's artifact attachments. Unlike `create --post-id` (which merges), the post API's `artifactIds` is a **full replacement** — pass every artifact you want on the post, since omitted ones are removed (omitting `--artifact` entirely leaves them unchanged).
 
@@ -113,15 +132,17 @@ The same artifact can be attached to **multiple posts** (it's a reusable, versio
 
 ## Available Commands
 
-- `gobi artifact create` — Create an artifact (markdown body or uploaded media). `--post-id` attaches it to a post; `--auto-attachments` (markdown) uploads `[[wikilinks]]`.
-- `gobi artifact revise` — Add a draft revision (new body or media file). `--from` branches off a specific revision.
-- `gobi artifact publish` — Publish a revision (becomes the single published revision).
-- `gobi artifact revert` — Move the published pointer to an earlier revision.
-- `gobi artifact history` — List the full revision tree (owner only).
-- `gobi artifact download` — Download a revision's content (markdown body or media bytes).
-- `gobi artifact delete` — Delete an artifact and its revision tree.
-- `gobi artifact get` — Get one artifact with its current revision.
-- `gobi artifact list` — List your artifacts (`--kind`, `--limit`).
+Under `gobi personal artifact …` (personal space) or `gobi space artifact …` (active team space):
+
+- `create` — Create an artifact (markdown body or uploaded media). `--post-id` attaches it to a post; `--auto-attachments` (markdown) uploads `[[wikilinks]]`.
+- `revise` — Add a draft revision (new body or media file). `--from` branches off a specific revision.
+- `publish` — Publish a revision (becomes the single published revision).
+- `revert` — Move the published pointer to an earlier revision.
+- `history` — List the full revision tree (owner only).
+- `download` — Download a revision's content (markdown body or media bytes).
+- `delete` — Delete an artifact and its revision tree.
+- `get` — Get one artifact with its current revision.
+- `list` — List this scope's artifacts (`--kind`, `--limit`).
 
 ## Confirm before mutating
 
@@ -134,4 +155,5 @@ Read-only commands (`get`, `list`, `history`) and `download` run without confirm
 
 ## Reference Documentation
 
-- [gobi artifact](references/artifact.md)
+- [gobi personal artifact](references/personal.md)
+- [gobi space artifact](references/space.md)

package/skills/gobi-artifact/references/personal.md

@@ -0,0 +1,42 @@
+# gobi personal
+
+```
+Usage: gobi personal [options] [command]
+
+Personal-space commands (private posts and replies visible only to you). Mirrors the `global` subcommand shape — posts/replies live in the same data model, scoped via personalSpaceUserId so they
+never surface on the public feed.
+
+Options:
+  -h, --help                       display help for command
+
+Commands:
+  artifact                         Versioned creations attached to posts, scoped to your personal space (visible only to you). Kinds: image | video | gif | markdown | meeting_summary. Always
+                                   human-owned; revisions form a draft/published tree (one published per artifact).
+  help [command]                   display help for command
+```
+
+## artifact
+
+```
+Usage: gobi personal artifact [options] [command]
+
+Versioned creations attached to posts, scoped to your personal space (visible only to you). Kinds: image | video | gif | markdown | meeting_summary. Always human-owned; revisions form a
+draft/published tree (one published per artifact).
+
+Options:
+  -h, --help                       display help for command
+
+Commands:
+  create [options]                 Create an artifact. markdown/meeting_summary kinds take a body via --file, --content, or stdin ("-"). image/gif/video kinds upload --file. Pass --post-id to attach
+                                   the new artifact to a post.
+  revise [options] <artifactId>    Add a draft revision to an artifact. New body via --file, --content, or stdin (markdown), or --file (media). Use --from to branch off a specific revision.
+  publish [options] <artifactId>   Publish a revision (becomes the artifact's single published revision).
+  revert [options] <artifactId>    Revert the artifact's published pointer to an earlier revision.
+  history <artifactId>             List the artifact's full revision tree (owner only).
+  download [options] <artifactId>  Download an artifact's content. markdown → write the body; media → fetch the bytes. Defaults to the published/latest revision; pass --revision to pick one. Writes
+                                   to --out or stdout (markdown).
+  delete <artifactId>              Delete an artifact (and its revision tree).
+  get <artifactId>                 Get one artifact with its current revision.
+  list [options]                   List this scope's artifacts (newest first).
+  help [command]                   display help for command
+```

package/skills/gobi-artifact/references/space.md

@@ -0,0 +1,42 @@
+# gobi space
+
+```
+Usage: gobi space [options] [command]
+
+Space commands (posts, replies). Space and member admin is web-UI only.
+
+Options:
+  --space-slug <spaceSlug>                    Space slug (overrides .gobi/settings.yaml)
+  -h, --help                                  display help for command
+
+Commands:
+  artifact                                    Versioned creations attached to posts, scoped to this space (visible to its members). Kinds: image | video | gif | markdown | meeting_summary. Always
+                                              human-owned; revisions form a draft/published tree (one published per artifact).
+  help [command]                              display help for command
+```
+
+## artifact
+
+```
+Usage: gobi space artifact [options] [command]
+
+Versioned creations attached to posts, scoped to this space (visible to its members). Kinds: image | video | gif | markdown | meeting_summary. Always human-owned; revisions form a draft/published
+tree (one published per artifact).
+
+Options:
+  -h, --help                       display help for command
+
+Commands:
+  create [options]                 Create an artifact. markdown/meeting_summary kinds take a body via --file, --content, or stdin ("-"). image/gif/video kinds upload --file. Pass --post-id to attach
+                                   the new artifact to a post.
+  revise [options] <artifactId>    Add a draft revision to an artifact. New body via --file, --content, or stdin (markdown), or --file (media). Use --from to branch off a specific revision.
+  publish [options] <artifactId>   Publish a revision (becomes the artifact's single published revision).
+  revert [options] <artifactId>    Revert the artifact's published pointer to an earlier revision.
+  history <artifactId>             List the artifact's full revision tree (owner only).
+  download [options] <artifactId>  Download an artifact's content. markdown → write the body; media → fetch the bytes. Defaults to the published/latest revision; pass --revision to pick one. Writes
+                                   to --out or stdout (markdown).
+  delete <artifactId>              Delete an artifact (and its revision tree).
+  get <artifactId>                 Get one artifact with its current revision.
+  list [options]                   List this scope's artifacts (newest first).
+  help [command]                   display help for command
+```

package/skills/gobi-core/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # gobi-core
 
-Core CLI commands for the Gobi collaborative knowledge platform (v2.0.34).
+Core CLI commands for the Gobi collaborative knowledge platform (v2.0.36).
 
 ## Prerequisites
 
@@ -50,7 +50,7 @@ There is **no `gobi init`** command — each setup step is its own command, and
 | Step | Command | Unlocks |
 |------|---------|---------|
 | 1. Log in | `gobi auth login` | All authenticated commands |
-| 2. Configure a vault for this directory | `gobi vault init` | Every `gobi vault …` command; also lets `artifact create --auto-attachments` resolve that vault automatically |
+| 2. Configure a vault for this directory | `gobi vault init` | Every `gobi vault …` command; also lets `<scope> artifact create --auto-attachments` resolve that vault automatically |
 | 3. Pick an active space for this directory | `gobi space warp` | Every `gobi space …` post/reply/feed command without needing `--space-slug` |
 
 After step 2 + step 3, `.gobi/settings.yaml` looks like:

package/skills/gobi-homepage/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # Gobi Homepage Developer Guide

package/skills/gobi-media/SKILL.md

@@ -10,12 +10,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # gobi-media
 
-Gobi media generation commands (v2.0.34).
+Gobi media generation commands (v2.0.36).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 

package/skills/gobi-sense/SKILL.md

@@ -7,12 +7,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # gobi-sense
 
-Gobi sense commands for activity and transcription data (v2.0.34).
+Gobi sense commands for activity and transcription data (v2.0.36).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 

package/skills/gobi-space/SKILL.md

@@ -11,12 +11,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.34"
+  version: "2.0.36"
 ---
 
 # gobi-space
 
-Gobi space, global, and personal-space posts (v2.0.34).
+Gobi space, global, and personal-space posts (v2.0.36).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 
@@ -47,9 +47,9 @@ The same applies to replies: a reply has only `--content` (no title), so do not
 
 ## Attaching artifacts (`--artifact`)
 
-Posts have no vault attribution. Both `create-post` and `edit-post` across all three scopes (`gobi space`, `gobi global`, `gobi personal`) accept `--artifact <artifactId>` (repeatable) to attach existing artifacts. On `create-post` it sets the new post's artifacts; on `edit-post` it **replaces** the post's artifact set wholesale (pass every artifact you want; omit `--artifact` to leave them unchanged). The same artifact can be attached to multiple posts — it's a reusable, versioned creation, and each post renders its currently-published revision. To author a vault-anchored document, create a markdown artifact (`gobi artifact create --kind markdown --vault-slug <slug>`) and attach it via `--artifact`. See the **gobi-artifact** skill.
+Posts have no vault attribution. Both `create-post` and `edit-post` across all three scopes (`gobi space`, `gobi global`, `gobi personal`) accept `--artifact <artifactId>` (repeatable) to attach existing artifacts. On `create-post` it sets the new post's artifacts; on `edit-post` it **replaces** the post's artifact set wholesale (pass every artifact you want; omit `--artifact` to leave them unchanged). The same artifact can be attached to multiple posts — it's a reusable, versioned creation, and each post renders its currently-published revision. To author a vault-anchored document, create a markdown artifact in the matching scope (`gobi space artifact create --kind markdown --vault-slug <slug>`, or `gobi personal artifact create …`) and attach it via `--artifact`. See the **gobi-artifact** skill.
 
-> **Wiki-link uploads moved to artifacts.** The `--auto-attachments` flag that used to upload `[[wiki-linked files]]` from a post body now lives on `gobi artifact create` / `gobi artifact revise` (markdown kinds). To publish a markdown creation with resolvable wikilinks, create a markdown artifact with `--vault-slug` + `--auto-attachments` and attach it to the post (`--post-id`). See the **gobi-artifact** skill. Before relying on wikilink resolution, confirm the anchor vault is published: `gobi --json vault status --vault-slug <slug>` should report `isPublished: true`.
+> **Wiki-link uploads moved to artifacts.** The `--auto-attachments` flag that used to upload `[[wiki-linked files]]` from a post body now lives on `gobi <scope> artifact create` / `gobi <scope> artifact revise` (markdown kinds; `<scope>` is `space` or `personal`). To publish a markdown creation with resolvable wikilinks, create a markdown artifact with `--vault-slug` + `--auto-attachments` and attach it to the post (`--post-id`). See the **gobi-artifact** skill. Before relying on wikilink resolution, confirm the anchor vault is published: `gobi --json vault status --vault-slug <slug>` should report `isPublished: true`.
 
 ## Post media + file attachments (`--attach`)
 
@@ -57,7 +57,7 @@ Posts have no vault attribution. Both `create-post` and `edit-post` across all t
 
 Mix rule (enforced client-side before upload): up to **4 photos + 4 document files** together, OR **1 GIF**, OR **1 video** — GIF and video are exclusive with everything. Size ceilings: 10MB photos, 15MB GIFs, 512MB video, 250MB document files.
 
-Use `--attach` for media/files you want shown in the post itself; use a markdown **artifact** (`gobi artifact create`) for `[[wikilinks]]`-bearing creations attached to the post.
+Use `--attach` for media/files you want shown in the post itself; use a markdown **artifact** (`gobi <scope> artifact create`, `<scope>` = `space`/`personal`) for `[[wikilinks]]`-bearing creations attached to the post.
 
 **Reading attachments back:** feed and list lines show a compact marker like `📎 2 photos, 1 file`; `get-post` prints an `Attachments (N):` block with one line per attachment — kind, original fileName, dimensions/MIME, and the fetchable CDN URL (artifact attachments show kind/title/artifactId instead). In `--json` mode the full `attachments` array is on every post/reply object.
 

package/skills/gobi-space/references/global.md

@@ -76,7 +76,7 @@ Options:
   --title <title>            Title of the post
   --content <content>        Post content (markdown supported, use "-" for stdin)
   --rich-text <richText>     Rich-text JSON array (mutually exclusive with --content)
-  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi artifact create`. (default: [])
+  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi personal artifact create`. (default: [])
   --attach <file>            Local media or document file to attach. Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv) OR 1 GIF OR 1 video. Size ceilings: 10MB photos /
                              15MB GIFs / 512MB video / 250MB files. (default: [])
   --repost-post-id <postId>  Wrap an existing top-level post as the embedded card on this new post. Composes with --content / --rich-text / --attach (the wrapping author's text + media render above
@@ -98,7 +98,7 @@ Options:
   --attach <file>          Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv)
                            OR 1 GIF OR 1 video. Size ceilings: 10MB photos / 15MB GIFs / 512MB video / 250MB files. Omit to leave attachments unchanged. (default: [])
   --artifact <artifactId>  Replace the post's artifact attachments with the given artifact(s) (existing artifact attachments are removed). Repeatable. Omit to leave them unchanged. Create artifacts
-                           with `gobi artifact create`. (default: [])
+                           with `gobi personal artifact create`. (default: [])
   -h, --help               display help for command
 ```
 

package/skills/gobi-space/references/personal.md

@@ -23,6 +23,8 @@ Commands:
   delete-reply <replyId>           Delete a reply you authored in your personal space.
   react <postId> <emoji>           Add an emoji reaction to a personal-space post or reply (idempotent). <postId> is the numeric id of a post OR a reply.
   unreact <postId> <emoji>         Remove your emoji reaction from a personal-space post or reply. <postId> is the numeric id of a post OR a reply.
+  artifact                         Versioned creations attached to posts, scoped to your personal space (visible only to you). Kinds: image | video | gif | markdown | meeting_summary. Always
+                                   human-owned; revisions form a draft/published tree (one published per artifact).
   help [command]                   display help for command
 ```
 
@@ -91,7 +93,7 @@ Options:
   --title <title>            Title of the post
   --content <content>        Post content (markdown supported, use "-" for stdin)
   --rich-text <richText>     Rich-text JSON array (mutually exclusive with --content)
-  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi artifact create`. (default: [])
+  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi personal artifact create`. (default: [])
   --attach <file>            Local media or document file to attach. Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv) OR 1 GIF OR 1 video. Size ceilings: 10MB photos /
                              15MB GIFs / 512MB video / 250MB files. (default: [])
   --repost-post-id <postId>  Wrap an existing top-level post as the embedded card on this new private post. The referenced post must be visible to you (your own personal-space post, a global-feed
@@ -113,7 +115,7 @@ Options:
   --attach <file>          Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv)
                            OR 1 GIF OR 1 video. Size ceilings: 10MB photos / 15MB GIFs / 512MB video / 250MB files. Omit to leave attachments unchanged. (default: [])
   --artifact <artifactId>  Replace the post's artifact attachments with the given artifact(s) (existing artifact attachments are removed). Repeatable. Omit to leave them unchanged. Create artifacts
-                           with `gobi artifact create`. (default: [])
+                           with `gobi personal artifact create`. (default: [])
   -h, --help               display help for command
 ```
 
@@ -188,3 +190,29 @@ Remove your emoji reaction from a personal-space post or reply. <postId> is the
 Options:
   -h, --help  display help for command
 ```
+
+## artifact
+
+```
+Usage: gobi personal artifact [options] [command]
+
+Versioned creations attached to posts, scoped to your personal space (visible only to you). Kinds: image | video | gif | markdown | meeting_summary. Always human-owned; revisions form a
+draft/published tree (one published per artifact).
+
+Options:
+  -h, --help                       display help for command
+
+Commands:
+  create [options]                 Create an artifact. markdown/meeting_summary kinds take a body via --file, --content, or stdin ("-"). image/gif/video kinds upload --file. Pass --post-id to attach
+                                   the new artifact to a post.
+  revise [options] <artifactId>    Add a draft revision to an artifact. New body via --file, --content, or stdin (markdown), or --file (media). Use --from to branch off a specific revision.
+  publish [options] <artifactId>   Publish a revision (becomes the artifact's single published revision).
+  revert [options] <artifactId>    Revert the artifact's published pointer to an earlier revision.
+  history <artifactId>             List the artifact's full revision tree (owner only).
+  download [options] <artifactId>  Download an artifact's content. markdown → write the body; media → fetch the bytes. Defaults to the published/latest revision; pass --revision to pick one. Writes
+                                   to --out or stdout (markdown).
+  delete <artifactId>              Delete an artifact (and its revision tree).
+  get <artifactId>                 Get one artifact with its current revision.
+  list [options]                   List this scope's artifacts (newest first).
+  help [command]                   display help for command
+```

package/skills/gobi-space/references/space.md

@@ -144,7 +144,7 @@ Options:
   --title <title>            Title of the post
   --content <content>        Post content (markdown supported, use "-" for stdin)
   --rich-text <richText>     Rich-text JSON array (mutually exclusive with --content)
-  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi artifact create`. (default: [])
+  --artifact <artifactId>    Attach an existing artifact to the post (repeatable). Create artifacts with `gobi space artifact create`. (default: [])
   --space-slug <spaceSlug>   Space slug (overrides .gobi/settings.yaml)
   --attach <file>            Local media or document file to attach. Repeatable. Mix rule: up to 4 photos + up to 4 document files (pdf/md/txt/csv) OR 1 GIF OR 1 video. Size ceilings: 10MB photos /
                              15MB GIFs / 512MB video / 250MB files. (default: [])
@@ -170,7 +170,7 @@ Options:
   --attach <file>           Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. Mix rule: up to 4 photos + up to 4 document files
                             (pdf/md/txt/csv) OR 1 GIF OR 1 video. Size ceilings: 10MB photos / 15MB GIFs / 512MB video / 250MB files. Omit to leave attachments unchanged. (default: [])
   --artifact <artifactId>   Replace the post's artifact attachments with the given artifact(s) (existing artifact attachments are removed). Repeatable. Omit to leave them unchanged. Create artifacts
-                            with `gobi artifact create`. (default: [])
+                            with `gobi space artifact create`. (default: [])
   -h, --help                display help for command
 ```