@danypops/jittor 0.20.0 → 0.21.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danypops/jittor",
-  "version": "0.20.0",
+  "version": "0.21.2",
   "description": "Just-in-Time Token Optimization Router for Pi -- token and context observability with optimization policies",
   "license": "MIT",
   "type": "module",
@@ -8,10 +8,16 @@
   "types": "./src/index.ts",
   "exports": {
     ".": "./src/index.ts",
+    "./usage": "./src/observability/usage.ts",
     "./package.json": "./package.json"
   },
   "sideEffects": false,
   "keywords": ["llm-router", "token-budget"],
+  "zodiac": {
+    "integrations": [
+      { "kind": "vehicle-surface", "vehicleName": "jittor", "title": "Jittor" }
+    ]
+  },
   "bin": {
     "jittor": "src/cli.ts"
   },

package/src/daemon.ts

@@ -137,6 +137,22 @@ export async function startDaemon(
 		handlePath: paths.handle,
 		logger,
 		buildApp: () => createApp({ service, token }),
+		// Publishes into the shared, cross-package Vehicle Handle Directory
+		// (see @danypops/vehicle-server/paths's resolveSharedVehicleHandlePath)
+		// -- without this, a discovering caller with no prior knowledge of
+		// jittor's own private handlePath (e.g. Zodiac's VehicleSurfaceGateway,
+		// resolving purely by vehicleName) can never find a real, running
+		// jittor daemon. Papyrus's own hand-rolled daemon.ts already does this
+		// explicitly; jittor uses this shared startDaemonKit but was never
+		// passing the option that turns the exact same behavior on.
+		vehicleName: "jittor",
+		tokenPath: paths.token,
+		// startDaemon()'s own `env` param was already used for telemetry/
+		// benchmark/catalog source detection above, but never forwarded to
+		// startDaemonKit itself -- meaning the shared-handle write above would
+		// silently always resolve against real process.env regardless of what
+		// env a caller (e.g. a test, or a future multi-instance setup) supplied.
+		env,
 		maintenanceTasks: [
 			{
 				name: "checkpoint",

package/src/observability/usage.ts

@@ -1,3 +1,15 @@
+/**
+ * Exposed as its own package.json subpath export ("@danypops/jittor/usage")
+ * alongside the main barrel: this module and its own single dependency
+ * (constants.ts) are the only fully browser/Node-tsc-safe slice of jittor's
+ * source tree (pure functions and types, no bun:sqlite, no Bun-only
+ * globals) -- importing the whole barrel instead drags in every other
+ * module's own raw `.ts` import specifiers, which a consumer's tsc rejects
+ * outright (TS5097) unless it enables allowImportingTsExtensions project-
+ * wide. A consumer that only needs buildUsageGraph/buildCostGraph/
+ * resolveUsageWindow (e.g. Zodiac's own React usage meter) should import
+ * this subpath directly, not the main entry.
+ */
 import { MAX_USAGE_BUCKETS, MILLISECONDS_PER_DAY, MILLISECONDS_PER_HOUR } from "../constants.ts";
 
 export const USAGE_PERIODS = [