@lotics/cli 0.90.0 → 0.91.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/render_page.js +4 -4
- package/dist/src/cli.js +18724 -1273
- package/docs/knowledge_docs.md +3 -1
- package/package.json +2 -1
package/docs/knowledge_docs.md
CHANGED
|
@@ -86,7 +86,9 @@ question without ever loading the rest. Structure your content so it works:
|
|
|
86
86
|
|
|
87
87
|
Send only the fields you're changing. Content edits are **diffs**, not a full rewrite: pass an
|
|
88
88
|
`edits` array (replace / insert / append operations) plus the `expected_version` you got from
|
|
89
|
-
`read_knowledge` (optimistic concurrency — a stale version is rejected).
|
|
89
|
+
`read_knowledge` (optimistic concurrency — a stale version is rejected). Over the CLI, the default
|
|
90
|
+
`read_knowledge` text output omits the version — read `current_version` from `lotics run read_knowledge … --json`.
|
|
91
|
+
Refine structure as you
|
|
90
92
|
learn what users actually ask: add the synonym that failed to match, split the section that was
|
|
91
93
|
too coarse to grep. See `lotics tools update_knowledge` for the edit shape.
|
|
92
94
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lotics/cli",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.91.2",
|
|
4
4
|
"description": "Lotics SDK and CLI for AI agents",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -22,6 +22,7 @@
|
|
|
22
22
|
},
|
|
23
23
|
"devDependencies": {
|
|
24
24
|
"@lotics/docx": "*",
|
|
25
|
+
"@lotics/ooxml": "*",
|
|
25
26
|
"@lotics/shared": "*",
|
|
26
27
|
"@lotics/xlsx": "*",
|
|
27
28
|
"@types/node": "^22.15.21",
|