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

package/README.md

@@ -533,7 +533,7 @@ src/
 │   ├── voice.ts          # voice design, voice create, voice clone, voice reset
 │   ├── avatar.ts         # avatar update
 │   ├── friends.ts        # friends list, requests, add, accept, remove, matches, reports
-│   ├── users.ts          # users search, profile
+│   ├── users.ts          # users search, profile, follow/unfollow/followers/following
 │   └── feed.ts           # feed, post create/drafts/publish, post comment
 └── lib/
     ├── config.ts          # defaults + resolved auth wrapper
@@ -591,11 +591,19 @@ amiko friends reports view <reportId>
 # Users
 amiko users search <query>              # find users by name/handle
 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
+amiko users followers <handleOrId>      # who follows them (--limit 1-50, --cursor)
+amiko users following <handleOrId>      # who they follow
 
-# Feed & posts
+# Feed & posts (a.k.a. notes)
 amiko feed                              # friends feed (default)
-amiko feed --type for_you --limit 20
+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 --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 --content "wip idea" --draft         # save a draft — no share URL until published
@@ -625,6 +633,13 @@ npm publish
 
 ## Changelog
 
+### 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.
+- **Follows: `amiko users follow / unfollow / follow-status / followers / following`.** Wraps `POST|DELETE|GET /api/users/<handleOrId>/follow` and the two list routes (`--limit` 1–50, `--cursor`; the CLI rejects a larger limit rather than letting the server silently clamp). Every slot takes a **handle or a user id**. Following is one-way and takes effect immediately — distinct from `amiko friends add`, which is a mutual request the other side must accept; the SKILL now carries a comparison table so agents stop conflating them.
+- **`amiko feed --type` now mirrors the app's tabs: `all` / `following` / `media`** (plus `friends`, and `humans` / `amikos`). `all` is the UI's name for the API's `for_you`, so both spellings are accepted and normalized on the way out. The server silently degrades an unrecognized type to `for_you`, which reads as "the filter worked" when it didn't — the CLI validates up front and exits with the allowed list rather than issuing a request. `media` is the trap that rule was written for: `/api/feed?type=media` degrades to `for_you`, because the Media tab is served by a **different endpoint** (`/api/media/feed`, site-wide public creations with a different response shape) — so `--type media` routes there instead, with `--kind image|audio|video` for that endpoint's own filter (named `--kind` because its wire param is also called `type`).
+- **SKILL.md**: notes/posts are the same surface; a note is a card so lead with `--title`; image- and document-only notes need no body; documents go through `--doc`, never `amiko drive upload`; **@-mentions must be written `@[Name](userId)`** — a bare `@handle` produces no mention and no notification; quoting a post means pasting its canonical URL into `--content`; follow-vs-friend routing table; which `--type` answers which question.
+
 ### 0.14.0-beta.24
 
 - **Private friend nicknames: `amiko friends nickname`.** Manage the owner's private nicknames for friends against amiko-web `/api/friends/{friendshipId}/nickname`: bare `nickname` (or `nickname list`) pages the whole friends list and shows every nickname set, `set <friend> "<nickname>"` adds or changes one (max 50 characters, validated client-side before any request), `remove <friend>` clears it (soft no-op when none is set). `<friend>` resolves against accepted user friends only — by name, `@handle`, user id, friendship id, or the current nickname — with ambiguity reported, never guessed. Mutations are `--yes`-gated (private resource, plain confirm); `amiko friends list` now also renders a NICKNAME column. **Requires the companion amiko-web deploy (`feat/friend-nicknames`)** — on an older server, reads work but `set`/`remove` return 403 (the CLI prints the deploy hint).