mio-agent-runtime 0.8.0 → 0.10.0

package/README.md

@@ -74,6 +74,7 @@ mio task record-outcome --outcome success   Record a task outcome (--yes to appl
 mio --json status           Machine-readable status
 mio --json agents           Machine-readable agents
 mio --json evolution status Machine-readable evolution module health
+mio --version                Print the version and exit (-V)
 ```
 
 ## MCP 工具

package/bin/mio.js

@@ -2797,6 +2797,14 @@ function observeCommand(args) {
   observer.startForeground(MIO_HOME)
 }
 
+function versionCommand(useJson) {
+  // Read from the package manifest so the installed copy reports its own version
+  // instead of a hardcoded string that drifts on every release.
+  const pkg = require('../package.json')
+  if (useJson) console.log(JSON.stringify({ name: pkg.name, version: pkg.version }))
+  else console.log(pkg.version)
+}
+
 function help() {
   console.log(`Mio Agent Runtime CLI
 
@@ -2860,6 +2868,7 @@ Usage:
   mio --json status           Machine-readable status
   mio --json agents           Machine-readable agents
   mio --json evolution status Machine-readable evolution module health
+  mio --version                Print the version and exit (-V)
 `)
 }
 
@@ -2915,6 +2924,9 @@ async function main() {
       return digestCommand(args, useJson)
     case 'evolution':
       return evolutionCommand(args, useJson)
+    case '--version':
+    case '-V':
+      return versionCommand(useJson)
     case 'help':
     case '--help':
       return help()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mio-agent-runtime",
-  "version": "0.8.0",
+  "version": "0.10.0",
   "description": "Mio Agent Runtime installer and MCP intelligence layer",
   "license": "MIT",
   "type": "commonjs",

package/server/insight-store.js

@@ -11,10 +11,24 @@
 
 const path = require('path')
 
+// Same two-step resolution as server/runtime-modules.js: the published package
+// first, then the workspace source. In a checkout the @akemi-mio/* packages are
+// NOT linked into node_modules (there is no node_modules/@akemi-mio at all), so
+// without the fallback every mio.insight.* tool stayed gated off even though the
+// source sits right there in packages/insight. In a published install only the
+// package exists, so the fallback never runs.
+function loadInsight() {
+  try {
+    return require('@akemi-mio/insight')
+  } catch (_) {
+    return require(path.resolve(__dirname, '..', '..', 'insight'))
+  }
+}
+
 let InsightStore = null
 let InsightGenerator = null
 try {
-  const insight = require('@akemi-mio/insight')
+  const insight = loadInsight()
   InsightStore = insight.InsightStore
   InsightGenerator = insight.InsightGenerator
 } catch {}

package/server/observer-store.js

@@ -17,10 +17,22 @@ const path = require('path')
 // Observer research pipeline (optional -- installed via @akemi-mio/observer).
 // Loaded lazily at module level so the CLI can report availability without the
 // MCP server having to pass its own handles down.
+// Two-step resolution, same as server/runtime-modules.js and insight-store.js:
+// the published package first, then the workspace source. A checkout has no
+// node_modules/@akemi-mio, so without the fallback the whole mio.observer.*
+// family stays gated off while its source is sitting in packages/observer.
+function loadObserver() {
+  try {
+    return require('@akemi-mio/observer')
+  } catch (_) {
+    return require(path.resolve(__dirname, '..', '..', 'observer'))
+  }
+}
+
 let ObserverStore = null
 let ObserverService = null
 try {
-  const obs = require('@akemi-mio/observer')
+  const obs = loadObserver()
   ObserverStore = obs.ObserverStore
   ObserverService = obs.ObserverService
 } catch {}