@meltstudio/meltctl 4.149.1 → 4.150.0

package/dist/index.js

@@ -14,7 +14,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/utils/version.ts"() {
     "use strict";
-    CLI_VERSION = "4.149.1";
+    CLI_VERSION = "4.150.0";
   }
 });
 
@@ -1364,97 +1364,210 @@ var extractionResultSchema = z.object({
 // ../sdk/dist/utils/health-status.js
 var ISSUE_RULES = [
   // Delivery — Roadmap
-  { id: "roadmap.none", dimension: "roadmap", severity: "high", label: "No roadmap" },
+  {
+    id: "roadmap.none",
+    dimension: "roadmap",
+    severity: "high",
+    label: "No roadmap",
+    category: "gaps",
+    howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
+    scope: "project"
+  },
   {
     id: "roadmap.no-active-phase",
     dimension: "roadmap",
     severity: "medium",
-    label: "Features but no active phase"
+    label: "Features but no active phase",
+    category: "gaps",
+    howToFix: "Open the Roadmap tab and mark the phase the team is currently working on as active",
+    scope: "project"
   },
   {
     id: "roadmap.empty-phase",
     dimension: "roadmap",
     severity: "medium",
-    label: "Active phase is empty"
+    label: "Active phase is empty",
+    category: "gaps",
+    howToFix: "Open the Roadmap tab and attach the phase's planned features, or close the phase if it's done",
+    scope: "project"
   },
   // Delivery — Board
-  { id: "board.no-mapping", dimension: "board", severity: "high", label: "No board connected" },
-  { id: "board.empty", dimension: "board", severity: "medium", label: "Board has no open tickets" },
-  { id: "board.health-low", dimension: "board", severity: "high", label: "Board health below 40%" },
+  {
+    id: "board.no-mapping",
+    dimension: "board",
+    severity: "high",
+    label: "No board connected",
+    category: "gaps",
+    howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
+    scope: "project"
+  },
+  {
+    id: "board.empty",
+    dimension: "board",
+    severity: "medium",
+    label: "Board has no open tickets",
+    category: "sprint",
+    howToFix: "Confirm the team is creating stories on the board, or that the mapping is correct",
+    scope: "project"
+  },
+  {
+    id: "board.health-low",
+    dimension: "board",
+    severity: "high",
+    label: "Board health below 40%",
+    category: "sprint",
+    howToFix: "Open the project's Linear board and triage the failing audit checks",
+    scope: "project"
+  },
   {
     id: "board.health-mid",
     dimension: "board",
     severity: "medium",
-    label: "Board health 40\u201369%"
+    label: "Board health 40\u201369%",
+    category: "sprint",
+    howToFix: "Open the project's Linear board and triage the failing audit checks",
+    scope: "project"
+  },
+  {
+    id: "board.audit-stale",
+    dimension: "board",
+    severity: "medium",
+    label: "Board audit stale",
+    category: "sprint",
+    howToFix: "Open the project page and click 'Run board audit' to refresh the score",
+    scope: "project"
   },
-  { id: "board.audit-stale", dimension: "board", severity: "medium", label: "Board audit stale" },
   // Delivery — Risks
   {
     id: "risks.stale-red-zone",
     dimension: "risks",
     severity: "critical",
-    label: "Red-zone risk with no recent comment"
+    label: "Red-zone risk with no recent comment",
+    category: "risks",
+    howToFix: "Open the risk in Linear, add a fresh status comment, or close it if resolved",
+    scope: "project"
   },
   {
     id: "risks.active-red-zone",
     dimension: "risks",
     severity: "medium",
-    label: "Open red-zone risk"
+    label: "Open red-zone risk",
+    category: "risks",
+    howToFix: "Review the open red-zone risk at this Tuesday's risk review and confirm an owner",
+    scope: "project"
   },
   // Delivery — Activity
   {
-    id: "activity.dead",
+    id: "activity.dormant",
     dimension: "activity",
-    severity: "high",
-    label: "No activity in 21+ days"
+    severity: "medium",
+    label: "No activity in 21+ days",
+    category: "gaps",
+    howToFix: "No meltctl activity in N days \u2014 confirm the project is still active, or mark it on-hold",
+    scope: "project"
   },
+  // Delivery — Plans
   {
-    id: "activity.quiet",
-    dimension: "activity",
+    id: "plans.stale",
+    dimension: "plans",
     severity: "medium",
-    label: "No activity in 10\u201320 days"
+    label: "No recent plan",
+    category: "plans",
+    howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
+    scope: "project"
+  },
+  {
+    id: "plans.unscored",
+    dimension: "plans",
+    severity: "low",
+    label: "Plans not yet scored",
+    category: "plans",
+    howToFix: "Open the plan and click 'Score plan' to run the rubric",
+    scope: "project"
+  },
+  {
+    id: "plans.stuck",
+    dimension: "plans",
+    severity: "high",
+    label: "Plan can't be scored",
+    category: "plans",
+    howToFix: "Re-run `meltctl plan submit` with a valid ticket, or close the plan if it's no longer relevant",
+    scope: "project"
   },
-  // Delivery — Plans
-  { id: "plans.stale", dimension: "plans", severity: "medium", label: "No recent plan" },
   // Delivery — Standups
   {
     id: "standups.low",
     dimension: "standups",
     severity: "medium",
-    label: "Standup submission below 50%"
+    label: "Standup submission below 50%",
+    category: "standup",
+    howToFix: "Remind the team that standup is set for 9am Colombia; follow up with non-submitters",
+    scope: "project"
   },
   // Code — Findings
   {
     id: "findings.critical",
     dimension: "findings",
     severity: "critical",
-    label: "Critical audit finding"
+    label: "Critical audit finding",
+    category: "audits",
+    howToFix: "Open the audit detail page and address the critical finding before anything else",
+    scope: "project"
+  },
+  {
+    id: "findings.high",
+    dimension: "findings",
+    severity: "high",
+    label: "High audit finding",
+    category: "audits",
+    howToFix: "Open the audit detail page and schedule the high-severity finding into the sprint",
+    scope: "project"
   },
-  { id: "findings.high", dimension: "findings", severity: "high", label: "High audit finding" },
   {
     id: "findings.medium",
     dimension: "findings",
     severity: "medium",
-    label: "Open audit warnings"
+    label: "Open audit warnings",
+    category: "audits",
+    howToFix: "Open the audit detail page and work through the open warnings/missing checks",
+    scope: "project"
   },
   // Code — Audit coverage
   {
     id: "audit.never",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Never audited"
+    label: "Never audited",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on the repo to create the baseline",
+    scope: "project"
   },
   {
     id: "audit.stale",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Audit over 90 days old"
+    label: "Audit over 90 days old",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on the repo to refresh the baseline",
+    scope: "project"
   },
   {
     id: "audit.partial",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Some repos never audited"
+    label: "Some repos never audited",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on each unaudited repo to create its baseline",
+    scope: "project"
+  },
+  {
+    id: "audit.unprocessed",
+    dimension: "audit-coverage",
+    severity: "low",
+    label: "Audit not processed for findings",
+    category: "audits",
+    howToFix: "Open each audit and click 'Extract findings' to populate the findings table",
+    scope: "project"
   }
 ];
 var RULE_BY_ID = new Map(ISSUE_RULES.map((r) => [r.id, r]));
@@ -1500,20 +1613,17 @@ var SKILL_FRONTMATTER = {
   setup: `---
 user-invocable: true
 description: >-
-  Analyze the project and customize AGENTS.md for this codebase.
-  Use when setting up a new project, after running meltctl init,
-  or when AGENTS.md has placeholder markers. Detects tech stack,
-  fills in project-specific sections, and merges existing standards.
+  Analyze the project and customize AGENTS.md for this codebase. Use when
+  setting up a new project, after meltctl init, or when AGENTS.md has
+  placeholder markers.
 ---
 
 `,
   plan: `---
 user-invocable: true
 description: >-
-  Design an implementation approach before writing code. Use when
-  starting a feature, tackling a complex task, or when the developer
-  says "plan this" or "how should we approach this". Gathers requirements,
-  explores codebase, and presents a step-by-step plan for approval.
+  Design an implementation approach before writing code. Use when starting
+  a feature, tackling a complex task, or the developer says "plan this".
 ---
 
 `,
@@ -1521,40 +1631,33 @@ description: >-
 user-invocable: true
 description: >-
   Review code changes against project standards and address PR feedback.
-  Use when the developer asks to review changes, check code quality,
-  or respond to PR reviewer comments. Categorizes findings as must-fix,
-  should-fix, or suggestions.
+  Use when the developer asks to review changes or respond to PR reviewer
+  comments.
 ---
 
 `,
   pr: `---
 user-invocable: true
 description: >-
-  Create a well-structured pull request from current changes. Use when
-  the developer is ready to submit work, says "create a PR", or "open
-  a pull request". Analyzes changes, runs pre-flight checks, drafts
-  description, and creates the PR via gh CLI.
+  Create a well-structured pull request from current changes. Use when the
+  developer says "create a PR" or is ready to submit work.
 ---
 
 `,
   debug: `---
 user-invocable: true
 description: >-
-  Systematically investigate and fix bugs. Use when the developer
-  reports a bug, encounters an error, or says "debug this" or "why
-  is this failing". Reproduces the issue, isolates root cause, writes
-  regression test, and implements minimal fix.
+  Systematically investigate and fix bugs. Use when the developer reports
+  a bug, hits an error, or says "debug this".
 ---
 
 `,
   audit: `---
 user-invocable: true
 description: >-
-  Run a comprehensive project compliance audit against team standards.
-  Use when the developer wants to assess project health, check compliance,
-  or says "audit this project". Checks 15 categories including documentation,
-  testing, CI/CD, security, and AI tool setup. Produces a structured
-  report with scores and actionable fixes.
+  Run a comprehensive project compliance audit against team standards. Use
+  when the developer wants to assess project health or says "audit this
+  project".
 ---
 
 `,
@@ -1562,31 +1665,25 @@ description: >-
 user-invocable: true
 description: >-
   Review the project's UI against usability heuristics using Chrome DevTools
-  MCP. Use when the developer wants to check UX quality, says "review the UI",
-  or "UX audit". In full audit mode, crawls the entire app. During an active
-  plan, scopes to the current feature and appends results to the plan file.
+  MCP. Use when the developer says "review the UI" or "UX audit".
 ---
 
 `,
   "security-audit": `---
 user-invocable: true
 description: >-
-  Run a comprehensive security posture audit across the entire platform.
-  Use when the developer wants to assess security, says "security audit",
-  or "check our security posture". Covers infrastructure, encryption, auth,
-  application security, data protection, CI/CD, and compliance readiness.
-  Investigates all platform repositories for a holistic view.
+  Run a comprehensive security posture audit across all platform
+  repositories. Use when the developer says "security audit" or wants to
+  assess security posture.
 ---
 
 `,
   validate: `---
 user-invocable: true
 description: >-
-  Run the validation plan from the plan document after implementation.
-  Use when the developer says "validate this", "test the feature", or
-  after finishing implementation. Validates end-to-end using browser,
-  API, or CLI testing, suggests test coverage improvements, then prompts
-  the developer for mandatory manual sign-off.
+  Run the validation plan from the plan document after implementation. Use
+  when the developer says "validate this" or "test the feature", or after
+  finishing implementation.
 ---
 
 `,
@@ -1594,9 +1691,7 @@ description: >-
 user-invocable: true
 description: >-
   Update Melt skills and standards to the latest version. Use when the
-  developer wants the latest skill templates, says "update melt", or
-  after a new meltctl version is released. Fetches latest templates,
-  preserves project customizations in AGENTS.md, and merges changes.
+  developer says "update melt" or wants the latest skill templates.
 ---
 
 `,
@@ -1604,9 +1699,8 @@ description: >-
 user-invocable: true
 description: >-
   Answer questions about the AI-First Development Playbook and team
-  workflow. Use when the developer asks about the development process,
-  what step they're on, how validation works, or any workflow question.
-  This is a reference skill \u2014 it explains the process, not executes it.
+  workflow. Use when the developer asks about the development process or
+  how a step works. Reference skill \u2014 explains, doesn't execute.
 ---
 
 `,
@@ -1614,9 +1708,8 @@ description: >-
 user-invocable: true
 description: >-
   Connect and verify required integrations (ticket tracker, browser
-  testing). Use after melt-setup, when tools aren't working, or when
-  a skill reports missing MCP connections. Guides setup, verifies
-  each tool works, and updates AGENTS.md connection status.
+  testing). Use after melt-setup, when tools aren't working, or when a
+  skill reports missing MCP connections.
 ---
 
 `
@@ -4055,97 +4148,210 @@ var extractionResultSchema2 = z2.object({
 });
 var ISSUE_RULES2 = [
   // Delivery — Roadmap
-  { id: "roadmap.none", dimension: "roadmap", severity: "high", label: "No roadmap" },
+  {
+    id: "roadmap.none",
+    dimension: "roadmap",
+    severity: "high",
+    label: "No roadmap",
+    category: "gaps",
+    howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
+    scope: "project"
+  },
   {
     id: "roadmap.no-active-phase",
     dimension: "roadmap",
     severity: "medium",
-    label: "Features but no active phase"
+    label: "Features but no active phase",
+    category: "gaps",
+    howToFix: "Open the Roadmap tab and mark the phase the team is currently working on as active",
+    scope: "project"
   },
   {
     id: "roadmap.empty-phase",
     dimension: "roadmap",
     severity: "medium",
-    label: "Active phase is empty"
+    label: "Active phase is empty",
+    category: "gaps",
+    howToFix: "Open the Roadmap tab and attach the phase's planned features, or close the phase if it's done",
+    scope: "project"
   },
   // Delivery — Board
-  { id: "board.no-mapping", dimension: "board", severity: "high", label: "No board connected" },
-  { id: "board.empty", dimension: "board", severity: "medium", label: "Board has no open tickets" },
-  { id: "board.health-low", dimension: "board", severity: "high", label: "Board health below 40%" },
+  {
+    id: "board.no-mapping",
+    dimension: "board",
+    severity: "high",
+    label: "No board connected",
+    category: "gaps",
+    howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
+    scope: "project"
+  },
+  {
+    id: "board.empty",
+    dimension: "board",
+    severity: "medium",
+    label: "Board has no open tickets",
+    category: "sprint",
+    howToFix: "Confirm the team is creating stories on the board, or that the mapping is correct",
+    scope: "project"
+  },
+  {
+    id: "board.health-low",
+    dimension: "board",
+    severity: "high",
+    label: "Board health below 40%",
+    category: "sprint",
+    howToFix: "Open the project's Linear board and triage the failing audit checks",
+    scope: "project"
+  },
   {
     id: "board.health-mid",
     dimension: "board",
     severity: "medium",
-    label: "Board health 40\u201369%"
+    label: "Board health 40\u201369%",
+    category: "sprint",
+    howToFix: "Open the project's Linear board and triage the failing audit checks",
+    scope: "project"
+  },
+  {
+    id: "board.audit-stale",
+    dimension: "board",
+    severity: "medium",
+    label: "Board audit stale",
+    category: "sprint",
+    howToFix: "Open the project page and click 'Run board audit' to refresh the score",
+    scope: "project"
   },
-  { id: "board.audit-stale", dimension: "board", severity: "medium", label: "Board audit stale" },
   // Delivery — Risks
   {
     id: "risks.stale-red-zone",
     dimension: "risks",
     severity: "critical",
-    label: "Red-zone risk with no recent comment"
+    label: "Red-zone risk with no recent comment",
+    category: "risks",
+    howToFix: "Open the risk in Linear, add a fresh status comment, or close it if resolved",
+    scope: "project"
   },
   {
     id: "risks.active-red-zone",
     dimension: "risks",
     severity: "medium",
-    label: "Open red-zone risk"
+    label: "Open red-zone risk",
+    category: "risks",
+    howToFix: "Review the open red-zone risk at this Tuesday's risk review and confirm an owner",
+    scope: "project"
   },
   // Delivery — Activity
   {
-    id: "activity.dead",
+    id: "activity.dormant",
     dimension: "activity",
-    severity: "high",
-    label: "No activity in 21+ days"
+    severity: "medium",
+    label: "No activity in 21+ days",
+    category: "gaps",
+    howToFix: "No meltctl activity in N days \u2014 confirm the project is still active, or mark it on-hold",
+    scope: "project"
   },
+  // Delivery — Plans
   {
-    id: "activity.quiet",
-    dimension: "activity",
+    id: "plans.stale",
+    dimension: "plans",
     severity: "medium",
-    label: "No activity in 10\u201320 days"
+    label: "No recent plan",
+    category: "plans",
+    howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
+    scope: "project"
+  },
+  {
+    id: "plans.unscored",
+    dimension: "plans",
+    severity: "low",
+    label: "Plans not yet scored",
+    category: "plans",
+    howToFix: "Open the plan and click 'Score plan' to run the rubric",
+    scope: "project"
+  },
+  {
+    id: "plans.stuck",
+    dimension: "plans",
+    severity: "high",
+    label: "Plan can't be scored",
+    category: "plans",
+    howToFix: "Re-run `meltctl plan submit` with a valid ticket, or close the plan if it's no longer relevant",
+    scope: "project"
   },
-  // Delivery — Plans
-  { id: "plans.stale", dimension: "plans", severity: "medium", label: "No recent plan" },
   // Delivery — Standups
   {
     id: "standups.low",
     dimension: "standups",
     severity: "medium",
-    label: "Standup submission below 50%"
+    label: "Standup submission below 50%",
+    category: "standup",
+    howToFix: "Remind the team that standup is set for 9am Colombia; follow up with non-submitters",
+    scope: "project"
   },
   // Code — Findings
   {
     id: "findings.critical",
     dimension: "findings",
     severity: "critical",
-    label: "Critical audit finding"
+    label: "Critical audit finding",
+    category: "audits",
+    howToFix: "Open the audit detail page and address the critical finding before anything else",
+    scope: "project"
+  },
+  {
+    id: "findings.high",
+    dimension: "findings",
+    severity: "high",
+    label: "High audit finding",
+    category: "audits",
+    howToFix: "Open the audit detail page and schedule the high-severity finding into the sprint",
+    scope: "project"
   },
-  { id: "findings.high", dimension: "findings", severity: "high", label: "High audit finding" },
   {
     id: "findings.medium",
     dimension: "findings",
     severity: "medium",
-    label: "Open audit warnings"
+    label: "Open audit warnings",
+    category: "audits",
+    howToFix: "Open the audit detail page and work through the open warnings/missing checks",
+    scope: "project"
   },
   // Code — Audit coverage
   {
     id: "audit.never",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Never audited"
+    label: "Never audited",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on the repo to create the baseline",
+    scope: "project"
   },
   {
     id: "audit.stale",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Audit over 90 days old"
+    label: "Audit over 90 days old",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on the repo to refresh the baseline",
+    scope: "project"
   },
   {
     id: "audit.partial",
     dimension: "audit-coverage",
     severity: "medium",
-    label: "Some repos never audited"
+    label: "Some repos never audited",
+    category: "audits",
+    howToFix: "Run `/melt-audit` on each unaudited repo to create its baseline",
+    scope: "project"
+  },
+  {
+    id: "audit.unprocessed",
+    dimension: "audit-coverage",
+    severity: "low",
+    label: "Audit not processed for findings",
+    category: "audits",
+    howToFix: "Open each audit and click 'Extract findings' to populate the findings table",
+    scope: "project"
   }
 ];
 var RULE_BY_ID2 = new Map(ISSUE_RULES2.map((r) => [r.id, r]));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meltstudio/meltctl",
-  "version": "4.149.1",
+  "version": "4.150.0",
   "description": "AI-first development tools for teams - set up AGENTS.md, Claude Code, Cursor, and OpenCode standards",
   "main": "dist/index.js",
   "type": "module",