@meltstudio/meltctl 4.179.2 → 4.179.4

package/dist/index.js

@@ -14,7 +14,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/utils/version.ts"() {
     "use strict";
-    CLI_VERSION = "4.179.2";
+    CLI_VERSION = "4.179.4";
   }
 });
 
@@ -1680,7 +1680,10 @@ var ISSUE_RULES = [
   {
     id: "board.pm-silent-critical",
     dimension: "board",
-    severity: "critical",
+    // Intentionally medium, not critical: PM silence is process hygiene, not an
+    // emergency, and red is reserved to avoid alert fatigue. Can be tightened
+    // again as adoption matures. (id keeps the -critical suffix for continuity.)
+    severity: "medium",
     label: "PM silent in active cycle",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
@@ -1746,7 +1749,9 @@ var ISSUE_RULES = [
   {
     id: "plans.stuck",
     dimension: "plans",
-    severity: "high",
+    // Medium, not high: a stuck plan is a tooling/terminal-scorer failure, not a
+    // project emergency. Red reserved to avoid fatigue; tighten later if needed.
+    severity: "medium",
     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",
@@ -1784,7 +1789,11 @@ var ISSUE_RULES = [
   {
     id: "findings.high",
     dimension: "findings",
-    severity: "high",
+    // Medium, not high: a high *code* finding is dev-facing work to schedule,
+    // not a PM red alarm — only critical findings turn the project band red.
+    // The finding keeps its own 'high' severity in the findings list; this only
+    // governs the project-health band. Tighten later as adoption matures.
+    severity: "medium",
     label: "High audit finding",
     category: "audits",
     howToFix: "Open the audit detail page and schedule the high-severity finding into the sprint",
@@ -4745,7 +4754,10 @@ var ISSUE_RULES2 = [
   {
     id: "board.pm-silent-critical",
     dimension: "board",
-    severity: "critical",
+    // Intentionally medium, not critical: PM silence is process hygiene, not an
+    // emergency, and red is reserved to avoid alert fatigue. Can be tightened
+    // again as adoption matures. (id keeps the -critical suffix for continuity.)
+    severity: "medium",
     label: "PM silent in active cycle",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
@@ -4811,7 +4823,9 @@ var ISSUE_RULES2 = [
   {
     id: "plans.stuck",
     dimension: "plans",
-    severity: "high",
+    // Medium, not high: a stuck plan is a tooling/terminal-scorer failure, not a
+    // project emergency. Red reserved to avoid fatigue; tighten later if needed.
+    severity: "medium",
     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",
@@ -4849,7 +4863,11 @@ var ISSUE_RULES2 = [
   {
     id: "findings.high",
     dimension: "findings",
-    severity: "high",
+    // Medium, not high: a high *code* finding is dev-facing work to schedule,
+    // not a PM red alarm — only critical findings turn the project band red.
+    // The finding keeps its own 'high' severity in the findings list; this only
+    // governs the project-health band. Tighten later as adoption matures.
+    severity: "medium",
     label: "High audit finding",
     category: "audits",
     howToFix: "Open the audit detail page and schedule the high-severity finding into the sprint",
@@ -5534,7 +5552,7 @@ function registerProjectHealthTools(server, getClient2) {
     "get_project_health",
     {
       title: "Get project health",
-      description: "Composite read-only snapshot of one project's health: 0-100 score, audit-freshness numbers, findings (critical/high/missing/warning counts), board-audit aggregate + age, ticket counts (open/started/overdue), standup compliance (last 14 days), plan recency, last CLI activity, and the project's RSK risks (open/mitigated counts, red-zone count, top 3 open risks with impact \xD7 probability scores AND the PM's latest weekly status comment on each one). Risks + comments come from a weekly mirror of the RSK Linear board, refreshed every Tuesday evening right after the team's risk-review meeting \u2014 so 'latestComment' is normally the just-logged update for the week. Use this for 'how's project X doing?' questions \u2014 it pulls in one round trip what would otherwise be 8+ separate tool calls. Score formula matches the dashboard's project cards.",
+      description: "Composite read-only snapshot of one project's health: 0-100 score; `issues` \u2014 the full list of open health issues (each with label, dimension, severity, and a one-line howToFix), which are the EXACT items shown on the project's dashboard health card (e.g. 'PM silent in active cycle', 'Roadmap status differs from Linear', 'No roadmap'); audit-freshness numbers, findings (critical/high/missing/warning counts), board-audit aggregate + age, ticket counts (open/started/overdue), standup compliance (last 14 days), plan recency, last CLI activity, and the project's RSK risks (open/mitigated counts, red-zone count, top 3 open risks with impact \xD7 probability scores AND the PM's latest weekly status comment on each one). Risks + comments come from a weekly mirror of the RSK Linear board, refreshed every Tuesday evening right after the team's risk-review meeting \u2014 so 'latestComment' is normally the just-logged update for the week. Use this for 'how's project X doing?' / 'what needs attention on X?' questions \u2014 prefer surfacing the `issues` list (worst severity first) over just the score. Pulls in one round trip what would otherwise be 8+ separate tool calls; score + issues match the dashboard's project cards.",
       inputSchema: {
         projectId: z8.number().int().positive().describe(
           "Strapi project id from list_projects. The project must have at least one linked repository \u2014 otherwise the score is undefined and the tool returns 422."

package/package.json

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