@heyamiko/amiko-cli 0.14.0-beta.25 → 0.14.0-beta.26

package/README.md

@@ -128,6 +128,7 @@ amiko create image "logo" --aspect 16:9 --model gpt-image-2     # widescreen, Op
 amiko create image "a sunset" --pay credits --yes               # pay with Amiko account credits (unified accounts)
 amiko create video "a whale in space" --resolution 768P --seconds 6
 amiko create video "animate cover" --first-frame https://.../cover.png --yes
+amiko create video "a slow pan over dunes at dusk" --model MiniMax-H3 --seconds 12 --resolution 2K --aspect 21:9 --yes
 amiko create video "dance clip" --model dreamina-seedance-2-0-fast-260128 \
   --reference-image https://.../ref1.png --reference-audio https://.../beat.mp3 --generate-audio --yes
 amiko create tts "Hello world" --voice 21m00Tcm4TlvDq8ikWAM
@@ -135,7 +136,7 @@ amiko create tts "Hello world" --provider minimax --model speech-2.8-turbo
 amiko create tts "Hello" --provider minimax --voice English_expressive_narrator --yes
 amiko voice clone ./me.mp3 --provider minimax
 amiko voice clone ./me.mp3 --provider elevenlabs
-amiko create music "lo-fi chill beat" --duration 30000
+amiko create music "lo-fi chill beat" --duration 30          # seconds
 amiko create music --lyrics "..." --instrumental               # instrumental
 amiko create sfx "thunder and heavy rain" --duration 5
 amiko create image "banner" --raw                               # raw JSON
@@ -163,21 +164,23 @@ Modes: `image`, `video`, `tts`, `music`, `sfx` (mirrors the platform Create Stud
 
 | Flag | Default | Description |
 |------|---------|-------------|
-| `--model <model>` | smart | Video model (`MiniMax-Hailuo-*`, `dreamina-seedance-2-0-fast-260128`, …). Default: `MiniMax-Hailuo-02` for prompt-only (T2V), `MiniMax-Hailuo-2.3-Fast` when `--first-frame` is given (I2V) |
-| `--resolution <res>` | `768P` | `512P`, `720P`, `768P`, `1080P` |
-| `--seconds <n>` | `6` | Clip length: `6` or `10` |
-| `--aspect <ratio>` | — | Aspect ratio (provider-dependent) |
+| `--model <model>` | smart | Video model (`MiniMax-Hailuo-*`, `MiniMax-H3`, `dreamina-seedance-2-0-fast-260128`, …). Default: `MiniMax-Hailuo-02` for prompt-only (T2V), `MiniMax-Hailuo-2.3-Fast` when `--first-frame` is given (I2V) |
+| `--resolution <res>` | `768P` | `512P`, `720P`, `768P`, `1080P`; `MiniMax-H3` only `768P` or `2K` |
+| `--seconds <n>` | `6` | Clip length: `6`/`10` (Hailuo), `4`/`6`/`8` (Veo), `4`/`6`/`8`/`10` (Grok, Seedance), any whole number `4`–`15` (`MiniMax-H3`) |
+| `--aspect <ratio>` | — | Aspect ratio (provider-dependent). `MiniMax-H3` text-to-video needs a concrete ratio (`21:9`, `16:9`, `4:3`, `1:1`, `3:4`, `9:16`) and defaults to `16:9` when omitted |
 | `--first-frame <url>` | — | Image-to-video: first frame URL or data URI |
 | `--last-frame <url>` | — | First-and-last-frame video: ending frame URL or data URI |
-| `--reference-image <url>` | — | Seedance multimodal reference image (repeatable, max 9) |
-| `--reference-video <url>` | — | Seedance multimodal reference video (repeatable, max 3) |
-| `--reference-audio <url>` | — | Seedance multimodal reference audio (repeatable, max 3) |
-| `--subject-reference <url>` | — | MiniMax S2V subject/character reference image |
+| `--reference-image <url>` | — | Seedance / `MiniMax-H3` reference image (repeatable, max 9; H3 surcharges images past the 5th) |
+| `--reference-video <url>` | — | Seedance / `MiniMax-H3` reference video (repeatable, max 3; H3 bills the input seconds too) |
+| `--reference-audio <url>` | — | Seedance / `MiniMax-H3` reference audio (repeatable, max 3; H3 needs an image or video alongside) |
+| `--subject-reference <url>` | — | MiniMax S2V / H3 subject/character reference image |
 | `--generate-audio` | — | Seedance: generate audio in the output |
 | `--no-generate-audio` | — | Seedance: output silent video |
 
 Reference flags accept URLs or data URIs (not local paths). Typical I2V flow: `create image` → `create status <jobId>` for the image URL → `create video --first-frame <url>`.
 
+**MiniMax-H3** (aliases `h3`, `hailuo-03`) is MiniMax's v2 video API and follows its own rules: a prompt is required in every mode (≤7000 chars), clips run any whole number of seconds from 4 to 15, only `768P` and `2K` exist, and it is billed **per second** (plus reference-video input seconds and a per-image surcharge past 5 reference images), so the quote scales with `--seconds`. It does text-to-video, first/last-frame image-to-video, and reference-to-video (`--reference-image`/`--reference-video`/`--reference-audio`), but a frame and a reference cannot be combined in one job. The CLI checks all of that before the quote and approval prompt, so a bad combination never costs a confirmation round-trip.
+
 **`amiko create tts <text>`**
 
 | Flag | Default | Description |
@@ -203,7 +206,7 @@ Examples: `amiko create tts "Hi" --provider minimax --yes` · `amiko create tts
 |------|---------|-------------|
 | `--model <model>` | `music-2.6` | `music_v1`, `music-2.6`, `music-cover` |
 | `--lyrics <lyrics>` | — | Lyrics (optional) |
-| `--duration <ms>` | — | Length in milliseconds |
+| `--duration <seconds>` | — | Track length in seconds, 1–300. `music-3.0` bills per second, so this sets the price |
 | `--instrumental` | — | Instrumental (no vocals) |
 
 **`amiko create sfx <text>`**
@@ -576,7 +579,7 @@ amiko voice reset --yes
 amiko avatar update --file ./portrait.png --yes
 
 # Friends
-amiko friends list                      # list
+amiko friends list                      # ENTIRE friend list + exact total, in one call
 amiko friends requests                  # pending requests (incoming + outgoing)
 amiko friends add --id <userId>
 amiko friends accept <friendshipId>
@@ -589,7 +592,8 @@ amiko friends reports list              # friend matching reports
 amiko friends reports view <reportId>
 
 # Users
-amiko users search <query>              # find users by name/handle
+amiko users search <query>              # find users by name/handle (one page, --limit default 10)
+amiko users search <query> --all        # every match, for "how many people match X"
 amiko users profile <handle>            # public profile
 amiko users follow <handleOrId>         # follow (one-way, no approval); unfollow to undo
 amiko users follow-status <handleOrId>  # do I follow them / do they follow me
@@ -606,8 +610,10 @@ amiko post create --title "Kyoto, 6am" --media ./shot.webp # image-only note —
 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 drafts                                       # list draft posts (--limit/--offset/--json)
+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"
 amiko post comment --id <postId> --comment "nice!" --media https://...jpg
@@ -633,6 +639,28 @@ npm publish
 
 ## Changelog
 
+### 0.14.0-beta.26 (`beta` dist-tag — `npm i -g @heyamiko/amiko-cli@beta`)
+
+- **`amiko create video --model MiniMax-H3`** (aliases `h3`, `hailuo-03`): MiniMax's v2 video model, already live in mpp-service and amiko-web, is now reachable from the CLI. H3 breaks every local rule the video command enforced for Hailuo, so it gets its own pre-flight: `--seconds` accepts any whole number 4–15 (was hard-coded `6|10`), `--resolution` must be `768P` or `2K` (case-insensitive, canonicalized on the wire), and text-to-video needs a concrete `--aspect` — the CLI defaults it to `16:9` and prints a dim note, because the server only rejects the missing ratio *after* the owner has approved the spend. Frame/reference runs are left alone (H3 infers the ratio from the input). All checks run before the quote so an invalid job never costs an approval round-trip.
+- **`--seconds` for non-H3 models widened from `6|10` to `4|6|8|10`**, matching amiko-web's own gate. The old check rejected `8`, which Veo and Seedance accept, and `4`, which Veo/Grok/Seedance accept; mpp still enforces the per-provider subset (Hailuo remains `6|10`). The error now points at `--model MiniMax-H3` for anything else.
+- Reference flags (`--reference-image/video/audio`, `--subject-reference`) document that they drive H3 reference-to-video too.
+
+### 0.14.2
+
+- **`--media drive:<docId>`** (new source for `post create` and `post comment`): attach a media file already in the twin's Drive — an upload, or a Create Studio generation, which `saveCreationToDrive` mirrors into the "Create Studio Files" folder. The id comes from `amiko drive list --json`. This closes the gap where the only way to post an *audio or video* file the twin already owned was to have kept the original `amiko create` URL: `--media` takes local paths for images only, and a Drive signed URL expires.
+- **No amiko-web change was needed, and this is why.** A Drive doc's `file_url` is stored in *public* form (`…/storage/v1/object/public/docs/<path>`) by all three write paths (`uploadDocumentToSupabase`, `createDocSignedUpload`, `saveCreationToDrive`) even though the `docs` bucket is private. `/api/posts` accepts it (`isAllowedPostMediaUrl` checks host + `/storage/v1/object/` only), then `ensurePostMediaUrl` sees a non-`post-media` bucket and does a **service-role server-side copy into `post-media`**, returning a durable URL — so the post never links the private object and never expires. If that copy fails, the fallback reachability probe on a private-bucket URL 4xxs and the route rejects the post rather than storing a dead link. This mirrors what amiko-web's own `DriveMediaPicker` already does (it forwards the same `file_url` under the same MIME allowlist), so the CLI is matching shipped behaviour, not inventing a path.
+- **The drive ref honours the command's `--twin`.** Docs are scoped by `twin_id`; `resolveMediaUrls` now takes the caller's `--twin` instead of re-resolving the default twin, so `post comment --twin <other> --media drive:<id>` no longer 404s on an id `drive list --twin <other>` had just printed.
+- **Two guards on the resolved row.** A `file_url` that isn't Amiko public storage is refused locally — only `source`-tagged Doc rows are pinned to the twin's storage namespace server-side, so an ordinary row can hold any URL, and letting it through produced a `/api/posts` 400 naming neither the ref nor the doc. And the image/audio/video MIME check falls back to the **filename extension** when `file_type` is `application/octet-stream`: Create Studio stores `assetMime || "application/octet-stream"` and the job's `mime_type` is nullable, so a real mp3 can arrive typeless — refusing it with "attach it with `--doc`" would be wrong advice about an attachable file.
+- **SKILL.md**: `--media` now documents its three sources (local image path / Amiko-hosted URL / `drive:<docId>`), says a Drive **signed URL** and a `/d/<slug>` share link are both rejected, and notes that a `drive:` ref pointing at a pdf belongs on `--doc`. New Examples row for "post the audio/image from my Drive".
+
+### 0.14.1
+
+- **`amiko post likers <postId>`** (new): lists everyone who liked a post, paging `GET /api/posts/[id]/likes` to completeness so "who / which friends liked this" is answered from the whole set. Cross-reference the printed user ids against `amiko friends list` for the "which *friends*" variant. The route is **owner-only** (`post.user_id !== user.id` → 403), so the command says so in `--help` and turns the server's generic 403 into a message naming the rule — an agent shouldn't read it as a broken login and retry.
+- **`amiko users search --all`** (new flag). Search stays a one-page lookup by default and `--limit` works again; `--all` is what pages through every match, for "how many people match X". Full paging is capped at 200 (10 requests at the server's 20-row page limit) rather than the shared 2000, because search is ranked recall — nobody needs the 2000th match, and a broad query shouldn't cost a hundred round trips.
+- **`amiko friends list` reports the server's exact total.** `/api/friends` without `limit` already returns the whole list *and* an authoritative `pagination.total` in one request; the header count now comes from `total` instead of the row count. An earlier attempt to paginate this command was reverted — it added ~19 requests, capped the set at 2000, and replaced an exact server-side number with an approximation.
+- **New `src/lib/paginate.ts`**: `fetchAllCursor` follows `hasMore`/`nextCursor` to completeness behind a safety cap, returning `{ items, partial }`. Exhaustion is checked *before* the cap so a set that ends exactly on the cap reports complete — flagging it `partial` would be the same lie about a count, inverted. When the cap really is hit, callers print `⚠ Partial results` and JSON carries `"partial": true` with an `N+` count.
+- **SKILL.md**: new top-level **"Counts & full lists — never answer from the first page"** section (promoted out of Friends, since two of its three commands aren't friends commands) with a question → command → where-the-number-comes-from table; `post likers`'s owner-only rule; the `users search` row in the "Who should I meet?" table now notes one-page-by-default vs `--all`; Examples table gains "谁给我点赞了" and "我有多少好友".
+
 ### 0.14.0-beta.25
 
 - **Notes parity: `amiko post create --title` and `--doc`.** amiko-web's Notes composer (the 小红书-style card grid — same `Post` rows, new name) writes fields the CLI had no way to set. `--title <text>` sets the card heading (max 150 chars, counted in **grapheme clusters** to match the server's `Intl.Segmenter`, validated before any request; omitted from the body when unset so older amiko-web deploys still accept the payload). `--doc <pathOrUrl...>` attaches non-media documents that render as downloadable file cards: local paths upload to the public `docs` bucket via `POST /api/upload/post-doc` (≤4 MB) or presigned `POST /api/upload/post-doc/sign` + direct PUT (>4 MB, 50 MB cap — the multipart route dies at the ~4.5 MB serverless body limit), https URLs pass through, and media MIME types are refused with a pointer to `--media`. Max 8 documents — the server silently truncates past that, so the CLI errors instead. `--content` is no longer a `requiredOption`: with `--media` or `--doc` attached the body may be empty (an image-only note is normal), but a post with nothing in it — including `--title` alone — is still rejected client-side, mirroring the server's rule. `feed` and `post drafts` now render titles and a document count.