@thehammer/danx-session-telemetry 0.1.46 → 0.1.47

package/dist/.source-hash

@@ -0,0 +1 @@
+ecc5da92c3cb5fcb4ef6668b9d9307de4f31ba3665c1d9437fdc1f45bd6f8b06

package/dist/activity-observer.d.ts

@@ -12,8 +12,8 @@
  * Claude Code's `SubagentStart` / `SubagentStop` hooks carry an `agent_type`
  * before the sub-agent has written anything and a FINISH for every sub-agent,
  * foreground or background. They ship from the danxbot plugin in the
- * claude-plugins repo (DX-3284, `danxbot/scripts/activity-report.mjs`), run the
- * `activity` subcommand of `@thehammer/danx-dashboard-mcp`, and reach the server
+ * claude-plugins repo (DX-3284; DX-4235 moved them into the plugin's hooks module), which calls
+ * `danxbot_api`, and reach the server
  * through `POST /api/plan-sessions/me/activity` — which writes the SAME
  * `dispatch_activities` rows through the same one server writer.
  *
@@ -50,12 +50,12 @@
  * Every row is an upsert keyed `(dispatch_id, kind, activity_id)`, and BOTH
  * producers derive `activity_id` from the same thing: the sub-agent's transcript
  * file basename, `agent-<agent_id>`. The watcher has it directly; a hook has the
- * `agent_id` and builds the same basename from it (`subagentActivityId` in
- * danx-dashboard-mcp's `activity.ts`, which also strips an `agent-` prefix the hooks docs show
- * on some `agent_id`s so both forms reach this key). A hook's `transcript_path` is NOT the
+ * `agent_id` and builds the same basename from it: `agent-` plus the id with one leading `agent-` stripped (the hooks docs
+ * show the prefix on some `agent_id`s), so both forms reach this key. That rule lives in the danxbot plugin's hooks module
+ * (claude-plugins repo). A hook's `transcript_path` is NOT the
  * sub-agent's file — on these events it is the MAIN session's transcript, and only
  * `SubagentStop` also carries the sub-agent's own as `agent_transcript_path`,
- * which the subcommand uses to refuse a key that disagrees. That basename is also
+ * which the plugin uses to refuse a key that disagrees. That basename is also
  * the key the ledger credits the sub-agent's tokens under, which is how
  * per-sub-agent tokens join to the running set without this table carrying a
  * token column. A task notification names the sub-agent by its bare id

package/dist/activity-observer.js

@@ -12,8 +12,8 @@
  * Claude Code's `SubagentStart` / `SubagentStop` hooks carry an `agent_type`
  * before the sub-agent has written anything and a FINISH for every sub-agent,
  * foreground or background. They ship from the danxbot plugin in the
- * claude-plugins repo (DX-3284, `danxbot/scripts/activity-report.mjs`), run the
- * `activity` subcommand of `@thehammer/danx-dashboard-mcp`, and reach the server
+ * claude-plugins repo (DX-3284; DX-4235 moved them into the plugin's hooks module), which calls
+ * `danxbot_api`, and reach the server
  * through `POST /api/plan-sessions/me/activity` — which writes the SAME
  * `dispatch_activities` rows through the same one server writer.
  *
@@ -50,12 +50,12 @@
  * Every row is an upsert keyed `(dispatch_id, kind, activity_id)`, and BOTH
  * producers derive `activity_id` from the same thing: the sub-agent's transcript
  * file basename, `agent-<agent_id>`. The watcher has it directly; a hook has the
- * `agent_id` and builds the same basename from it (`subagentActivityId` in
- * danx-dashboard-mcp's `activity.ts`, which also strips an `agent-` prefix the hooks docs show
- * on some `agent_id`s so both forms reach this key). A hook's `transcript_path` is NOT the
+ * `agent_id` and builds the same basename from it: `agent-` plus the id with one leading `agent-` stripped (the hooks docs
+ * show the prefix on some `agent_id`s), so both forms reach this key. That rule lives in the danxbot plugin's hooks module
+ * (claude-plugins repo). A hook's `transcript_path` is NOT the
  * sub-agent's file — on these events it is the MAIN session's transcript, and only
  * `SubagentStop` also carries the sub-agent's own as `agent_transcript_path`,
- * which the subcommand uses to refuse a key that disagrees. That basename is also
+ * which the plugin uses to refuse a key that disagrees. That basename is also
  * the key the ledger credits the sub-agent's tokens under, which is how
  * per-sub-agent tokens join to the running set without this table carrying a
  * token column. A task notification names the sub-agent by its bare id

package/dist/internal-logger.js

@@ -13,7 +13,7 @@ function emit(level, component, message, error) {
         entry.error = String(error);
     }
     // DX-2954 — every level goes to STDERR. The MCP server's
-    // relay and the one-shot subcommands run this collector; the subcommands' STDOUT is a protocol
+    // relay and the `subagents-live` subcommand run this collector; the subcommand's STDOUT is a protocol
     // channel the plugin parses (and the MCP server's is JSON-RPC), so a log line there
     // would corrupt it. The worker captures both streams.
     console.error(JSON.stringify(entry));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@thehammer/danx-session-telemetry",
-  "version": "0.1.46",
+  "version": "0.1.47",
   "description": "Shared Claude Code transcript collector (DX-2962) — incremental JSONL tailing for the danxbot worker and the danx-dashboard-mcp MCP server's relay, so both run identical collector code.",
   "license": "MIT",
   "type": "module",