@heyamiko/amiko-cli 0.17.0 → 0.17.2

package/README.md

@@ -653,14 +653,16 @@ amiko feed                              # friends feed (default)
 amiko feed --type all --limit 20        # the "All" tab (a.k.a. for_you)
 amiko feed --type following             # posts from accounts you follow
 amiko feed --type media --kind image    # site-wide public media (hits /api/media/feed)
-amiko post create --content "hello from the CLI"           # public post — prints the canonical share URL (post_url in --json); share that verbatim, never hand-build one from the id
+amiko post create --content "hello from the CLI"           # saves a DRAFT by default (owner-only) — preview with `amiko post show <id>`, then `amiko post publish <id>`
+amiko post create --content "ship it" --publish            # create AND publish in one step — prints the canonical share URL (post_url in --json); share that verbatim, never hand-build one from the id
 amiko post create --title "Kyoto, 6am" --media ./shot.webp # image-only note — --content is optional when media/docs are attached
 amiko post create --title "Q3 report" --doc ./q3.pdf       # document note — rendered as a file card
 amiko post create --content "private note" --visibility private
 amiko post create --content "look" --media https://...jpg
 amiko post create --title "the track" --media drive:<docId>  # media already in the Drive (id from `amiko drive list`) — works for audio/video too
-amiko post create --content "wip idea" --draft         # save a draft — no share URL until published
+amiko post create --content "wip idea" --draft         # explicit draft (same as the default) — no share URL until published
 amiko post drafts                                       # list draft posts (--limit/--offset/--json)
+amiko post show <postId>                                # preview any post, including your own unpublished drafts
 amiko post likers <postId>                              # who liked one of YOUR posts (403 on someone else's)
 amiko post publish <postId>                             # publish a draft (fresh timestamp, prints the share URL)
 amiko post comment --id <postId> --comment "great post"
@@ -1808,6 +1810,7 @@ Send a friend request to a user by id
 | Flag | Default | Description |
 |---|---|---|
 | `--id <userId>` |  | Target user id |
+| `--yes` |  | Skip the confirmation. Only pass this after the owner has confirmed they want to friend this specific person. |
 | `--json` |  | Output as JSON |
 
 #### `amiko friends accept <friendshipId>`
@@ -1816,6 +1819,7 @@ Accept a pending friend request
 
 | Flag | Default | Description |
 |---|---|---|
+| `--yes` |  | Skip the confirmation. Only pass this after the owner has confirmed they want to accept this request. |
 | `--json` |  | Output as JSON |
 
 #### `amiko friends requests`
@@ -2039,8 +2043,9 @@ Create posts (notes) and comments on the feed — text, images, and documents
 
 | Subcommand | Description |
 |---|---|
-| `post create` | Create a post (a.k.a. note) on your feed |
+| `post create` | Create a post (a.k.a. note) on your feed. Saved as a DRAFT by default (owner-only, editable) — publish it as a second step with `amiko post publish <id>`, or pass --publish to create and publish in one go. |
 | `post drafts` | List your draft posts (newest first) |
+| `post show` | Preview a single post by id. Works on your own drafts too (owner-only, before publishing) — use it to show the owner exactly what will go out. |
 | `post publish` | Publish a draft post (stamps a fresh timestamp and notifies mentions) |
 | `post delete` | Delete one of your posts. Use this to clean up a post that went out wrong (bad link, test post, wrong version) |
 | `post comments` | List comments on a post |
@@ -2049,17 +2054,19 @@ Create posts (notes) and comments on the feed — text, images, and documents
 
 #### `amiko post create`
 
-Create a post (a.k.a. note) on your feed
+Create a post (a.k.a. note) on your feed. Saved as a DRAFT by default (owner-only, editable) — publish it as a second step with `amiko post publish <id>`, or pass --publish to create and publish in one go.
 
 | Flag | Default | Description |
 |---|---|---|
 | `--content <text>` |  | Post body. Optional when --media or --doc is given (an image-only note is a normal post) |
+| `--markdown` |  | Render --content as markdown (bold/lists/links/tables). @mentions and #hashtags still link. Default is plain text. |
 | `--title <text>` |  | Note title, max 150 chars — the heading shown on the feed card. Optional but strongly recommended for image notes |
 | `--visibility <public|private>` | `public` | Post visibility |
 | `--media <pathOrUrl...>` |  | Attach media: local IMAGE file paths (uploaded automatically); Amiko-hosted URLs (image/music/video from `amiko create`); or `drive:<docId>` for a media file in your Drive (`amiko drive list`) |
 | `--doc <pathOrUrl...>` |  | Attach documents (pdf/md/txt/…, max 8): local file paths are uploaded automatically. Rendered as file cards, not images |
-| `--draft` |  | Save as a draft instead of publishing (list: amiko post drafts · publish: amiko post publish <id>) |
-| `--yes` |  | Skip the publish confirmation (drafts never prompt). Only pass this after the owner has reviewed the exact copy and approved sending it. |
+| `--draft` |  | Save as a draft (this is the default). Kept for clarity/back-compat — a bare `create` already drafts. List: amiko post drafts · publish: amiko post publish <id> |
+| `--publish` |  | Create AND publish immediately, skipping the draft step. Outward — everyone sees it — so it takes the confirmation gate (or --yes once the owner has approved the exact copy). |
+| `--yes` |  | Skip the publish confirmation (only relevant with --publish; drafts never prompt). Only pass this after the owner has reviewed the exact copy and approved publishing it. |
 | `--json` |  | Output as JSON |
 
 #### `amiko post drafts`
@@ -2072,6 +2079,14 @@ List your draft posts (newest first)
 | `--offset <n>` | `0` | Pagination offset |
 | `--json` |  | Output as JSON |
 
+#### `amiko post show <postId>`
+
+Preview a single post by id. Works on your own drafts too (owner-only, before publishing) — use it to show the owner exactly what will go out.
+
+| Flag | Default | Description |
+|---|---|---|
+| `--json` |  | Output as JSON |
+
 #### `amiko post publish <postId>`
 
 Publish a draft post (stamps a fresh timestamp and notifies mentions)

package/dist/index.js

@@ -34041,8 +34041,14 @@ function registerFriendsCommand(program2) {
       process.exit(1);
     }
   });
-  program2.command("add").description("Send a friend request to a user by id").requiredOption("--id <userId>", "Target user id").option("--json", "Output as JSON").action(async (opts) => {
+  program2.command("add").description("Send a friend request to a user by id").requiredOption("--id <userId>", "Target user id").option("--yes", "Skip the confirmation. Only pass this after the owner has confirmed they want to friend this specific person.").option("--json", "Output as JSON").action(async (opts) => {
     const auth = resolveAuth();
+    await requireApproval({
+      free: "sends a friend request to a real person, who is notified",
+      summary: `Send a friend request to user ${opts.id}`,
+      yes: opts.yes,
+      commandExample: `amiko friends add --id ${JSON.stringify(opts.id)}`
+    });
     const spinner = opts.json ? null : ora("Sending friend request...").start();
     try {
       const data = await amikoWebFetch(auth, "/api/friends", {
@@ -34061,8 +34067,14 @@ function registerFriendsCommand(program2) {
       process.exit(1);
     }
   });
-  program2.command("accept <friendshipId>").description("Accept a pending friend request").option("--json", "Output as JSON").action(async (friendshipId, opts) => {
+  program2.command("accept <friendshipId>").description("Accept a pending friend request").option("--yes", "Skip the confirmation. Only pass this after the owner has confirmed they want to accept this request.").option("--json", "Output as JSON").action(async (friendshipId, opts) => {
     const auth = resolveAuth();
+    await requireApproval({
+      free: "accepts a friend request, forming a mutual connection the other person sees",
+      summary: `Accept friend request ${friendshipId}`,
+      yes: opts.yes,
+      commandExample: `amiko friends accept ${JSON.stringify(friendshipId)}`
+    });
     const spinner = opts.json ? null : ora("Accepting...").start();
     try {
       const data = await amikoWebFetch(auth, `/api/friends/${friendshipId}`, { method: "PATCH", body: { action: "accept" } });
@@ -34990,7 +35002,7 @@ function registerFeedCommand(program2) {
   });
 }
 function registerPostCommand(program2) {
-  program2.command("create").description("Create a post (a.k.a. note) on your feed").option("--content <text>", "Post body. Optional when --media or --doc is given (an image-only note is a normal post)").option("--title <text>", "Note title, max 150 chars — the heading shown on the feed card. Optional but strongly recommended for image notes").option("--visibility <public|private>", "Post visibility", "public").option("--media <pathOrUrl...>", "Attach media: local IMAGE file paths (uploaded automatically); Amiko-hosted URLs (image/music/video from `amiko create`); or `drive:<docId>` for a media file in your Drive (`amiko drive list`)").option("--doc <pathOrUrl...>", "Attach documents (pdf/md/txt/…, max 8): local file paths are uploaded automatically. Rendered as file cards, not images").option("--draft", "Save as a draft instead of publishing (list: amiko post drafts · publish: amiko post publish <id>)").option("--yes", "Skip the publish confirmation (drafts never prompt). Only pass this after the owner has reviewed the exact copy and approved sending it.").option("--json", "Output as JSON").action(async (opts) => {
+  program2.command("create").description("Create a post (a.k.a. note) on your feed. Saved as a DRAFT by default (owner-only, editable) — publish it as a second step with `amiko post publish <id>`, or pass --publish to create and publish in one go.").option("--content <text>", "Post body. Optional when --media or --doc is given (an image-only note is a normal post)").option("--markdown", "Render --content as markdown (bold/lists/links/tables). @mentions and #hashtags still link. Default is plain text.").option("--title <text>", "Note title, max 150 chars — the heading shown on the feed card. Optional but strongly recommended for image notes").option("--visibility <public|private>", "Post visibility", "public").option("--media <pathOrUrl...>", "Attach media: local IMAGE file paths (uploaded automatically); Amiko-hosted URLs (image/music/video from `amiko create`); or `drive:<docId>` for a media file in your Drive (`amiko drive list`)").option("--doc <pathOrUrl...>", "Attach documents (pdf/md/txt/…, max 8): local file paths are uploaded automatically. Rendered as file cards, not images").option("--draft", "Save as a draft (this is the default). Kept for clarity/back-compat — a bare `create` already drafts. List: amiko post drafts · publish: amiko post publish <id>").option("--publish", "Create AND publish immediately, skipping the draft step. Outward — everyone sees it — so it takes the confirmation gate (or --yes once the owner has approved the exact copy).").option("--yes", "Skip the publish confirmation (only relevant with --publish; drafts never prompt). Only pass this after the owner has reviewed the exact copy and approved publishing it.").option("--json", "Output as JSON").action(async (opts) => {
     const auth = resolveAuth();
     const visibility = opts.visibility === "private" ? "private" : "public";
     const content = opts.content?.trim() ?? "";
@@ -35004,7 +35016,12 @@ function registerPostCommand(program2) {
       console.error(error(`--title is ${titleLength} characters; the maximum is ${MAX_TITLE_CHARS}.`));
       process.exit(1);
     }
-    if (!opts.draft) {
+    if (opts.publish && opts.draft) {
+      console.error(error("Pass either --publish or --draft, not both."));
+      process.exit(1);
+    }
+    const isDraft = !opts.publish;
+    if (!isDraft) {
       const previewLine = (title ? `${title} — ` : "") + content;
       const attachSummary = [
         opts.media?.length ? `${opts.media.length} media` : "",
@@ -35014,20 +35031,21 @@ function registerPostCommand(program2) {
         free: "publishes a post to your public feed — everyone can see it",
         summary: `Publish ${visibility} post${attachSummary ? ` [+${attachSummary}]` : ""}: ${previewLine.slice(0, 80)}${previewLine.length > 80 ? "…" : ""}`,
         yes: opts.yes,
-        commandExample: `amiko post create` + (opts.content ? ` --content ${JSON.stringify(opts.content)}` : "") + (opts.title ? ` --title ${JSON.stringify(opts.title)}` : "") + (opts.visibility && opts.visibility !== "public" ? ` --visibility ${opts.visibility}` : "") + (opts.media?.length ? ` --media ${opts.media.map((m) => JSON.stringify(m)).join(" ")}` : "") + (opts.doc?.length ? ` --doc ${opts.doc.map((d) => JSON.stringify(d)).join(" ")}` : "")
+        commandExample: `amiko post create --publish` + (opts.content ? ` --content ${JSON.stringify(opts.content)}` : "") + (opts.markdown ? " --markdown" : "") + (opts.title ? ` --title ${JSON.stringify(opts.title)}` : "") + (opts.visibility && opts.visibility !== "public" ? ` --visibility ${opts.visibility}` : "") + (opts.media?.length ? ` --media ${opts.media.map((m) => JSON.stringify(m)).join(" ")}` : "") + (opts.doc?.length ? ` --doc ${opts.doc.map((d) => JSON.stringify(d)).join(" ")}` : "")
       });
     }
-    const workingText = opts.draft ? "Saving draft..." : "Publishing post...";
+    const workingText = isDraft ? "Saving draft..." : "Publishing post...";
     const spinner = opts.json ? null : ora(workingText).start();
     try {
       const body = {
         content,
         visibility
       };
+      if (opts.markdown)
+        body.content_format = "markdown";
       if (title)
         body.title = title;
-      if (opts.draft)
-        body.status = "draft";
+      body.status = isDraft ? "draft" : "published";
       if (opts.media?.length) {
         if (spinner)
           spinner.text = "Uploading media...";
@@ -35044,16 +35062,16 @@ function registerPostCommand(program2) {
       }
       const data = await amikoWebFetch(auth, "/api/posts", { method: "POST", body });
       spinner?.stop();
-      const postUrl = !opts.draft && data.post?.id ? `https://platform.heyamiko.com/post/${data.post.id}` : null;
+      const postUrl = !isDraft && data.post?.id ? `https://platform.heyamiko.com/post/${data.post.id}` : null;
       renderOutput(postUrl ? { ...data, post_url: postUrl } : data, (d) => {
-        console.log(success(opts.draft ? "Draft saved" : "Post published"));
+        console.log(success(isDraft ? "Draft saved" : "Post published"));
         const post = d.post;
         if (post) {
           if (post.id)
             console.log(label("Post ID", String(post.id)));
           if (postUrl)
             console.log(label("URL", postUrl));
-          if (opts.draft)
+          if (isDraft)
             console.log(label("Status", "draft"));
           if (title)
             console.log(label("Title", title));
@@ -35062,8 +35080,8 @@ function registerPostCommand(program2) {
             console.log(label("Documents", (docs ?? []).map((doc2) => doc2.filename).join(", ")));
           }
           console.log(label("Visibility", visibility));
-          if (opts.draft && post.id) {
-            console.log(dim(`No public URL until published. List: amiko post drafts · Publish: amiko post publish ${post.id}`));
+          if (isDraft && post.id) {
+            console.log(dim(`Draft only — nobody else can see it yet, and there's no public URL until it's published. Preview: amiko post show ${post.id} · Publish (owner approves): amiko post publish ${post.id}`));
           }
         }
       }, { json: opts.json });
@@ -35127,6 +35145,47 @@ function registerPostCommand(program2) {
       process.exit(1);
     }
   });
+  program2.command("show <postId>").description("Preview a single post by id. Works on your own drafts too (owner-only, before publishing) — use it to show the owner exactly what will go out.").option("--json", "Output as JSON").action(async (postId, opts) => {
+    const auth = resolveAuth();
+    const spinner = opts.json ? null : ora("Loading post...").start();
+    try {
+      const data = await amikoWebFetch(auth, `/api/posts/${encodeURIComponent(postId)}`);
+      spinner?.stop();
+      const post = data.post;
+      if (!post) {
+        console.error(error(`Post ${postId} not found.`));
+        process.exit(1);
+      }
+      const status = post.status ?? "published";
+      const postUrl = status === "published" && post.id ? `https://platform.heyamiko.com/post/${post.id}` : null;
+      renderOutput(postUrl ? { ...data, post_url: postUrl } : data, () => {
+        console.log(heading(status === "draft" ? "Draft (owner-only)" : "Post"));
+        if (post.title)
+          console.log(heading(String(post.title)));
+        if (post.content)
+          console.log(String(post.content));
+        const mediaCount = post.media_urls?.length ?? 0;
+        const docCount = post.doc_attachments?.length ?? 0;
+        console.log(dim(`${post.visibility ?? "public"}${mediaCount ? ` · ${mediaCount} media` : ""}${docCount ? ` · ${docCount} docs` : ""}`));
+        if (post.id)
+          console.log(label("Post ID", String(post.id)));
+        console.log(label("Status", status));
+        if (postUrl)
+          console.log(label("URL", postUrl));
+        if (status === "draft" && post.id) {
+          console.log(dim(`Publish (owner approves): amiko post publish ${post.id}`));
+        }
+      }, { json: opts.json });
+    } catch (e5) {
+      spinner?.stop();
+      if (e5.status === 404) {
+        console.error(error(`Post ${postId} not found (or a draft that isn't yours). Your drafts: amiko post drafts`));
+      } else {
+        console.error(error(e5 instanceof Error ? e5.message : String(e5)));
+      }
+      process.exit(1);
+    }
+  });
   program2.command("publish <postId>").description("Publish a draft post (stamps a fresh timestamp and notifies mentions)").option("--yes", "Skip the publish confirmation. Only pass this after the owner has reviewed the draft and approved publishing it.").option("--json", "Output as JSON").action(async (postId, opts) => {
     const auth = resolveAuth();
     await requireApproval({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@heyamiko/amiko-cli",
-  "version": "0.17.0",
+  "version": "0.17.2",
   "description": "Amiko CLI — swap tokens, manage credits, bridge cross-chain, and call marketplace agents",
   "type": "module",
   "bin": {

package/skills/SKILL.md

@@ -33,13 +33,13 @@ Call your shell tool (your runtime calls it `bash`, `shell`, `run`, or similar)
 | "what comments are on my post?" | shell → `amiko post comments --id <postId>` |
 | "谁给我点赞了 / which friends liked my post?" | shell → `amiko post likers <postId>` (own posts only) → cross-reference ids against `amiko friends list` |
 | "我有多少好友 / how many friends do I have?" | shell → `amiko friends list` — read the header total, don't count rows |
-| "发个笔记 / post this photo as a note" | draft-first → `amiko post create --title "…" --media ./photo.webp --draft` → show the owner → `amiko post publish <id> --yes` |
-| "post the audio/image from my Drive" | shell → `amiko drive list --json` (copy the `id`) → `amiko post create --title "…" --media drive:<docId> --draft` → owner reviews → `amiko post publish <id> --yes` |
-| "share this PDF on my feed" | `amiko post create --title "…" --doc ./report.pdf --draft` → owner reviews → `amiko post publish <id> --yes` |
+| "发个笔记 / post this photo as a note" | draft-first (`create` drafts by default) → `amiko post create --title "…" --media ./photo.webp` → `amiko post show <id>` show the owner → `amiko post publish <id> --yes` |
+| "post the audio/image from my Drive" | shell → `amiko drive list --json` (copy the `id`) → `amiko post create --title "…" --media drive:<docId>` → `amiko post show <id>` owner reviews → `amiko post publish <id> --yes` |
+| "share this PDF on my feed" | `amiko post create --title "…" --doc ./report.pdf` → `amiko post show <id>` owner reviews → `amiko post publish <id> --yes` |
 | "关注 / follow @mars" | shell → `amiko users follow mars` (confirm first — it notifies them) |
 | "what did the people I follow post?" | shell → `amiko feed --type following` |
-| "save this as a post draft, don't publish yet" | shell → `amiko post create --content "…" --draft` |
-| "publish that draft" | shell → `amiko post drafts` (copy the id) → show the owner → `amiko post publish <postId> --yes` |
+| "save this as a post draft, don't publish yet" | shell → `amiko post create --content "…"` (drafts by default; `--draft` is optional/back-compat) |
+| "publish that draft" | shell → `amiko post drafts` (copy the id) → `amiko post show <postId>` show the owner → `amiko post publish <postId> --yes` |
 | "delete / 撤下 that post (it went out wrong)" | shell → `amiko post list` (copy the id) → confirm which one → `amiko post delete <postId> --yes` |
 | "search memory for X" | shell → `amiko memory search "X"` |
 | "share the group's invite link" (asked by an admin) | shell → `amiko chat group info "<group>"` (confirm they're admin) → `amiko chat group invite "<group>"` |
@@ -73,7 +73,7 @@ Discover everything via `amiko --help` (or `amiko <group> --help` / `amiko <grou
 
 ## Critical Rules
 
-1. **Every paid / value-moving command is hard-gated on `--yes` in a non-interactive shell.** The CLI refuses to run `search *`, `markets *`, `create *`, `card mint`, `credits topup`, `wallets swap send`, `wallets bridge send`, `wallets transfer` unless `--yes` is passed. The refusal prints the cost and the re-run command. **Quote the cost, get explicit approval, THEN append `--yes`.** For `create *` there is a step before that — propose the model and settings and get the owner's sign-off on the *plan* first; see **Proposing, then quoting, before you generate**. The same `--yes` gate also covers **free outward social actions** — `chat send`, `chat pin` (the whole chat sees a pinned-message announcement), `chat group create`, `chat group add` (real people see them, so get the owner's explicit approval for the action itself) — and **destructive ops** like `chat unpin` (removes the pin for everyone), `chat mark-read --all` (irreversibly marks every conversation read — senders see read ticks), `chat group remove/leave/rename/promote/mention-all`, `chat lists create/rename/add/remove/delete` (private to the owner, but they reshape the owner's chat UI), `friends nickname set/remove` (private to the owner, but it changes how that friend is displayed everywhere in the owner's apps), `twin update --public`, `drive delete`, `drive share` / `drive folder share` (exposes the file — or the folder's ENTIRE subtree — to anyone with the link), `friends remove`, `friends reports request`, `avatar update`, `voice reset`, `review reject`. **For these free actions never mention cost, never say "the cost is 0", and never call it a paid operation** — ask for plain confirmation of the action itself (e.g. "Send "hi" to Mars — go ahead?").
+1. **Every paid / value-moving command is hard-gated on `--yes` in a non-interactive shell.** The CLI refuses to run `search *`, `markets *`, `create *`, `card mint`, `credits topup`, `wallets swap send`, `wallets bridge send`, `wallets transfer` unless `--yes` is passed. The refusal prints the cost and the re-run command. **Quote the cost, get explicit approval, THEN append `--yes`.** For `create *` there is a step before that — propose the model and settings and get the owner's sign-off on the *plan* first; see **Proposing, then quoting, before you generate**. The same `--yes` gate also covers **free outward social actions** — `chat send`, `chat pin` (the whole chat sees a pinned-message announcement), `chat group create`, `chat group add`, `friends add` / `friends accept` (real people see them — a friended user is notified — so get the owner's explicit approval for the action itself) — and **destructive ops** like `chat unpin` (removes the pin for everyone), `chat mark-read --all` (irreversibly marks every conversation read — senders see read ticks), `chat group remove/leave/rename/promote/mention-all`, `chat lists create/rename/add/remove/delete` (private to the owner, but they reshape the owner's chat UI), `friends nickname set/remove` (private to the owner, but it changes how that friend is displayed everywhere in the owner's apps), `twin update --public`, `drive delete`, `drive share` / `drive folder share` (exposes the file — or the folder's ENTIRE subtree — to anyone with the link), `friends remove`, `friends reports request`, `avatar update`, `voice reset`, `review reject`. **For these free actions never mention cost, never say "the cost is 0", and never call it a paid operation** — ask for plain confirmation of the action itself (e.g. "Send "hi" to Mars — go ahead?").
 2. **After every paid command, report the remaining balance.** The CLI prints a `Balance: N credits` line — include that figure in your reply.
 3. **Never retry a failed command.** Report and stop. Every paid call costs tokens even on failure.
 4. **Auth is automatic.** Never suggest `amiko login` / `amiko connect`. Run from the agent's workspace folder; if anything looks off, `amiko accounts` shows the resolved `userId` / `twinId`.
@@ -352,7 +352,9 @@ Two different relationships — pick the one the owner actually asked for:
 
 **"Notes" and "posts" are the same thing.** The web app calls the feed surface *notes* (小红书-style card grid); the CLI calls it `post` / `feed`. When the owner says "发个笔记" / "post a note", that is `amiko post create` — there is no separate notes command.
 
-> **⚠️ Draft-first, publish on the owner's word.** Publishing is outward and permanent — everyone sees it, and you cannot edit a published post from the CLI. Publishing goes wrong most often in exactly three ways: a **wrong link** in the body, a **stray test post** while you're trying out a format, and the **wrong version** of something you drafted more than once. So the default workflow is: **save a draft first** (`amiko post create … --draft`), show the owner the exact copy (and, for an image/media note, the actual attachment and any link in the body), and publish **only after they say go** — then `amiko post publish <postId> --yes`. Publishing and deleting are gated: `amiko post publish`, `amiko post delete`, and a direct `amiko post create` (no `--draft`) all **refuse without `--yes`** and will not run until the owner has approved the specific thing. `--yes` is *not* yours to add on your own initiative — add it only once the owner has seen what goes out and approved it. When in doubt, draft it and ask; do not publish to "check how it looks." (Scheduled/automated posting the owner set up is the exception — those runs carry `--yes` because the owner pre-approved the job.)
+> **⚠️ Draft-first, publish on the owner's word.** Publishing is outward and permanent — everyone sees it, and you cannot edit a published post from the CLI. Publishing goes wrong most often in exactly three ways: a **wrong link** in the body, a **stray test post** while you're trying out a format, and the **wrong version** of something you drafted more than once. So `amiko post create` **saves a draft by default** — a draft is owner-only, editable, and invisible to everyone else, so it is safe and never prompts. Show the owner the exact copy (`amiko post show <id>` — for an image/media note also the actual attachment and any link in the body), and publish **only after they say go**: `amiko post publish <postId> --yes`. The **outward** steps are what's gated: `amiko post publish`, `amiko post delete`, and `amiko post create --publish` (the one-step create-and-publish shortcut) all **refuse without `--yes`** and will not run until the owner has approved the specific thing. A bare `amiko post create` does NOT need `--yes` — it only makes a draft. `--yes` is *not* yours to add on your own initiative — add it only once the owner has seen what goes out and approved it. When in doubt, draft it and ask; do not publish to "check how it looks."
+
+> **⏰ Schedule mode — publishing needs `--publish` (the job is the owner's pre-approval).** When this run is a scheduled task — you'll see a `### Scheduled Task` block in your context — the owner set the job up in advance, so it *is* the approval. But draft-first still applies to the raw command: a bare `amiko post create` **drafts** even inside a schedule, so a post that stops appearing on the feed is the tell that the `--publish` flag is missing. If the job's purpose is to publish to the feed, create-and-publish in one step: **`amiko post create --publish --yes …`** (or, if you drafted first, `amiko post publish <id> --yes`). The `--yes` is what carries the owner's standing approval for the scheduled job — outside a schedule you would never add it on your own. If the job only says "draft" (e.g. a review-before-send flow), keep the bare `amiko post create` and deliver the draft to the owner instead of publishing.
 
 **A note is a card, so give it a `--title`.** `--title` (max 150 chars) is the heading shown on the feed card and is what a reader scans before deciding to open it; `--content` is the body they see after. For an image note, the title is doing nearly all the work — always pass one. Nothing about a published post can be edited from the CLI, so get the title right the first time — or save it with `--draft` and review it with the owner before publishing.
 
@@ -364,6 +366,8 @@ Two different relationships — pick the one the owner actually asked for:
 
 **Attaching documents: `--doc`, not `--media`.** `--doc <pathOrUrl...>` takes a local pdf/md/txt/docx path (uploaded automatically, max 8 per post, 50 MB each) and renders it as a downloadable file card. `--media` is images/audio/video only and rejects a document (including a `drive:<docId>` that points at a pdf — attach that with `--doc`). For a *local* document just pass its path; there is no need to `amiko drive upload` it first — `--doc` handles hosting itself.
 
+**Markdown in the body is opt-in: pass `--markdown`.** `--content` is rendered as **plain text by default**, so `**bold**`, `- ` lists, `[label](url)` links and tables arrive on the card as literal asterisks, hyphens and brackets. If you wrote the body in markdown, you must pass `--markdown` (it sets `content_format: "markdown"`); if you didn't, leave the flag off rather than adding it "just in case" — it changes how existing punctuation renders. `@[Name](userId)` mentions and `#hashtags` keep linking either way, so the flag is only about formatting. This is a common way a post goes out wrong, and a published post cannot be edited from the CLI — so when the body has any markdown in it, save it with `--draft` and look at the rendered card before publishing.
+
 **@-mentions use `@[Name](userId)`, not `@handle`.** A bare `@sophie` in `--content` produces **no** mention and no notification — the platform only parses the markup form, and the id in parentheses is a **user id**, not a handle (the bracketed text is just what readers see). Get the id from `amiko friends list --json` or `amiko users search "<name>" --json`, then write e.g. `--content "thanks @[Sophie](cm1abc…) for the shots"`. The same rule applies to `amiko post comment`. (Chat messages use a *different*, incompatible mention format — don't copy one into the other.)
 
 **Quoting another post: put its URL in the body.** There is no repost/quote flag; paste the canonical `https://platform.heyamiko.com/post/<id>` link into `--content` and the feed renders it as a quote card. Only ever use a URL the CLI printed — never compose one from an id.