tanuki-telemetry 1.3.5 → 1.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tanuki-telemetry",
-  "version": "1.3.5",
+  "version": "1.3.6",
   "description": "Workflow monitor and telemetry dashboard for Claude Code autonomous agents",
   "type": "module",
   "bin": {

package/skills/compare-image.md

@@ -15,7 +15,7 @@ Compare two sets of images (reference vs generated) with pixel-diff heatmaps and
 - `template-names`: One or more slide template names to test (space-separated). Matched against `presentation_template.name` in local Supabase DB (case-insensitive LIKE).
 - `--session-id=<id>`: Attach to an existing telemetry session instead of creating a new one.
 - `--skip-generation`: Use existing generated presentations in the DB — don't re-generate.
-- `--output-dir=<path>`: Override output directory (default: `~/junior-main/outputs/slide-comparisons/`)
+- `--output-dir=<path>`: Override output directory (default: `~/.tanuki/data/slide-comparisons/`)
 
 ---
 
@@ -380,7 +380,7 @@ mcp__telemetry__log_event({
     slide_title: "<Title>",                // e.g., "Cover", "Metrics Dashboard"
     severity: "<critical|notable|minor|good>",
     finding_title: "<short title>",        // e.g., "Client logo removed"
-    finding_details: "<full description>", // e.g., "Reference has 'Junior | TRINITY' dual logo..."
+    finding_details: "<full description>", // e.g., "Reference has 'Acme | PARTNER' dual logo..."
     diff_pct: <X.X>,                       // pixel diff percentage for this slide
     comparison_image: "<absolute path>",   // path to the annotated comparison PNG
     ref_image: "<absolute path>",          // path to the reference slide PNG
@@ -414,7 +414,7 @@ metadata: {
   slide_title: "Table of Contents",
   severity: "notable",
   finding_title: "Logo expanded",
-  finding_details: "Reference: icon-only Junior logo. Generated: full 'Junior' wordmark with icon — different logo variant.",
+  finding_details: "Reference: icon-only client logo. Generated: full wordmark with icon — different logo variant.",
   ...
 }
 

package/skills/start-work.md

@@ -17,9 +17,9 @@ These are NON-NEGOTIABLE. Violating any of these makes the session useless for r
 
 **3. UPDATE PLAN STEPS.** Call `mcp__telemetry__update_plan_step` as you start and finish each step. Every step must go through `in_progress` → `completed`/`failed`/`skipped`.
 
-**4. LOG SCREENSHOTS.** Call `mcp__telemetry__log_screenshot` for EVERY screenshot taken. Use the full absolute path: `/Users/ykim/junior-main/outputs/<worktree>/screenshots/<name>.png`
+**4. LOG SCREENSHOTS.** Call `mcp__telemetry__log_screenshot` for EVERY screenshot taken. Use the full absolute path: `$TANUKI_OUTPUTS/<worktree>/screenshots/<name>.png`
 
-**4b. LOG ARTIFACTS.** Call `mcp__telemetry__log_artifact` for EVERY non-screenshot file output: generated reports, templates, rubrics, PPTX files, summaries, configs, CSV exports, etc. Use the full absolute path: `/Users/ykim/junior-main/outputs/<worktree>/artifacts/<name>.<ext>`. Artifacts appear on the dashboard with download links. Screenshots go to `log_screenshot`; everything else goes to `log_artifact`.
+**4b. LOG ARTIFACTS.** Call `mcp__telemetry__log_artifact` for EVERY non-screenshot file output: generated reports, templates, rubrics, PPTX files, summaries, configs, CSV exports, etc. Use the full absolute path: `$TANUKI_OUTPUTS/<worktree>/artifacts/<name>.<ext>`. Artifacts appear on the dashboard with download links. Screenshots go to `log_screenshot`; everything else goes to `log_artifact`.
 
 **5. INCLUDE METADATA.** Every `log_event` call MUST include the `metadata` field with structured context (file paths, commands, exit codes, error output, decision reasoning). Events without metadata are useless.
 
@@ -64,7 +64,7 @@ These are NON-NEGOTIABLE. Violating any of these makes the session useless for r
 /start-work <worktree-name(optional)> <flags(optional)>
 ```
 
-**Default repo:** `~/junior-main/junior` (hardcoded — worktrees go in `~/junior-main/junior-worktrees/`)
+**Default repo:** `$PROJECT_DIR` (set in environment or CLAUDE.md — worktrees go in `$WORKTREES_DIR/`)
 
 **Arguments:**
 - `worktree-name`: Name for worktree/workspace. If omitted, will be derived from ticket or user input.
@@ -96,11 +96,11 @@ Before starting any work, verify the telemetry server is running:
    - Tell the user: "Telemetry MCP is not running. Attempting to start it..."
    - Try to start it:
      ```bash
-     docker run --rm -d --name telemetry-mcp -i -v /Users/ykim/junior-main/outputs:/data telemetry-mcp:latest
+     docker run --rm -d --name telemetry-mcp -i -v $TANUKI_OUTPUTS:/data telemetry-mcp:latest
      ```
    - If the image doesn't exist, rebuild it:
      ```bash
-     cd /Users/ykim/.claude/mcp-servers/telemetry && docker compose build && docker compose up -d
+     cd ~/.claude/mcp-servers/telemetry && docker compose build && docker compose up -d
      ```
    - Retry the `list_sessions` call
    - If it STILL fails → warn the user: "Telemetry unavailable — proceeding without logging. Run `docker compose up` in `~/.claude/mcp-servers/telemetry/` to fix."
@@ -187,7 +187,7 @@ Structure metadata depending on event type:
   ```
 - **any event with a screenshot** — include `screenshot_path` in metadata to attach the image inline on the dashboard:
   ```json
-  { "screenshot_path": "/Users/ykim/junior-main/outputs/<worktree>/screenshots/01-feature.png", "description": "Test failure output" }
+  { "screenshot_path": "$TANUKI_OUTPUTS/<worktree>/screenshots/01-feature.png", "description": "Test failure output" }
   ```
   The dashboard renders the screenshot inline when you expand the event. Use this whenever a screenshot provides evidence for a decision, error, or finding.
 
@@ -202,14 +202,14 @@ If you do something that would be a meaningful line in a `git log` or a step you
 ### 1.0 Parse Arguments
 
 Parse `$ARGUMENTS`:
-- `home-dir` is always `~/junior-main/junior` (hardcoded)
-- Worktree directory is always `~/junior-main/junior-worktrees/`
+- `home-dir` is `$PROJECT_DIR` (from environment or CLAUDE.md)
+- Worktree directory is `$WORKTREES_DIR/`
 - Detect flags: `--remote`, `--resume`, `--parallel`, `--context="<text>"`
 - Extract `--context` value if present (everything between the quotes)
 - Remaining non-flag args: first = `worktree-name`
 
-**Auto-detect current worktree:** If no `worktree-name` is provided (with or without `--resume`), check if the current working directory is inside `~/junior-main/junior-worktrees/`. If so:
-- Infer `worktree-name` from the directory name (e.g., cwd `~/junior-main/junior-worktrees/fix-auth-bug` → `worktree-name = fix-auth-bug`)
+**Auto-detect current worktree:** If no `worktree-name` is provided (with or without `--resume`), check if the current working directory is inside `$WORKTREES_DIR/`. If so:
+- Infer `worktree-name` from the directory name (e.g., cwd `$WORKTREES_DIR/fix-auth-bug` → `worktree-name = fix-auth-bug`)
 - Automatically treat this as a `--resume` flow (no need for the flag)
 
 ### 1.1 Environment Setup
@@ -223,23 +223,23 @@ Parse `$ARGUMENTS`:
    ```
 3. `cd` into the worktree (if not already there)
 4. Check `git status` — report any uncommitted work
-5. Check if `~/junior-main/outputs/<worktree-name>/handoff.md` exists from a prior session — if so, read it and present a recap of where the last agent left off, what's working, what's not, and recommended next steps
-6. Check if `~/junior-main/outputs/<worktree-name>/summary.md` exists — if so, the work may already be done
+5. Check if `$TANUKI_OUTPUTS/<worktree-name>/handoff.md` exists from a prior session — if so, read it and present a recap of where the last agent left off, what's working, what's not, and recommended next steps
+6. Check if `$TANUKI_OUTPUTS/<worktree-name>/summary.md` exists — if so, the work may already be done
 7. Skip to **PHASE 2** (scope)
 
 #### If `--remote` flag (new Coder workspace):
 
 1. Create workspace:
    ```bash
-   coder create <worktree-name> --template junior-workspace --yes
+   coder create <worktree-name> --template <workspace-template> --yes
    ```
 2. Set up branch:
    ```bash
-   coder ssh <worktree-name> -- bash -c 'cd /workspace/junior && git fetch origin && git checkout -b <worktree-name> origin/develop && git pull'
+   coder ssh <worktree-name> -- bash -c 'cd /workspace/$PROJECT && git fetch origin && git checkout -b <worktree-name> origin/develop && git pull'
    ```
 3. Install deps:
    ```bash
-   coder ssh <worktree-name> -- bash -c 'cd /workspace/junior && yarn install'
+   coder ssh <worktree-name> -- bash -c 'cd /workspace/$PROJECT && yarn install'
    ```
 
 #### Default (new local worktree):
@@ -943,7 +943,7 @@ cd <worktree-dir> && yarn dev &
 
 **Remote mode:**
 ```bash
-coder ssh <name> -- bash -c 'cd /workspace/junior && yarn dev &'
+coder ssh <name> -- bash -c 'cd /workspace/$PROJECT && yarn dev &'
 # Get the forwarded port URL
 ```
 
@@ -959,7 +959,7 @@ Wait for the dev server to be ready (poll `http://localhost:3000` or the remote
 
 ```bash
 # 1. Create the screenshots directory first
-mkdir -p ~/junior-main/outputs/<worktree-name>/screenshots ~/junior-main/outputs/<worktree-name>/artifacts
+mkdir -p $TANUKI_OUTPUTS/<worktree-name>/screenshots $TANUKI_OUTPUTS/<worktree-name>/artifacts
 ```
 
 ```bash
@@ -967,7 +967,7 @@ mkdir -p ~/junior-main/outputs/<worktree-name>/screenshots ~/junior-main/outputs
 npx agent-browser \
   --url "http://localhost:3000/<page>" \
   --width 1920 --height 1080 \
-  --output ~/junior-main/outputs/<worktree-name>/screenshots/01-feature-main-view.png
+  --output $TANUKI_OUTPUTS/<worktree-name>/screenshots/01-feature-main-view.png
 ```
 
 ```
@@ -976,7 +976,7 @@ mcp__telemetry__log_screenshot({
   session_id,
   phase: "verification",
   description: "Main feature view with data loaded",
-  file_path: "/Users/ykim/junior-main/outputs/<worktree-name>/screenshots/01-feature-main-view.png"
+  file_path: "$TANUKI_OUTPUTS/<worktree-name>/screenshots/01-feature-main-view.png"
 })
 ```
 
@@ -1002,7 +1002,7 @@ mcp__telemetry__log_event({
 
 Name screenshots descriptively:
 ```
-~/junior-main/outputs/<worktree-name>/screenshots/
+$TANUKI_OUTPUTS/<worktree-name>/screenshots/
   01-feature-main-view.png
   01-feature-main-view-comparison.png   (if comparing to reference)
   01-feature-main-view-fixed.png        (after a fix iteration)
@@ -1092,7 +1092,7 @@ kill %1  # or the appropriate PID
 Output goes in the **centralized outputs directory**, not inside the worktree:
 
 ```
-~/junior-main/outputs/<worktree-name>/
+$TANUKI_OUTPUTS/<worktree-name>/
   summary.md
   quality-analysis.md    (if iterating on quality — tracks score progression across sessions)
   handoff.md
@@ -1134,7 +1134,7 @@ mcp__telemetry__log_event({
   session_id, phase: "deliverables", event_type: "info",
   message: "Quality analysis report: <overall-score>/10",
   metadata: {
-    report_path: "~/junior-main/outputs/<worktree>/quality-analysis.md",
+    report_path: "$TANUKI_OUTPUTS/<worktree>/quality-analysis.md",
     overall_score: <number>,
     score_breakdown: { <category>: <score>, ... },
     version: "<V1|V2|V3...>"
@@ -1143,7 +1143,7 @@ mcp__telemetry__log_event({
 ```
 
 ```bash
-mkdir -p ~/junior-main/outputs/<worktree-name>/screenshots ~/junior-main/outputs/<worktree-name>/artifacts
+mkdir -p $TANUKI_OUTPUTS/<worktree-name>/screenshots $TANUKI_OUTPUTS/<worktree-name>/artifacts
 ```
 
 ### 5.2 Write Summary
@@ -1189,7 +1189,7 @@ Log the summary as an artifact:
 ```
 mcp__telemetry__log_artifact({
   session_id,
-  file_path: "~/junior-main/outputs/<worktree-name>/summary.md",
+  file_path: "$TANUKI_OUTPUTS/<worktree-name>/summary.md",
   artifact_type: "summary",
   description: "Work summary for <worktree-name>"
 })
@@ -1271,7 +1271,7 @@ mcp__telemetry__log_session_end({
 
 ### 5.6.1 Write Handoff Notes
 
-**Always** write handoff notes to `~/junior-main/outputs/<worktree-name>/handoff.md`, regardless of session outcome. If the session is interrupted, failed, or even completed successfully, the next `--resume` session needs context.
+**Always** write handoff notes to `$TANUKI_OUTPUTS/<worktree-name>/handoff.md`, regardless of session outcome. If the session is interrupted, failed, or even completed successfully, the next `--resume` session needs context.
 
 ```markdown
 # Handoff: <worktree-name>
@@ -1315,7 +1315,7 @@ mcp__telemetry__log_event({
 ```
 mcp__telemetry__log_artifact({
   session_id,
-  file_path: "~/junior-main/outputs/<worktree-name>/handoff.md",
+  file_path: "$TANUKI_OUTPUTS/<worktree-name>/handoff.md",
   artifact_type: "report",
   description: "Handoff notes for <worktree-name>"
 })
@@ -1358,7 +1358,7 @@ yarn dev
 # Then visit <relevant-url>
 
 ### Telemetry: http://localhost:3333
-### Output report: ~/junior-main/outputs/<worktree-name>/summary.md
+### Output report: $TANUKI_OUTPUTS/<worktree-name>/summary.md
 ```
 
 ---
@@ -1551,8 +1551,8 @@ mcp__telemetry__log_event({
 
 ```bash
 # For each stream — use descriptive task-based names, NOT "stream-1":
-git worktree add ~/junior-main/junior-worktrees/<parent>--<task-slug> -b <parent-branch>/<task-slug>
-cmux new-workspace --cwd ~/junior-main/junior-worktrees/<parent>--<task-slug> --command "claude"
+git worktree add $WORKTREES_DIR/<parent>--<task-slug> -b <parent-branch>/<task-slug>
+cmux new-workspace --cwd $WORKTREES_DIR/<parent>--<task-slug> --command "claude"
 ```
 
 #### Step 3: Inject the sub-agent prompt via cmux send