@mx-space/cli 0.6.8 → 0.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mx-space/cli",
-  "version": "0.6.8",
+  "version": "0.7.1",
   "description": "Command line interface for mx-space (mx-core) — auth, content, configuration",
   "keywords": [
     "mx-space",
@@ -61,6 +61,7 @@
     "fast-xml-parser": "4.5.6",
     "get-east-asian-width": "^1.6.0",
     "lexical": "^0.44.0",
+    "minisearch": "^7.2.0",
     "open": "^11.0.0",
     "semver": "7.8.0",
     "@mx-space/api-client": "5.0.2"

package/skills/authoring.md

@@ -164,6 +164,67 @@ mxs page update about --subtitle "Updated subtitle" --json
 mxs page get about --output llm
 ```
 
+## `meta` field — built-in presets
+
+The `meta` column on posts, notes, and pages is a free-form JSON record;
+mx-core does not validate keys. However a small set of keys are seeded as
+**built-in presets** (`apps/core/src/modules/meta-preset/meta-preset.service.ts`)
+and the frontend (Shiro / Yohaku) consumes them to render dedicated UI.
+Prefer these keys for the documented purpose; do not invent parallel names.
+
+| Key        | Type                  | Frontend behavior                                                  |
+| ---------- | --------------------- | ------------------------------------------------------------------ |
+| `aiGen`    | number or number[]    | Renders an `AIGenBadge` disclosing AI involvement. See below.      |
+| `cover`    | URL string            | Used as the article / note cover image.                            |
+| `banner`   | object                | Renders a notice banner above the body (`{type, message, className}`). |
+| `keywords` | string[]              | SEO keywords.                                                      |
+| `style`    | string                | Named article style applied by the theme.                          |
+
+### `meta.aiGen` — AI involvement disclosure
+
+When an AI agent (Claude Code, Codex, a custom mxs caller, etc.) contributed to
+a post / note / page, set `meta.aiGen` so the frontend can render the disclosure
+badge. The value is a single preset number, or an array of preset numbers when
+multiple kinds of AI involvement apply. Exclusive values (`-1` handmade, `2`
+fully AI-generated) must not be combined with anything else.
+
+| Value | Label                       | Exclusive |
+| ----- | --------------------------- | --------- |
+| `-1`  | No AI (handcrafted)         | yes       |
+| `0`   | Writing assistance          | no        |
+| `2`   | Fully AI-generated          | yes       |
+| `3`   | Story organization          | no        |
+| `4`   | Title generation            | no        |
+| `8`   | AI-generated imagery        | no        |
+| `9`   | Dictation                   | no        |
+
+Legacy values `1` / `5` / `6` / `7` have been merged into `0` (assist) on the
+frontend; read-side compatibility is kept but new content should use `0`.
+
+Setting via the CLI:
+
+```bash
+# Fully AI-generated body.
+mxs post create --file ./post.xml --meta '{"aiGen":2}' --json
+
+# Mixed involvement: writing assistance + title generation.
+mxs note create --file ./note.xml --meta '{"aiGen":[0,4]}' --json
+
+# Merge from a JSON file.
+mxs post update aws-vless --meta 'file=./meta.json' --json
+```
+
+Rules of thumb for agents:
+
+- If you wrote the full body, set `aiGen: 2`.
+- If you only refined wording, set `aiGen: 0` (or include `0` in the array).
+- If a human authored the body and you only patched metadata (title, tags,
+  summary), do **not** set `aiGen` — leave the field untouched.
+- If `meta.aiGen` is already set and you only patch unrelated fields, preserve
+  the existing value; do not strip it.
+- Prefer the camelCase key `aiGen`. The frontend also accepts legacy `ai_gen`
+  for backward compatibility, but new writes must use `aiGen`.
+
 ## Read-back verification
 
 | Resource | Minimum read-back checks                                                                |