@withone/cli 1.56.1 → 1.57.1

package/dist/{migrate-IJI3BTWL.js → migrate-TACDLGPD.js}

@@ -3,10 +3,10 @@ import {
   dotPathToJsonbExpr,
   memMigrateCommand,
   reviveStringifiedJson
-} from "./chunk-XWTV7FA3.js";
+} from "./chunk-YTM6HJKA.js";
 import "./chunk-44CV5IMX.js";
 import "./chunk-OLQ55K6B.js";
-import "./chunk-VH46MAE4.js";
+import "./chunk-IMU2X3ZV.js";
 import "./chunk-YMUY55U2.js";
 import "./chunk-6UB623BG.js";
 export {

package/dist/{runtime-65IPTPVD.js → runtime-SX36HGBA.js}

@@ -5,7 +5,7 @@ import {
   resetBackendSingleton,
   updateRecord,
   upsertRecord
-} from "./chunk-VH46MAE4.js";
+} from "./chunk-IMU2X3ZV.js";
 import "./chunk-YMUY55U2.js";
 import "./chunk-6UB623BG.js";
 export {

package/dist/{schema-OO4WK5ND.js → schema-RJC2WQQ6.js}

@@ -6,7 +6,7 @@ import {
 } from "./chunk-OLQ55K6B.js";
 import {
   getBackend
-} from "./chunk-VH46MAE4.js";
+} from "./chunk-IMU2X3ZV.js";
 import "./chunk-YMUY55U2.js";
 import "./chunk-6UB623BG.js";
 

package/dist/{sql-QIVDWTL3.js → sql-SYCWUPNP.js}

@@ -1,9 +1,9 @@
 import {
   memSqlCommand,
   syncSqlCommand
-} from "./chunk-KAF5SVJS.js";
+} from "./chunk-GKAIRI4Y.js";
 import "./chunk-OLQ55K6B.js";
-import "./chunk-VH46MAE4.js";
+import "./chunk-IMU2X3ZV.js";
 import "./chunk-YMUY55U2.js";
 import "./chunk-6UB623BG.js";
 export {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withone/cli",
-  "version": "1.56.1",
+  "version": "1.57.1",
   "description": "CLI for managing One",
   "type": "module",
   "files": [

package/skills/one/SKILL.md

@@ -89,6 +89,26 @@ one --agent actions knowledge <platform> <actionId>
 
 This tells you exactly what parameters are required, how to structure the request, and which flags to use. Never skip this step — without it you'll guess wrong on parameters.
 
+**You get a digest, not always the whole document.** Large docs are trimmed to the request-building sections (method/URL, headers, description, rules, required + optional parameters, sample request, gotchas, error handling). The response tells you what was left out:
+
+- `truncated: true` — some sections are omitted. `truncated: false` — you have everything (and no `sections` list is sent).
+- `sections[]` — the omitted sections only, each with `id`, `heading`, `chars`, and `included` (`false` / `"partial"`). Included sections are the headings you can see in the markdown.
+- The markdown itself ends with a notice naming the omitted sections and the exact commands to load them.
+
+Load more only when you need it (response shapes, response fields, worked examples). Served from the local cache, no network:
+
+```bash
+one --agent actions knowledge <platform> <actionId> --section "Response Fields"   # by heading
+one --agent actions knowledge <platform> <actionId> --section response,optional    # by alias, several at once
+one --agent actions knowledge <platform> <actionId> --full                         # whole document
+```
+
+Aliases: `response`, `fields`, `optional`, `required`, `examples`, `errors`, `success`, `body`, `query`, `path`, `notes`, `behavior`, `gotchas`. An unknown name returns an error listing every available section — retry with one of those ids.
+
+- A `--section` response has `truncated: false` (you got the whole section) and `resolved` (which ids your names matched). It does not repeat the table of contents.
+- If the digest says `sectionsCollapsed: true`, the doc has hundreds of headings and `sections` shows only the top omitted levels (`children` = hidden count). `--toc` lists every heading without the document.
+- Sections named `(appendix)` in the notice are appended reference chunks or companion endpoints, not the action doc itself.
+
 ### 4. Execute
 
 ```bash
@@ -164,6 +184,7 @@ Knowledge and search responses are cached locally (`~/.one/cache/`). Subsequent
 - In `--agent` mode, responses include a `_cache` field: `{"hit": true, "age": 1423, "fresh": true}`; execute responses include `"_preflight": {"cache": "hit"|"miss"}`
 - Use `--no-cache` to force a fresh fetch: works on `knowledge`, `search`, and `execute` (refreshes execute's action-details lookup)
 - Use `--cache-status` to check cache state without fetching
+- `knowledge --section <name>` and `--full` read from the cached document — no extra API call once the doc is cached
 - Manage cache: `one cache list`, `one cache clear`, `one cache update-all`
 - Execution responses are NEVER cached — the action always runs live; only action metadata (docs, method, path, schema) is cached
 
@@ -171,7 +192,7 @@ Knowledge and search responses are cached locally (`~/.one/cache/`). Subsequent
 
 One ships a local memory store (a real Postgres process bootstrapped on demand via the bundled `embedded-postgres` plugin, with a `postgres` plugin available for remote/self-hosted Postgres) that backs both user-authored notes and synced platform data. `one mem <cmd>` is the primary surface; `one sync` is a namespaced alias (`one mem sync ...`) that writes synced rows into the same store.
 
-**Zero-config.** The first `one mem` call on a new machine auto-initializes — no separate `mem init` step required. The `embedded-postgres` plugin downloads its Postgres binaries on first run (~52MB) and writes a daemon PID/port file at `~/.one/pg/.pgserve.json` so subsequent CLI invocations reuse the running cluster. If an OpenAI key is already resolvable (env, `.onerc`, or `config.openaiApiKey`), embeddings enable automatically and search becomes hybrid FTS + semantic. Otherwise you get FTS-only with a structured `_upgrade` hint on every response telling the user how to upgrade.
+**Zero-config.** The first `one mem` call on a new machine auto-initializes — no separate `mem init` step required. The `embedded-postgres` plugin downloads its Postgres binaries on first run (~52MB) and writes a daemon PID/port file at `~/.one/pg/.pgserve.json` so subsequent CLI invocations reuse the running cluster. The daemon listens on 5434, or the next free port if another program holds it; pin one with `one --agent mem config set embedded-postgres.port <n>` (a conflict on a pinned port is an error, not a silent move). If an OpenAI key is already resolvable (env, `.onerc`, or `config.openaiApiKey`), embeddings enable automatically and search becomes hybrid FTS + semantic. Otherwise you get FTS-only with a structured `_upgrade` hint on every response telling the user how to upgrade.
 
 **Listing synced rows.** `mem list <type>` takes a positional namespaced type — there is no `--platform` flag. Synced rows live under `<platform>/<model>` types: