@lotagate/cli 0.1.8 → 0.1.10

package/README.md

@@ -113,6 +113,8 @@ lotagate agent stdio
 
 lotagate exec --json and lotagate exec --jsonl provide structured output for automation. lotagate agent stdio exposes the versioned JSONL protocol; it validates requests, bounds in-flight work, supports cancellation, and emits safe structured errors instead of raw provider failures. The Desktop bridge is available through `lotagate agent desktop`; its version-1 protocol supports image and file uploads with `attachment.begin`, ordered `attachment.chunk`, `attachment.complete`, and `turn.start` attachment references. Image bytes are normalized by the CLI; other files are encoded as SDK-compatible `input_file` data parts. All bytes are chunked before they cross JSONL's bounded line size, and existing Desktop turns without attachments plus all standalone CLI surfaces keep their current behavior.
 
+Desktop turns also emit structured orchestration events when applicable: `plan.started`, `plan.step.started`, `plan.step.completed`, `plan.completed`, `plan.failed`, and `subagent.created`, `subagent.started`, `subagent.activity`, `subagent.completed`, `subagent.completed_with_warning`, `subagent.failed`, or `subagent.cancelled`. These events contain bounded plan metadata and presentation-safe subagent identity, status, last action, and handoff information; they do not expose child-agent content or tool payloads.
+
 Run lotagate help for the complete direct-command reference. The executable command catalog is the source of truth for command arguments and flags.
 
 ## Models and media
@@ -185,6 +187,17 @@ lotagate plugin install <source> --scope user --sha256 <sha256>
 
 Plugins are declarative packages with .lotagate-plugin/plugin.json. The CLI copies and validates them atomically; it does not run package-install scripts. Skills are validated SKILL.md directories and can be user, project, plugin, or immutable bundled skills. Project hooks are loaded only from <project>/.lotagate/hooks/ in a trusted project.
 
+Each project hook is a JSON file with an `event`, executable `command`, optional string-array `args`, and a `timeoutMs` between 100 and 120000. Supported lifecycle events are `session.start`, `prompt.before`, `tool.before`, `tool.after`, `response.after`, and `session.end`. The `tool.before` event runs immediately before a local or MCP tool is executed; `tool.after` runs after it completes.
+
+~~~json
+{
+  "event": "tool.before",
+  "command": "node",
+  "args": [".lotagate/hooks/audit.mjs"],
+  "timeoutMs": 10000
+}
+~~~
+
 ## Configuration and data
 
 Configuration is merged in this order, with later layers taking precedence:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotagate/cli",
-  "version": "0.1.8",
+  "version": "0.1.10",
   "description": "Enterprise-grade terminal client for LotaGate AI agents.",
   "type": "module",
   "license": "MIT",
@@ -69,12 +69,12 @@
     "tiktoken": "^1.0.22"
   },
   "optionalDependencies": {
-    "@lotagate/cli-native-linux-arm64-gnu": "0.1.8",
-    "@lotagate/cli-native-linux-x64-gnu": "0.1.8",
-    "@lotagate/cli-native-macos-arm64": "0.1.8",
-    "@lotagate/cli-native-macos-x64": "0.1.8",
-    "@lotagate/cli-native-windows-arm64": "0.1.8",
-    "@lotagate/cli-native-windows-x64": "0.1.8"
+    "@lotagate/cli-native-linux-arm64-gnu": "0.1.10",
+    "@lotagate/cli-native-linux-x64-gnu": "0.1.10",
+    "@lotagate/cli-native-macos-arm64": "0.1.10",
+    "@lotagate/cli-native-macos-x64": "0.1.10",
+    "@lotagate/cli-native-windows-arm64": "0.1.10",
+    "@lotagate/cli-native-windows-x64": "0.1.10"
   },
   "devDependencies": {
     "@eslint/js": "9.39.5",