@gobi-ai/cli 2.0.28 → 2.0.30

package/.claude-plugin/marketplace.json

@@ -4,12 +4,12 @@
     "name": "gobi-ai"
   },
   "description": "Claude Code plugin for the Gobi collaborative knowledge platform CLI",
-  "version": "2.0.28",
+  "version": "2.0.30",
   "plugins": [
     {
       "name": "gobi",
       "description": "Manage the Gobi collaborative knowledge platform from the command line. Publish vault profiles, create posts and replies, generate images and videos.",
-      "version": "2.0.28",
+      "version": "2.0.30",
       "author": {
         "name": "gobi-ai"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gobi",
   "description": "Manage the Gobi collaborative knowledge platform from the command line",
-  "version": "2.0.28",
+  "version": "2.0.30",
   "author": {
     "name": "gobi-ai"
   },

package/dist/attachments.js

@@ -4,6 +4,7 @@ import { basename, join, extname, isAbsolute, resolve } from "path";
 import ignore from "ignore";
 import { WEBDRIVE_BASE_URL } from "./constants.js";
 import { apiPost } from "./client.js";
+import { normalizeSyncPattern } from "./commands/sync.js";
 // Best-effort extension → MIME mapping. Anything we don't recognize falls
 // back to `application/octet-stream`; the backend caps size per content-type
 // tier (5MB photos / 15MB GIFs / 512MB video) so it's the authority on what's
@@ -129,8 +130,9 @@ function addToLocalSyncfiles(gobiDir, filePath) {
     if (isPathCovered(filePath, patterns))
         return;
     const syncfilesPath = join(gobiDir, "syncfiles");
-    appendFileSync(syncfilesPath, `${EOL}${filePath}`);
-    console.log(`Added to syncfiles: ${filePath}`);
+    const pattern = normalizeSyncPattern(filePath);
+    appendFileSync(syncfilesPath, `${EOL}${pattern}`);
+    console.log(`Added to syncfiles: ${pattern}`);
 }
 export async function uploadAttachments(vaultSlug, links, token, options) {
     const addToSyncfiles = options?.addToSyncfiles ?? false;

package/dist/commands/global.js

@@ -235,13 +235,16 @@ export function registerGlobalCommand(program) {
         .option("--content <content>", "New content (markdown supported, use \"-\" for stdin)")
         .option("--rich-text <richText>", "Rich-text JSON array (mutually exclusive with --content)")
         .option("--attach <file>", "Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size ceilings: 5MB photos / 15MB GIFs / 512MB video. Omit to leave attachments unchanged.", (value, prev = []) => [...prev, value], [])
+        .option("--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`.", (value, prev = []) => [...prev, value], [])
         .action(async (postId, opts) => {
         const wantsAttachChange = !!(opts.attach && opts.attach.length > 0);
+        const wantsArtifactChange = !!(opts.artifact && opts.artifact.length > 0);
         if (opts.title == null &&
             opts.content == null &&
             opts.richText == null &&
-            !wantsAttachChange) {
-            throw new Error("Provide at least --title, --content, --rich-text, or --attach to update.");
+            !wantsAttachChange &&
+            !wantsArtifactChange) {
+            throw new Error("Provide at least --title, --content, --rich-text, --attach, or --artifact to update.");
         }
         if (opts.content && opts.richText) {
             throw new Error("--content and --rich-text are mutually exclusive.");
@@ -266,6 +269,8 @@ export function registerGlobalCommand(program) {
             assertPostAttachmentMix(opts.attach);
             body.attachments = await uploadPostAttachments(opts.attach);
         }
+        if (opts.artifact && opts.artifact.length > 0)
+            body.artifactIds = opts.artifact;
         const resp = (await apiPatch(`/posts/${postId}`, body));
         const post = unwrapResp(resp);
         if (isJsonMode(global)) {

package/dist/commands/init.js

@@ -31,6 +31,15 @@ export function getVaultSlug() {
     }
     return vault;
 }
+/**
+ * Starter PUBLISH.md frontmatter. Shared by `vault init` (seed) and
+ * `vault publish` (scaffold-on-missing) so the two paths can't drift.
+ * `description` is intentionally left blank — the vault won't list publicly
+ * until the user fills in both `title` and `description`.
+ */
+export function defaultPublishMd(title) {
+    return `---\ntitle: ${title}\ntags: []\ndescription:\nthumbnail:\nprompt:\n---\n`;
+}
 // Per-command requirement markers. Tri-state: true / false override / inherit
 // from parent. The pre-action warning uses these to decide whether to remind
 // the user to run `gobi vault init` / `gobi space warp`.
@@ -221,7 +230,7 @@ export async function runVaultInitFlow() {
     // Create default PUBLISH.md if it doesn't exist
     const publishPath = join(process.cwd(), "PUBLISH.md");
     if (!existsSync(publishPath)) {
-        writeFileSync(publishPath, `---\ntitle: ${vaultName}\ntags: []\ndescription:\nthumbnail:\nprompt:\n---\n`, "utf-8");
+        writeFileSync(publishPath, defaultPublishMd(vaultName), "utf-8");
         console.log("Created PUBLISH.md");
     }
 }

package/dist/commands/personal.js

@@ -246,13 +246,16 @@ export function registerPersonalCommand(program) {
         .option("--content <content>", "New content (markdown supported, use \"-\" for stdin)")
         .option("--rich-text <richText>", "Rich-text JSON array (mutually exclusive with --content)")
         .option("--attach <file>", "Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size ceilings: 5MB photos / 15MB GIFs / 512MB video. Omit to leave attachments unchanged.", (value, prev = []) => [...prev, value], [])
+        .option("--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`.", (value, prev = []) => [...prev, value], [])
         .action(async (postId, opts) => {
         const wantsAttachChange = !!(opts.attach && opts.attach.length > 0);
+        const wantsArtifactChange = !!(opts.artifact && opts.artifact.length > 0);
         if (opts.title == null &&
             opts.content == null &&
             opts.richText == null &&
-            !wantsAttachChange) {
-            throw new Error("Provide at least --title, --content, --rich-text, or --attach to update.");
+            !wantsAttachChange &&
+            !wantsArtifactChange) {
+            throw new Error("Provide at least --title, --content, --rich-text, --attach, or --artifact to update.");
         }
         if (opts.content && opts.richText) {
             throw new Error("--content and --rich-text are mutually exclusive.");
@@ -277,6 +280,8 @@ export function registerPersonalCommand(program) {
             assertPostAttachmentMix(opts.attach);
             body.attachments = await uploadPostAttachments(opts.attach);
         }
+        if (opts.artifact && opts.artifact.length > 0)
+            body.artifactIds = opts.artifact;
         const resp = (await apiPatch(`/posts/${postId}`, body));
         const post = unwrapResp(resp);
         if (isJsonMode(personal)) {

package/dist/commands/space.js

@@ -377,13 +377,16 @@ export function registerSpaceCommand(program) {
         .option("--rich-text <richText>", "Rich-text JSON array (mutually exclusive with --content)")
         .option("--space-slug <spaceSlug>", "Space slug (overrides .gobi/settings.yaml)")
         .option("--attach <file>", "Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size ceilings: 5MB photos / 15MB GIFs / 512MB video. Omit to leave attachments unchanged.", (value, prev = []) => [...prev, value], [])
+        .option("--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`.", (value, prev = []) => [...prev, value], [])
         .action(async (postId, opts) => {
         const wantsAttachChange = !!(opts.attach && opts.attach.length > 0);
+        const wantsArtifactChange = !!(opts.artifact && opts.artifact.length > 0);
         if (opts.title == null &&
             opts.content == null &&
             opts.richText == null &&
-            !wantsAttachChange) {
-            throw new Error("Provide at least --title, --content, --rich-text, or --attach to update.");
+            !wantsAttachChange &&
+            !wantsArtifactChange) {
+            throw new Error("Provide at least --title, --content, --rich-text, --attach, or --artifact to update.");
         }
         if (opts.content && opts.richText) {
             throw new Error("--content and --rich-text are mutually exclusive.");
@@ -409,6 +412,8 @@ export function registerSpaceCommand(program) {
             assertPostAttachmentMix(opts.attach);
             body.attachments = await uploadPostAttachments(opts.attach);
         }
+        if (opts.artifact && opts.artifact.length > 0)
+            body.artifactIds = opts.artifact;
         const resp = (await apiPatch(`/spaces/${spaceSlug}/posts/${postId}`, body));
         const post = unwrapResp(resp);
         if (isJsonMode(space)) {

package/dist/commands/sync.js

@@ -142,6 +142,22 @@ export function saveSyncState(gobiDir, state) {
     }
 }
 // ─── Syncfiles ────────────────────────────────────────────────────────────────
+/**
+ * Webdrive requires every sync/private pattern to be root-anchored — the server
+ * rejects anything not starting with "/" (HTTP 400: "Pattern must start with
+ * '/'"). Older syncfiles, hand-edits, and `--auto-attachments` appends can all
+ * produce slash-less entries that hard-fail the whole sync with a cryptic 400,
+ * so anchor them to the vault root here. Negation patterns ("!foo") keep their
+ * leading "!". Patterns already starting with "/" are returned unchanged, so
+ * anything the server currently accepts is untouched.
+ */
+export function normalizeSyncPattern(pattern) {
+    if (pattern.startsWith("!")) {
+        const rest = pattern.slice(1);
+        return rest.startsWith("/") ? pattern : `!/${rest}`;
+    }
+    return pattern.startsWith("/") ? pattern : `/${pattern}`;
+}
 export function readSyncfiles(gobiDir) {
     const syncfilesPath = join(gobiDir, "syncfiles");
     if (!existsSync(syncfilesPath)) {
@@ -151,7 +167,8 @@ export function readSyncfiles(gobiDir) {
     const patterns = content
         .split("\n")
         .map((l) => l.trim())
-        .filter((l) => l.length > 0 && !l.startsWith("#"));
+        .filter((l) => l.length > 0 && !l.startsWith("#"))
+        .map(normalizeSyncPattern);
     const contentHash = createHash("md5").update(content).digest("hex");
     return { patterns, contentHash };
 }
@@ -162,7 +179,8 @@ export function readPrivatefiles(gobiDir) {
     return readFileSync(path, "utf-8")
         .split("\n")
         .map((l) => l.trim())
-        .filter((l) => l.length > 0 && !l.startsWith("#"));
+        .filter((l) => l.length > 0 && !l.startsWith("#"))
+        .map(normalizeSyncPattern);
 }
 export function buildWhitelistMatcher(patterns) {
     if (patterns.length === 0)

package/dist/commands/vault.js

@@ -1,10 +1,10 @@
-import { existsSync, readFileSync } from "fs";
+import { existsSync, readFileSync, writeFileSync } from "fs";
 import { join, resolve as pathResolve } from "path";
 import { WEB_BASE_URL, WEBDRIVE_BASE_URL } from "../constants.js";
 import { getValidToken } from "../auth/manager.js";
 import { GobiError } from "../errors.js";
 import { apiDelete, apiGet, apiPatch, apiPost } from "../client.js";
-import { getVaultSlug, requireVault, runVaultInitFlow } from "./init.js";
+import { defaultPublishMd, getVaultSlug, requireVault, runVaultInitFlow } from "./init.js";
 import { isJsonMode, jsonOut, unwrapResp } from "./utils.js";
 import { runSync } from "./sync.js";
 export const PUBLISH_FILENAME = "PUBLISH.md";
@@ -156,7 +156,19 @@ export function registerVaultCommand(program) {
         const vaultId = getVaultSlug();
         const filePath = join(process.cwd(), PUBLISH_FILENAME);
         if (!existsSync(filePath)) {
-            throw new Error(`${PUBLISH_FILENAME} not found in ${process.cwd()}`);
+            // Scaffold a starter profile locally instead of dead-ending, but do NOT
+            // push it — an empty profile shouldn't go live without the user's review.
+            // (Legacy vaults that predate PUBLISH.md, e.g. BRAIN.md-only, land here.)
+            writeFileSync(filePath, defaultPublishMd(vaultId), "utf-8");
+            const msg = `${PUBLISH_FILENAME} not found, so a starter one was created at ${filePath}. ` +
+                `Fill in at least "title" and "description" (add "homepage" too if you have a custom homepage), ` +
+                `then re-run "gobi vault publish".`;
+            if (isJsonMode(vault)) {
+                jsonOut({ vaultId, published: false, created: PUBLISH_FILENAME, message: msg });
+                return;
+            }
+            console.log(msg);
+            return;
         }
         const content = readFileSync(filePath, "utf-8");
         const token = await getValidToken();

package/package.json

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

package/skills/gobi-artifact/SKILL.md

@@ -9,12 +9,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.28"
+  version: "2.0.30"
 ---
 
 # gobi-artifact
 
-Gobi artifact commands for versioned, post-attachable creations (v2.0.28).
+Gobi artifact commands for versioned, post-attachable creations (v2.0.30).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
@@ -103,9 +103,13 @@ gobi artifact download <artifactId> --revision <revisionId> --out image.png
 
 ## Attaching to a post
 
-`create --post-id <id>` attaches the new artifact to a post **without clobbering** the post's existing artifacts: the CLI reads the post's current artifact attachments, appends the new id, and writes the merged set via the post edit endpoint (`PATCH /posts/:id` with `artifactIds`). The post API's `artifactIds` is otherwise a full replacement.
+Three ways to attach an artifact, depending on what already exists:
 
-Attaching is done at artifact-create time via `--post-id`. The post commands (`create-post` / `edit-post`) do **not** expose an artifact-attach flag — to attach to an existing post, create the artifact with `--post-id <that post's id>`.
+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`).
+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).
+
+The same artifact can be attached to **multiple posts** (it's a reusable, versioned creation — each post renders its currently-published revision, so revising + publishing updates every post at once). Create it once, then reference its id via `--artifact` on each post.
 
 ## Available Commands
 

package/skills/gobi-core/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.28"
+  version: "2.0.30"
 ---
 
 # gobi-core
 
-Core CLI commands for the Gobi collaborative knowledge platform (v2.0.28).
+Core CLI commands for the Gobi collaborative knowledge platform (v2.0.30).
 
 ## Prerequisites
 

package/skills/gobi-homepage/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.28"
+  version: "2.0.30"
 ---
 
 # Gobi Homepage Developer Guide
@@ -20,13 +20,26 @@ A **Gobi Homepage** is a custom HTML page hosted on a vault's webdrive and serve
 
 ## Setup
 
-1. Create an HTML file in the vault (e.g. `app/home.html`) and upload:
+A homepage is registered only after `PUBLISH.md` references it **and** the vault is re-published. Uploading the HTML alone does **not** set the homepage — `gobi vault status` will keep reporting `homepagePath: null` until you publish.
+
+1. **Create** the HTML file at a vault-root-relative path, e.g. `app/home.html` (not `_Gobi_/app/home.html` — paths are relative to the vault root).
+2. **Reference it** in `PUBLISH.md` frontmatter via the `homepage` property:
+   - `homepage: "[[app/home.html]]"` — Gobi sidebar visible alongside the homepage
+   - `homepage: "[[app/home.html?nav=false]]"` — full-screen, no Gobi chrome
+3. **Upload** the HTML to webdrive:
    ```bash
-   gobi vault sync
+   gobi vault sync --upload-only --path app/home.html
    ```
-2. Set `homepage` in PUBLISH.md (homepage property):
-   - `homepage: "[[app/home.html]]"` — Gobi sidebars visible alongside the homepage
-   - `homepage: "[[app/home.html?nav=false]]"` — full-screen, no Gobi chrome
+4. **Publish** so the updated frontmatter takes effect (this uploads `PUBLISH.md` and re-syncs vault metadata):
+   ```bash
+   gobi vault publish
+   ```
+5. **Verify** the homepage is registered:
+   ```bash
+   gobi --json vault status   # expect "homepagePath": "app/home.html"
+   ```
+
+> Any time you change the `homepage` frontmatter, re-run `gobi vault publish` — the file upload alone won't update the profile. See the **gobi-vault** skill for the full publishing workflow.
 
 ---
 

package/skills/gobi-media/SKILL.md

@@ -10,12 +10,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.28"
+  version: "2.0.30"
 ---
 
 # gobi-media
 
-Gobi media generation commands (v2.0.28).
+Gobi media generation commands (v2.0.30).
 
 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.28"
+  version: "2.0.30"
 ---
 
 # gobi-sense
 
-Gobi sense commands for activity and transcription data (v2.0.28).
+Gobi sense commands for activity and transcription data (v2.0.30).
 
 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.28"
+  version: "2.0.30"
 ---
 
 # gobi-space
 
-Gobi space, global, and personal-space posts (v2.0.28).
+Gobi space, global, and personal-space posts (v2.0.30).
 
 Requires gobi-cli installed and authenticated. See the **gobi-core** skill for setup.
 
@@ -47,7 +47,7 @@ The same applies to replies: a reply has only `--content` (no title), so do not
 
 ## Attaching artifacts (`--artifact`)
 
-Posts have no vault attribution. `create-post` across all three scopes (`gobi space`, `gobi global`, `gobi personal`) accepts `--artifact <artifactId>` (repeatable) to attach existing artifacts to the post. 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 (`gobi artifact create --kind markdown --vault-slug <slug>`) 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`.
 

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

@@ -89,12 +89,14 @@ Usage: gobi global edit-post [options] <postId>
 Edit a post you authored in the global feed.
 
 Options:
-  --title <title>         New title
-  --content <content>     New content (markdown supported, use "-" for stdin)
-  --rich-text <richText>  Rich-text JSON array (mutually exclusive with --content)
-  --attach <file>         Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size
-                          ceilings: 5MB photos / 15MB GIFs / 512MB video. Omit to leave attachments unchanged. (default: [])
-  -h, --help              display help for command
+  --title <title>          New title
+  --content <content>      New content (markdown supported, use "-" for stdin)
+  --rich-text <richText>   Rich-text JSON array (mutually exclusive with --content)
+  --attach <file>          Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size
+                           ceilings: 5MB photos / 15MB GIFs / 512MB video. 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: [])
+  -h, --help               display help for command
 ```
 
 ## delete-post

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

@@ -88,12 +88,14 @@ Usage: gobi personal edit-post [options] <postId>
 Edit a post you authored in your personal space.
 
 Options:
-  --title <title>         New title
-  --content <content>     New content (markdown supported, use "-" for stdin)
-  --rich-text <richText>  Rich-text JSON array (mutually exclusive with --content)
-  --attach <file>         Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size
-                          ceilings: 5MB photos / 15MB GIFs / 512MB video. Omit to leave attachments unchanged. (default: [])
-  -h, --help              display help for command
+  --title <title>          New title
+  --content <content>      New content (markdown supported, use "-" for stdin)
+  --rich-text <richText>   Rich-text JSON array (mutually exclusive with --content)
+  --attach <file>          Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size
+                           ceilings: 5MB photos / 15MB GIFs / 512MB video. 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: [])
+  -h, --help               display help for command
 ```
 
 ## delete-post

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

@@ -140,6 +140,8 @@ Options:
   --space-slug <spaceSlug>  Space slug (overrides .gobi/settings.yaml)
   --attach <file>           Replace the post's media attachments with the given files (existing attachments are removed). Repeatable. X-style mix rule: up to 4 photos OR 1 GIF OR 1 video. Size
                             ceilings: 5MB photos / 15MB GIFs / 512MB video. 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: [])
   -h, --help                display help for command
 ```
 

package/skills/gobi-vault/SKILL.md

@@ -8,12 +8,12 @@ description: >-
 allowed-tools: Bash(gobi:*)
 metadata:
   author: gobi-ai
-  version: "2.0.28"
+  version: "2.0.30"
 ---
 
 # gobi-vault
 
-Gobi vault commands for publishing your vault profile and syncing files (v2.0.28).
+Gobi vault commands for publishing your vault profile and syncing files (v2.0.30).
 
 Requires gobi-cli installed and authenticated. See gobi-core skill for setup.
 
@@ -46,7 +46,7 @@ gobi --json vault publish
 - `gobi vault create <slug> --name <name>` — Create a new vault with the given slug and display name. Slug must be unique (use `vault list` to see what's taken). Does not change the configured vault — run `vault init` here afterwards if you want to anchor to it.
 - `gobi vault rename <newName>` — Rename the configured vault's display name. Pass `--vault-slug <slug>` to target another vault. Local handle only — the public profile title comes from `PUBLISH.md` frontmatter and is unaffected.
 - `gobi vault delete <slug>` — Delete a vault. Irreversible. Required arg, no `.gobi` fallback. The API will reject if the vault still owns content; clean up posts, members, and files first.
-- `gobi vault publish` — Upload `PUBLISH.md` to the vault root on webdrive. Triggers post-processing (vault profile sync, metadata update).
+- `gobi vault publish` — Upload `PUBLISH.md` to the vault root on webdrive. Triggers post-processing (vault profile sync, metadata update). If `PUBLISH.md` is missing (e.g. a legacy vault that only has `BRAIN.md`), a starter `PUBLISH.md` is scaffolded locally and **nothing is pushed** — fill in at least `title` and `description`, then re-run.
 - `gobi vault unpublish` — Delete `PUBLISH.md` from the vault on webdrive.
 - `gobi vault sync` — Sync local vault files with Gobi Webdrive. Supports `--upload-only`, `--download-only`, `--conflict <ask|server|client|skip>`, `--dry-run`, `--full`, `--path <p>`, `--plan-file`, `--execute`.