panopticon-cli 0.4.31 → 0.4.33

package/skills/spec-readiness-setup/SKILL.md

@@ -0,0 +1,361 @@
+---
+name: spec-readiness-setup
+description: >
+  Create a customized wrapper for the spec-readiness skill. Configures branding,
+  issue tracker bindings, field mappings, and org-specific conventions. Generates
+  a ready-to-use wrapper skill directory with config.yaml and SKILL.md.
+triggers:
+  - spec readiness setup
+  - setup spec readiness
+  - configure spec readiness
+  - create readiness wrapper
+  - customize readiness skill
+  - spec readiness branding
+  - brand readiness report
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+# Spec Readiness Setup — Wrapper Creator
+
+This skill creates a customized wrapper for the `spec-readiness` core skill. The wrapper binds your organization's branding, issue tracker, field names, and conventions to the generic scoring engine.
+
+## What Gets Created
+
+```
+~/.panopticon/skills/spec-readiness-{name}/
+  SKILL.md       # Wrapper skill that invokes the core with your config
+  config.yaml    # Branding, tracker bindings, field mappings, conventions
+```
+
+After creation, the wrapper is immediately available. Users invoke it by name (e.g., `spec readiness acme MIN-704`) or the core skill auto-detects it.
+
+---
+
+## Workflow
+
+### Step 1: Gather Information
+
+Ask the user the following questions. Use `AskUserQuestion` with sensible defaults. Skip questions the user has already answered in their prompt.
+
+**1. Wrapper name** (used in directory name and skill name):
+- "What should this wrapper be called? This becomes the skill name, e.g., `spec-readiness-acme`"
+- Default: derive from company name (lowercase, kebab-case)
+- Validation: kebab-case, no spaces, alphanumeric + hyphens only
+
+**2. Company / Organization name** (for report branding):
+- "What company or team name should appear on reports?"
+- This appears in the HTML report header and footer
+
+**3. Issue tracker**:
+- "Which issue tracker do you use?"
+- Options: Linear, GitHub Issues, GitLab Issues, Rally, Jira, Other
+- If Other: ask for details, we'll create a custom mapping
+
+**4. Branding colors** (optional):
+- "Do you have brand colors for the report? (Enter hex codes or skip for defaults)"
+- Primary color (header/accents): default `#1e293b` (dark slate)
+- Stripe color (top bar): default matches primary
+- If the user has an existing branding skill, offer to read colors from it
+
+**5. Tracker-specific fields** (based on tracker choice):
+
+For **Linear**:
+- "What's your team name in Linear?"
+- "Do you use a label for customer-directed issues? (e.g., 'Customer Request')"
+
+For **GitHub**:
+- "What's the repo (owner/name)?"
+- "Do you use labels for epics/features? (e.g., 'epic')"
+
+For **GitLab**:
+- "What's the project path?"
+- "Do you use epics or parent issues for features?"
+
+For **Rally**:
+- "What's the MCP tool prefix for your Rally MCP server?"
+- "Do you have a custom estimate field? (e.g., `c_ManDays`)"
+- "Do you have an investment category field for customer-directed work?"
+
+For **Jira**:
+- "What's your Jira instance URL?"
+- "Do you use Epics or another issue type for features?"
+- "Custom estimate field name? (e.g., `story_points`, `customfield_10016`)"
+
+**6. Org-specific conventions** (optional):
+- "Do you use any naming patterns for overflow/carryover issues? (e.g., `[Unfinished]`, `[Part 2]`)"
+- "Do you use any naming patterns for spike/investigation issues? (e.g., `SPIKE:`, `[Investigation]`)"
+- "Any custom footer text for reports?"
+
+### Step 2: Build Tracker Tool Mapping
+
+Based on the tracker choice, generate the tool mapping. These are the MCP tools or CLI commands the core skill will use.
+
+**Linear:**
+```yaml
+tracker:
+  type: linear
+  team: "{team_name}"
+  tools:
+    get_issue: "mcp__linear__get_issue"
+    list_child_issues: "mcp__linear__list_issues"
+    get_comments: "mcp__linear__list_comments"
+    search_issues: "mcp__linear__list_issues"
+    get_relations: "mcp__linear__get_issue"  # with includeRelations=true
+    get_activity_log: null  # not available in Linear
+  fields:
+    identifier: "identifier"
+    estimate: "estimate"
+    status: "status"
+    parent_field: "parentId"
+    customer_directed_label: "{label_or_null}"
+    overflow_markers: []
+```
+
+**GitHub:**
+```yaml
+tracker:
+  type: github
+  repo: "{owner}/{repo}"
+  tools:
+    get_issue: "bash:gh issue view {id} --repo {repo} --json title,body,state,labels,milestone,assignees,comments"
+    list_child_issues: "bash:gh issue list --repo {repo} --search 'parent:{id}' --json number,title,body,state,createdAt"
+    get_comments: "bash:gh issue view {id} --repo {repo} --json comments"
+    search_issues: "bash:gh issue list --repo {repo} --label bug --search '{query}' --json number,title,state"
+    get_relations: "bash:gh issue view {id} --repo {repo} --json body"  # parse from body
+    get_activity_log: "bash:gh api repos/{repo}/issues/{id}/events"
+  fields:
+    identifier: "number"
+    estimate: null  # GitHub has no native estimate field
+    status: "state"
+    parent_field: null  # GitHub uses tasklist / sub-issue references
+    customer_directed_label: "{label_or_null}"
+    overflow_markers: []
+```
+
+**GitLab:**
+```yaml
+tracker:
+  type: gitlab
+  project: "{project_path}"
+  tools:
+    get_issue: "bash:glab issue view {id}"
+    list_child_issues: "bash:glab api '/projects/{project_id}/issues?parent_id={id}'"
+    get_comments: "bash:glab issue note list {id}"
+    search_issues: "bash:glab issue list --label bug --search '{query}'"
+    get_relations: "bash:glab api '/projects/{project_id}/issues/{id}/links'"
+    get_activity_log: "bash:glab api '/projects/{project_id}/issues/{id}/resource_state_events'"
+  fields:
+    identifier: "iid"
+    estimate: "weight"
+    status: "state"
+    parent_field: "parent_id"
+    customer_directed_label: "{label_or_null}"
+    overflow_markers: []
+```
+
+**Rally:**
+```yaml
+tracker:
+  type: rally
+  tools:
+    get_issue: "{mcp_prefix}__get_feature"
+    get_story: "{mcp_prefix}__get_story"
+    get_defect: "{mcp_prefix}__get_defect"
+    list_child_issues: null  # from _collections.UserStories in feature response
+    get_comments: null  # from Discussion collection
+    search_issues: "{mcp_prefix}__search_work_items"
+    get_relations: null  # from Predecessors/Successors collections
+    get_activity_log: "{mcp_prefix}__get_revision_history"
+    search_risks: "{mcp_prefix}__search_risks"
+  fields:
+    identifier: "FormattedID"
+    estimate: "{custom_estimate_field_or_PlanEstimate}"
+    status: "ScheduleState"
+    parent_field: null  # Rally uses Feature→UserStory hierarchy
+    customer_directed_label: null
+    investment_category_field: "{field_or_null}"
+    investment_category_value: "{value_or_null}"
+    overflow_markers:
+      - "[Unfinished]"
+      - "[Continued]"
+```
+
+**Jira:**
+```yaml
+tracker:
+  type: jira
+  url: "{jira_url}"
+  tools:
+    get_issue: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/3/issue/{id}'"
+    list_child_issues: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/2/search?jql=parent={id}'"
+    get_comments: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/3/issue/{id}/comment'"
+    search_issues: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/2/search?jql={jql}'"
+    get_relations: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/3/issue/{id}?fields=issuelinks'"
+    get_activity_log: "bash:curl -s -H 'Authorization: Bearer $JIRA_TOKEN' '{jira_url}/rest/api/3/issue/{id}/changelog'"
+  fields:
+    identifier: "key"
+    estimate: "{custom_field_or_story_points}"
+    status: "status.name"
+    parent_field: "parent.key"
+    customer_directed_label: "{label_or_null}"
+    overflow_markers: []
+```
+
+### Step 3: Generate config.yaml
+
+Assemble the full config from gathered information:
+
+```yaml
+# Spec Readiness Wrapper: {wrapper_name}
+# Generated by spec-readiness-setup on {date}
+
+tracker:
+  type: {type}
+  # ... tracker-specific fields from Step 2
+
+branding:
+  company_name: "{company_name}"
+  primary_color: "{primary_color}"
+  stripe_color: "{stripe_color}"
+  footer_text: "{footer_text_or_null}"
+  logo_url: null
+
+conventions:
+  overflow_markers: {markers_list}
+  spike_patterns:
+    - "spike"
+    - "investigation"
+    - "discovery"
+    - "POC"
+    - "prototype"
+    - "analysis"
+    # ... plus any user-specified patterns
+  estimate_field_custom: "{custom_field_or_null}"
+  investment_category_field: "{field_or_null}"
+  investment_category_value: "{value_or_null}"
+```
+
+### Step 4: Generate Wrapper SKILL.md
+
+Create the wrapper skill that invokes the core:
+
+```markdown
+---
+name: spec-readiness-{name}
+description: >
+  {company_name}-branded requirements readiness scoring. Wraps the core
+  spec-readiness skill with {company_name} branding and {tracker_type}
+  tracker integration. Score issues 0-100 across 5 dimensions.
+triggers:
+  - spec readiness {name}
+  - {name} readiness
+  - {name} spec score
+  # ... include all core triggers too
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - WebFetch
+  - Task
+  {tracker_specific_tools}
+---
+
+# Spec Readiness — {company_name}
+
+This is a branded wrapper for the `spec-readiness` core skill.
+
+## Configuration
+
+- **Tracker:** {tracker_type}
+- **Branding:** {company_name}
+- **Config:** ~/.panopticon/skills/spec-readiness-{name}/config.yaml
+
+## Usage
+
+Invoke exactly like the core skill. This wrapper is auto-detected:
+
+```
+spec readiness {example_id}
+how ready is {example_id}
+readiness check {example_id}
+```
+
+## How It Works
+
+1. This wrapper sets the configuration context (branding, tracker, field mappings)
+2. The core `spec-readiness` skill runs the scoring engine
+3. Reports are generated with {company_name} branding
+
+**To modify configuration**, edit:
+`~/.panopticon/skills/spec-readiness-{name}/config.yaml`
+
+**To update the scoring model**, the core skill at
+`~/.panopticon/skills/spec-readiness/SKILL.md` controls all scoring logic.
+```
+
+### Step 5: Write Files
+
+```bash
+mkdir -p ~/.panopticon/skills/spec-readiness-{name}
+write config.yaml to ~/.panopticon/skills/spec-readiness-{name}/config.yaml
+write SKILL.md to ~/.panopticon/skills/spec-readiness-{name}/SKILL.md
+```
+
+### Step 6: Verify and Report
+
+1. Confirm both files were written
+2. Show the user a summary:
+
+```
+Created spec-readiness wrapper: spec-readiness-{name}
+
+  Location: ~/.panopticon/skills/spec-readiness-{name}/
+  Tracker:  {tracker_type}
+  Branding: {company_name} ({primary_color})
+
+  Files:
+    config.yaml  — tracker bindings, branding, conventions
+    SKILL.md     — wrapper skill definition
+
+  Usage:
+    spec readiness {example_id}
+
+  To customize further, edit:
+    ~/.panopticon/skills/spec-readiness-{name}/config.yaml
+```
+
+3. Ask if they want to run a test assessment on a real issue to verify the setup
+
+---
+
+## Updating an Existing Wrapper
+
+If the user runs this skill and a wrapper already exists:
+
+1. Read the existing `config.yaml`
+2. Show current configuration
+3. Ask what they want to change
+4. Update only the changed fields
+5. Preserve any manual customizations
+
+---
+
+## Examples
+
+```
+User: setup spec readiness
+→ Full wizard: asks all questions
+
+User: create readiness wrapper for Acme using Linear
+→ Skips tracker question, asks remaining
+
+User: configure spec readiness for our team using GitHub Issues on eltmon/panopticon-cli
+→ Skips tracker question and repo question
+
+User: spec readiness branding — change colors to #0891b2
+→ Updates existing wrapper branding only
+```

package/skills/workspace-status/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: workspace-status
+description: Auto-applied when reporting on agent/workspace status. Displays robust workspace information with URLs and commands.
+---
+
+# Workspace Status Display Format
+
+When discussing agent status, workspace setup, or providing updates about spawned agents, ALWAYS include this comprehensive table format.
+
+## Required Information Table
+
+Display workspace details in this exact format:
+
+```markdown
+## Agent: {ISSUE_ID} - {ISSUE_TITLE}
+
+| Field | Value |
+|-------|-------|
+| Issue | {TRACKER_URL} |
+| PR/MR | {PR_OR_MR_URL} (if available) |
+| Workspace | {WORKSPACE_PATH} |
+| **Frontend** | https://feature-{issue-id-lowercase}.{PROJECT_DOMAIN} |
+| **API** | https://api-feature-{issue-id-lowercase}.{PROJECT_DOMAIN} |
+| tmux Session | agent-{issue-id-lowercase} |
+
+## Commands
+
+| Action | Command |
+|--------|---------|
+| **Watch agent** | `tmux attach -t agent-{issue-id-lowercase}` |
+| **Send feedback** | `pan tell {ISSUE_ID} "your message"` |
+| **Approve & merge** | `pan approve {ISSUE_ID}` |
+| Detach | `Ctrl+b` then `d` |
+| Kill | `tmux kill-session -t agent-{issue-id-lowercase}` |
+| Resources | `htop` or `watch -n 5 'free -h'` |
+```
+
+## When to Apply This Format
+
+Use this format when:
+- Spawning a new agent
+- Reporting agent completion
+- Providing agent status updates
+- Resuming or restarting an agent
+- User asks about an agent's status
+- Providing investigation/spike results
+
+## Additional Context (Optional)
+
+After the tables, you may add additional context like:
+- Investigation plan or next steps
+- Important notes about the workspace
+- Special setup or requirements
+- Resource availability status
+
+The tables should ALWAYS come first, followed by any additional narrative.

package/templates/traefik/dynamic/panopticon.yml.template

@@ -36,8 +36,3 @@ http:
       loadBalancer:
         servers:
           - url: "http://host.docker.internal:{{DASHBOARD_API_PORT}}"
-
-tls:
-  certificates:
-    - certFile: /etc/traefik/certs/_wildcard.{{TRAEFIK_DOMAIN}}.pem
-      keyFile: /etc/traefik/certs/_wildcard.{{TRAEFIK_DOMAIN}}-key.pem

package/templates/traefik/traefik.yml

@@ -43,11 +43,3 @@ log:
 # Access Logs
 accessLog:
   format: common
-
-# TLS Configuration
-tls:
-  stores:
-    default:
-      defaultCertificate:
-        certFile: /etc/traefik/certs/_wildcard.pan.localhost.pem
-        keyFile: /etc/traefik/certs/_wildcard.pan.localhost-key.pem

package/dist/chunk-3XAB4IXF.js

@@ -1,51 +0,0 @@
-import {
-  init_config,
-  loadConfig
-} from "./chunk-VU4FLXV5.js";
-import {
-  SOURCE_TRAEFIK_TEMPLATES,
-  TRAEFIK_DYNAMIC_DIR,
-  init_paths
-} from "./chunk-6HXKTOD7.js";
-import {
-  init_esm_shims
-} from "./chunk-ZHC57RCV.js";
-
-// src/lib/traefik.ts
-init_esm_shims();
-init_paths();
-init_config();
-import { existsSync, readFileSync, writeFileSync, mkdirSync, unlinkSync } from "fs";
-import { join } from "path";
-function generatePanopticonTraefikConfig() {
-  const templatePath = join(SOURCE_TRAEFIK_TEMPLATES, "dynamic", "panopticon.yml.template");
-  if (!existsSync(templatePath)) {
-    return false;
-  }
-  const config = loadConfig();
-  const placeholders = {
-    TRAEFIK_DOMAIN: config.traefik?.domain || "pan.localhost",
-    DASHBOARD_PORT: String(config.dashboard.port),
-    DASHBOARD_API_PORT: String(config.dashboard.api_port)
-  };
-  let content = readFileSync(templatePath, "utf-8");
-  for (const [key, value] of Object.entries(placeholders)) {
-    content = content.replace(new RegExp(`\\{\\{${key}\\}\\}`, "g"), value);
-  }
-  mkdirSync(TRAEFIK_DYNAMIC_DIR, { recursive: true });
-  const outputPath = join(TRAEFIK_DYNAMIC_DIR, "panopticon.yml");
-  writeFileSync(outputPath, content, "utf-8");
-  return true;
-}
-function cleanupTemplateFiles() {
-  const copiedTemplate = join(TRAEFIK_DYNAMIC_DIR, "panopticon.yml.template");
-  if (existsSync(copiedTemplate)) {
-    unlinkSync(copiedTemplate);
-  }
-}
-
-export {
-  generatePanopticonTraefikConfig,
-  cleanupTemplateFiles
-};
-//# sourceMappingURL=chunk-3XAB4IXF.js.map

package/dist/chunk-3XAB4IXF.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/lib/traefik.ts"],"sourcesContent":["/**\n * Traefik Configuration Generator\n *\n * Generates the Panopticon dashboard Traefik routing config\n * from a template, substituting values from config.toml.\n */\n\nimport { existsSync, readFileSync, writeFileSync, mkdirSync, unlinkSync } from 'fs';\nimport { join } from 'path';\nimport { TRAEFIK_DYNAMIC_DIR, SOURCE_TRAEFIK_TEMPLATES } from './paths.js';\nimport { loadConfig } from './config.js';\n\n/**\n * Generate panopticon.yml from template using current config values.\n * Safe to call multiple times (idempotent).\n * Returns true if file was written, false if template not found.\n */\nexport function generatePanopticonTraefikConfig(): boolean {\n  const templatePath = join(SOURCE_TRAEFIK_TEMPLATES, 'dynamic', 'panopticon.yml.template');\n  if (!existsSync(templatePath)) {\n    return false;\n  }\n\n  const config = loadConfig();\n  const placeholders: Record<string, string> = {\n    TRAEFIK_DOMAIN: config.traefik?.domain || 'pan.localhost',\n    DASHBOARD_PORT: String(config.dashboard.port),\n    DASHBOARD_API_PORT: String(config.dashboard.api_port),\n  };\n\n  let content = readFileSync(templatePath, 'utf-8');\n  for (const [key, value] of Object.entries(placeholders)) {\n    content = content.replace(new RegExp(`\\\\{\\\\{${key}\\\\}\\\\}`, 'g'), value);\n  }\n\n  mkdirSync(TRAEFIK_DYNAMIC_DIR, { recursive: true });\n  const outputPath = join(TRAEFIK_DYNAMIC_DIR, 'panopticon.yml');\n  writeFileSync(outputPath, content, 'utf-8');\n  return true;\n}\n\n/**\n * Remove any accidentally-copied .template files from the runtime Traefik dir.\n * Called after copyDirectoryRecursive in pan install.\n */\nexport function cleanupTemplateFiles(): void {\n  const copiedTemplate = join(TRAEFIK_DYNAMIC_DIR, 'panopticon.yml.template');\n  if (existsSync(copiedTemplate)) {\n    unlinkSync(copiedTemplate);\n  }\n}\n"],"mappings":";;;;;;;;;;;;;;AAAA;AASA;AACA;AAHA,SAAS,YAAY,cAAc,eAAe,WAAW,kBAAkB;AAC/E,SAAS,YAAY;AASd,SAAS,kCAA2C;AACzD,QAAM,eAAe,KAAK,0BAA0B,WAAW,yBAAyB;AACxF,MAAI,CAAC,WAAW,YAAY,GAAG;AAC7B,WAAO;AAAA,EACT;AAEA,QAAM,SAAS,WAAW;AAC1B,QAAM,eAAuC;AAAA,IAC3C,gBAAgB,OAAO,SAAS,UAAU;AAAA,IAC1C,gBAAgB,OAAO,OAAO,UAAU,IAAI;AAAA,IAC5C,oBAAoB,OAAO,OAAO,UAAU,QAAQ;AAAA,EACtD;AAEA,MAAI,UAAU,aAAa,cAAc,OAAO;AAChD,aAAW,CAAC,KAAK,KAAK,KAAK,OAAO,QAAQ,YAAY,GAAG;AACvD,cAAU,QAAQ,QAAQ,IAAI,OAAO,SAAS,GAAG,UAAU,GAAG,GAAG,KAAK;AAAA,EACxE;AAEA,YAAU,qBAAqB,EAAE,WAAW,KAAK,CAAC;AAClD,QAAM,aAAa,KAAK,qBAAqB,gBAAgB;AAC7D,gBAAc,YAAY,SAAS,OAAO;AAC1C,SAAO;AACT;AAMO,SAAS,uBAA6B;AAC3C,QAAM,iBAAiB,KAAK,qBAAqB,yBAAyB;AAC1E,MAAI,WAAW,cAAc,GAAG;AAC9B,eAAW,cAAc;AAAA,EAC3B;AACF;","names":[]}

package/dist/chunk-6HXKTOD7.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/lib/paths.ts"],"sourcesContent":["import { homedir } from 'os';\nimport { join } from 'path';\nimport { existsSync } from 'fs';\n\n// Panopticon home directory (can be overridden for testing)\nexport const PANOPTICON_HOME = process.env.PANOPTICON_HOME || join(homedir(), '.panopticon');\n\n/** Get PANOPTICON_HOME dynamically (reads env var on each call, useful for testing) */\nexport function getPanopticonHome(): string {\n  return process.env.PANOPTICON_HOME || join(homedir(), '.panopticon');\n}\n\n// Subdirectories\nexport const CONFIG_DIR = PANOPTICON_HOME;\nexport const SKILLS_DIR = join(PANOPTICON_HOME, 'skills');\nexport const COMMANDS_DIR = join(PANOPTICON_HOME, 'commands');\nexport const AGENTS_DIR = join(PANOPTICON_HOME, 'agents');\nexport const BIN_DIR = join(PANOPTICON_HOME, 'bin');\nexport const BACKUPS_DIR = join(PANOPTICON_HOME, 'backups');\nexport const COSTS_DIR = join(PANOPTICON_HOME, 'costs');\nexport const HEARTBEATS_DIR = join(PANOPTICON_HOME, 'heartbeats');\n\n// Traefik directories\nexport const TRAEFIK_DIR = join(PANOPTICON_HOME, 'traefik');\nexport const TRAEFIK_DYNAMIC_DIR = join(TRAEFIK_DIR, 'dynamic');\nexport const TRAEFIK_CERTS_DIR = join(TRAEFIK_DIR, 'certs');\n\n// Legacy certs directory (for backwards compatibility)\nexport const CERTS_DIR = join(PANOPTICON_HOME, 'certs');\n\n// Config files\nexport const CONFIG_FILE = join(CONFIG_DIR, 'config.toml');\nexport const SETTINGS_FILE = join(CONFIG_DIR, 'settings.json');\n\n// AI tool directories\nexport const CLAUDE_DIR = join(homedir(), '.claude');\nexport const CODEX_DIR = join(homedir(), '.codex');\nexport const CURSOR_DIR = join(homedir(), '.cursor');\nexport const GEMINI_DIR = join(homedir(), '.gemini');\nexport const OPENCODE_DIR = join(homedir(), '.opencode');\n\n// Target sync locations\nexport const SYNC_TARGETS = {\n  claude: {\n    skills: join(CLAUDE_DIR, 'skills'),\n    commands: join(CLAUDE_DIR, 'commands'),\n    agents: join(CLAUDE_DIR, 'agents'),\n  },\n  codex: {\n    skills: join(CODEX_DIR, 'skills'),\n    commands: join(CODEX_DIR, 'commands'),\n    agents: join(CODEX_DIR, 'agents'),\n  },\n  cursor: {\n    skills: join(CURSOR_DIR, 'skills'),\n    commands: join(CURSOR_DIR, 'commands'),\n    agents: join(CURSOR_DIR, 'agents'),\n  },\n  gemini: {\n    skills: join(GEMINI_DIR, 'skills'),\n    commands: join(GEMINI_DIR, 'commands'),\n    agents: join(GEMINI_DIR, 'agents'),\n  },\n  opencode: {\n    skills: join(OPENCODE_DIR, 'skills'),\n    commands: join(OPENCODE_DIR, 'commands'),\n    agents: join(OPENCODE_DIR, 'agents'),\n  },\n} as const;\n\nexport type Runtime = keyof typeof SYNC_TARGETS;\n\n// Templates directory (in user's ~/.panopticon)\nexport const TEMPLATES_DIR = join(PANOPTICON_HOME, 'templates');\nexport const CLAUDE_MD_TEMPLATES = join(TEMPLATES_DIR, 'claude-md', 'sections');\n\n// Source templates directory (bundled with the package)\n// This is resolved at runtime from the package root\nimport { fileURLToPath } from 'url';\nimport { dirname } from 'path';\n\nconst currentFile = fileURLToPath(import.meta.url);\nconst currentDir = dirname(currentFile);\n\n// Handle both development (src/lib/) and production (dist/) modes\n// In dev: /path/to/panopticon/src/lib/paths.ts -> /path/to/panopticon\n// In prod: /path/to/panopticon/dist/lib/paths.js -> /path/to/panopticon\nlet packageRoot: string;\nif (currentDir.includes('/src/')) {\n  // Development mode - go up from src/lib to package root\n  packageRoot = dirname(dirname(currentDir));\n} else {\n  // Production mode - go up from dist (or dist/lib) to package root\n  packageRoot = currentDir.endsWith('/lib')\n    ? dirname(dirname(currentDir))\n    : dirname(currentDir);\n}\n\nexport const SOURCE_TEMPLATES_DIR = join(packageRoot, 'templates');\nexport const SOURCE_TRAEFIK_TEMPLATES = join(SOURCE_TEMPLATES_DIR, 'traefik');\nexport const SOURCE_SCRIPTS_DIR = join(packageRoot, 'scripts');\nexport const SOURCE_SKILLS_DIR = join(packageRoot, 'skills');\nexport const SOURCE_DEV_SKILLS_DIR = join(packageRoot, 'dev-skills');\n\n/**\n * Detect if running in development mode (from npm link or panopticon repo)\n *\n * Dev mode is detected if:\n * 1. Running from the panopticon source directory (npm link)\n * 2. The SOURCE_DEV_SKILLS_DIR exists (only present in repo, not in npm package)\n */\nexport function isDevMode(): boolean {\n  try {\n    // Check if dev-skills directory exists - this is only in the repo, not npm package\n    return existsSync(SOURCE_DEV_SKILLS_DIR);\n  } catch {\n    return false;\n  }\n}\n\n// All directories to create on init\nexport const INIT_DIRS = [\n  PANOPTICON_HOME,\n  SKILLS_DIR,\n  COMMANDS_DIR,\n  AGENTS_DIR,\n  BIN_DIR,\n  BACKUPS_DIR,\n  COSTS_DIR,\n  HEARTBEATS_DIR,\n  TEMPLATES_DIR,\n  CLAUDE_MD_TEMPLATES,\n  CERTS_DIR,\n  TRAEFIK_DIR,\n  TRAEFIK_DYNAMIC_DIR,\n  TRAEFIK_CERTS_DIR,\n];\n"],"mappings":";;;;;;AAAA,SAAS,eAAe;AACxB,SAAS,YAAY;AACrB,SAAS,kBAAkB;AA4E3B,SAAS,qBAAqB;AAC9B,SAAS,eAAe;AAvEjB,SAAS,oBAA4B;AAC1C,SAAO,QAAQ,IAAI,mBAAmB,KAAK,QAAQ,GAAG,aAAa;AACrE;AAqGO,SAAS,YAAqB;AACnC,MAAI;AAEF,WAAO,WAAW,qBAAqB;AAAA,EACzC,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAtHA,IAKa,iBAQA,YACA,YACA,cACA,YACA,SACA,aACA,WACA,gBAGA,aACA,qBACA,mBAGA,WAGA,aACA,eAGA,YACA,WACA,YACA,YACA,cAGA,cA+BA,eACA,qBAOP,aACA,YAKF,aAWS,sBACA,0BACA,oBACA,mBACA,uBAmBA;AAzHb;AAAA;AAAA;AAAA;AAKO,IAAM,kBAAkB,QAAQ,IAAI,mBAAmB,KAAK,QAAQ,GAAG,aAAa;AAQpF,IAAM,aAAa;AACnB,IAAM,aAAa,KAAK,iBAAiB,QAAQ;AACjD,IAAM,eAAe,KAAK,iBAAiB,UAAU;AACrD,IAAM,aAAa,KAAK,iBAAiB,QAAQ;AACjD,IAAM,UAAU,KAAK,iBAAiB,KAAK;AAC3C,IAAM,cAAc,KAAK,iBAAiB,SAAS;AACnD,IAAM,YAAY,KAAK,iBAAiB,OAAO;AAC/C,IAAM,iBAAiB,KAAK,iBAAiB,YAAY;AAGzD,IAAM,cAAc,KAAK,iBAAiB,SAAS;AACnD,IAAM,sBAAsB,KAAK,aAAa,SAAS;AACvD,IAAM,oBAAoB,KAAK,aAAa,OAAO;AAGnD,IAAM,YAAY,KAAK,iBAAiB,OAAO;AAG/C,IAAM,cAAc,KAAK,YAAY,aAAa;AAClD,IAAM,gBAAgB,KAAK,YAAY,eAAe;AAGtD,IAAM,aAAa,KAAK,QAAQ,GAAG,SAAS;AAC5C,IAAM,YAAY,KAAK,QAAQ,GAAG,QAAQ;AAC1C,IAAM,aAAa,KAAK,QAAQ,GAAG,SAAS;AAC5C,IAAM,aAAa,KAAK,QAAQ,GAAG,SAAS;AAC5C,IAAM,eAAe,KAAK,QAAQ,GAAG,WAAW;AAGhD,IAAM,eAAe;AAAA,MAC1B,QAAQ;AAAA,QACN,QAAQ,KAAK,YAAY,QAAQ;AAAA,QACjC,UAAU,KAAK,YAAY,UAAU;AAAA,QACrC,QAAQ,KAAK,YAAY,QAAQ;AAAA,MACnC;AAAA,MACA,OAAO;AAAA,QACL,QAAQ,KAAK,WAAW,QAAQ;AAAA,QAChC,UAAU,KAAK,WAAW,UAAU;AAAA,QACpC,QAAQ,KAAK,WAAW,QAAQ;AAAA,MAClC;AAAA,MACA,QAAQ;AAAA,QACN,QAAQ,KAAK,YAAY,QAAQ;AAAA,QACjC,UAAU,KAAK,YAAY,UAAU;AAAA,QACrC,QAAQ,KAAK,YAAY,QAAQ;AAAA,MACnC;AAAA,MACA,QAAQ;AAAA,QACN,QAAQ,KAAK,YAAY,QAAQ;AAAA,QACjC,UAAU,KAAK,YAAY,UAAU;AAAA,QACrC,QAAQ,KAAK,YAAY,QAAQ;AAAA,MACnC;AAAA,MACA,UAAU;AAAA,QACR,QAAQ,KAAK,cAAc,QAAQ;AAAA,QACnC,UAAU,KAAK,cAAc,UAAU;AAAA,QACvC,QAAQ,KAAK,cAAc,QAAQ;AAAA,MACrC;AAAA,IACF;AAKO,IAAM,gBAAgB,KAAK,iBAAiB,WAAW;AACvD,IAAM,sBAAsB,KAAK,eAAe,aAAa,UAAU;AAO9E,IAAM,cAAc,cAAc,YAAY,GAAG;AACjD,IAAM,aAAa,QAAQ,WAAW;AAMtC,QAAI,WAAW,SAAS,OAAO,GAAG;AAEhC,oBAAc,QAAQ,QAAQ,UAAU,CAAC;AAAA,IAC3C,OAAO;AAEL,oBAAc,WAAW,SAAS,MAAM,IACpC,QAAQ,QAAQ,UAAU,CAAC,IAC3B,QAAQ,UAAU;AAAA,IACxB;AAEO,IAAM,uBAAuB,KAAK,aAAa,WAAW;AAC1D,IAAM,2BAA2B,KAAK,sBAAsB,SAAS;AACrE,IAAM,qBAAqB,KAAK,aAAa,SAAS;AACtD,IAAM,oBAAoB,KAAK,aAAa,QAAQ;AACpD,IAAM,wBAAwB,KAAK,aAAa,YAAY;AAmB5D,IAAM,YAAY;AAAA,MACvB;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,MACA;AAAA,IACF;AAAA;AAAA;","names":[]}