@meltstudio/meltctl 5.13.0 → 5.15.0

package/dist/index.js

@@ -7450,7 +7450,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/utils/version.ts"() {
     "use strict";
-    CLI_VERSION = "5.13.0";
+    CLI_VERSION = "5.15.0";
   }
 });
 
@@ -27939,9 +27939,9 @@ function createProfileAuditsResource(config2) {
 function createSupportEffortResource(config2) {
   return {
     /**
-     * Get the by-project + by-architect rollups, the week/month trend, and the
-     * actionable missing-time worklist. `period` selects the trend granularity
-     * (default 'week').
+     * Get the by-project + by-architect rollups, the project × month matrix
+     * (last 6 months), the week/month trend, and the actionable missing-time
+     * worklist. `period` selects the trend granularity (default 'week').
      */
     async get(opts = {}) {
       const params = new URLSearchParams();
@@ -41889,9 +41889,9 @@ var ISSUE_RULES = [
   {
     id: "roadmap.none",
     dimension: "roadmap",
-    // Setup/hygiene gap — Medium, not High (#446 follow-up: process-hygiene
-    // rules softened so the portfolio's genuinely-critical signals stand out).
-    severity: "medium",
+    // Setup/hygiene gap — demoted Medium → Low in the #580 lenient phase
+    // (setup nudges shouldn't band a project; re-promote when ratcheting).
+    severity: "low",
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
@@ -41974,7 +41974,8 @@ var ISSUE_RULES = [
   {
     id: "board.no-mapping",
     dimension: "board",
-    severity: "medium",
+    // Setup nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
@@ -41984,7 +41985,8 @@ var ISSUE_RULES = [
   {
     id: "tracker.no-oauth",
     dimension: "board",
-    severity: "medium",
+    // Setup nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Tracker needs OAuth connect",
     category: "gaps",
     howToFix: "Open Project Settings \u2192 Tracker connections and click Connect for the missing provider; that switches the project off Melt's shared key onto its own OAuth grant",
@@ -41994,7 +41996,9 @@ var ISSUE_RULES = [
   {
     id: "board.empty",
     dimension: "board",
-    severity: "medium",
+    // Hygiene check — demoted Medium → Low in the #580 lenient phase (fires
+    // in normal operation, e.g. between cycles).
+    severity: "low",
     label: "Board has no open tickets",
     category: "sprint",
     howToFix: "Confirm the team is creating stories on the board, or that the mapping is correct",
@@ -42003,8 +42007,10 @@ var ISSUE_RULES = [
   {
     id: "board.health-low",
     dimension: "board",
+    // The genuinely-bad tier. Threshold moved <40% → <55% in the #580 lenient
+    // phase so the medium tier only covers boards that are truly failing.
     severity: "medium",
-    label: "Board health below 40%",
+    label: "Board health below 55%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
     scope: "project"
@@ -42012,8 +42018,10 @@ var ISSUE_RULES = [
   {
     id: "board.health-mid",
     dimension: "board",
-    severity: "medium",
-    label: "Board health 40\u201369%",
+    // The could-be-better tier (55–69%) — demoted Medium → Low in the #580
+    // lenient phase; a passing-but-imperfect board is backlog, not an alarm.
+    severity: "low",
+    label: "Board health 55\u201369%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
     scope: "project"
@@ -42021,7 +42029,8 @@ var ISSUE_RULES = [
   {
     id: "board.audit-stale",
     dimension: "board",
-    severity: "medium",
+    // Staleness nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Board audit stale",
     category: "sprint",
     howToFix: "Open the project page and click 'Run board audit' to refresh the score",
@@ -42102,7 +42111,8 @@ var ISSUE_RULES = [
   {
     id: "activity.dormant",
     dimension: "activity",
-    severity: "medium",
+    // Staleness signal — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     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",
@@ -42113,7 +42123,8 @@ var ISSUE_RULES = [
   {
     id: "plans.stale",
     dimension: "plans",
-    severity: "medium",
+    // Adoption nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "No recent plan",
     category: "plans",
     howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
@@ -42189,8 +42200,21 @@ var ISSUE_RULES = [
   {
     id: "findings.medium",
     dimension: "findings",
+    // Fires only when ≥5 medium findings are open (#580) — a real backlog
+    // worth banding, not one warning. Smaller counts fall to findings.minor.
     severity: "medium",
-    label: "Open audit warnings",
+    label: "Open medium findings",
+    category: "audits",
+    howToFix: "Open the audit detail page and work through the open warnings/missing checks",
+    scope: "project"
+  },
+  {
+    id: "findings.minor",
+    dimension: "findings",
+    // The lenient tier under findings.medium (#580): 1–4 open mediums, or
+    // only lows, read as backlog — visible but never banding.
+    severity: "low",
+    label: "Minor findings",
     category: "audits",
     howToFix: "Open the audit detail page and work through the open warnings/missing checks",
     scope: "project"
@@ -42199,7 +42223,8 @@ var ISSUE_RULES = [
   {
     id: "audit.never",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Coverage nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Never audited",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on the repo to create the baseline",
@@ -42209,7 +42234,8 @@ var ISSUE_RULES = [
   {
     id: "audit.stale",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Staleness nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Audit over 90 days old",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on the repo to refresh the baseline",
@@ -42231,7 +42257,8 @@ var ISSUE_RULES = [
   {
     id: "audit.partial",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Coverage nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Some repos never audited",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on each unaudited repo to create its baseline",
@@ -54540,9 +54567,9 @@ function createProfileAuditsResource2(config2) {
 function createSupportEffortResource2(config2) {
   return {
     /**
-     * Get the by-project + by-architect rollups, the week/month trend, and the
-     * actionable missing-time worklist. `period` selects the trend granularity
-     * (default 'week').
+     * Get the by-project + by-architect rollups, the project × month matrix
+     * (last 6 months), the week/month trend, and the actionable missing-time
+     * worklist. `period` selects the trend granularity (default 'week').
      */
     async get(opts = {}) {
       const params = new URLSearchParams();
@@ -54716,9 +54743,9 @@ var ISSUE_RULES2 = [
   {
     id: "roadmap.none",
     dimension: "roadmap",
-    // Setup/hygiene gap — Medium, not High (#446 follow-up: process-hygiene
-    // rules softened so the portfolio's genuinely-critical signals stand out).
-    severity: "medium",
+    // Setup/hygiene gap — demoted Medium → Low in the #580 lenient phase
+    // (setup nudges shouldn't band a project; re-promote when ratcheting).
+    severity: "low",
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
@@ -54801,7 +54828,8 @@ var ISSUE_RULES2 = [
   {
     id: "board.no-mapping",
     dimension: "board",
-    severity: "medium",
+    // Setup nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
@@ -54811,7 +54839,8 @@ var ISSUE_RULES2 = [
   {
     id: "tracker.no-oauth",
     dimension: "board",
-    severity: "medium",
+    // Setup nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Tracker needs OAuth connect",
     category: "gaps",
     howToFix: "Open Project Settings \u2192 Tracker connections and click Connect for the missing provider; that switches the project off Melt's shared key onto its own OAuth grant",
@@ -54821,7 +54850,9 @@ var ISSUE_RULES2 = [
   {
     id: "board.empty",
     dimension: "board",
-    severity: "medium",
+    // Hygiene check — demoted Medium → Low in the #580 lenient phase (fires
+    // in normal operation, e.g. between cycles).
+    severity: "low",
     label: "Board has no open tickets",
     category: "sprint",
     howToFix: "Confirm the team is creating stories on the board, or that the mapping is correct",
@@ -54830,8 +54861,10 @@ var ISSUE_RULES2 = [
   {
     id: "board.health-low",
     dimension: "board",
+    // The genuinely-bad tier. Threshold moved <40% → <55% in the #580 lenient
+    // phase so the medium tier only covers boards that are truly failing.
     severity: "medium",
-    label: "Board health below 40%",
+    label: "Board health below 55%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
     scope: "project"
@@ -54839,8 +54872,10 @@ var ISSUE_RULES2 = [
   {
     id: "board.health-mid",
     dimension: "board",
-    severity: "medium",
-    label: "Board health 40\u201369%",
+    // The could-be-better tier (55–69%) — demoted Medium → Low in the #580
+    // lenient phase; a passing-but-imperfect board is backlog, not an alarm.
+    severity: "low",
+    label: "Board health 55\u201369%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
     scope: "project"
@@ -54848,7 +54883,8 @@ var ISSUE_RULES2 = [
   {
     id: "board.audit-stale",
     dimension: "board",
-    severity: "medium",
+    // Staleness nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Board audit stale",
     category: "sprint",
     howToFix: "Open the project page and click 'Run board audit' to refresh the score",
@@ -54929,7 +54965,8 @@ var ISSUE_RULES2 = [
   {
     id: "activity.dormant",
     dimension: "activity",
-    severity: "medium",
+    // Staleness signal — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     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",
@@ -54940,7 +54977,8 @@ var ISSUE_RULES2 = [
   {
     id: "plans.stale",
     dimension: "plans",
-    severity: "medium",
+    // Adoption nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "No recent plan",
     category: "plans",
     howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
@@ -55016,8 +55054,21 @@ var ISSUE_RULES2 = [
   {
     id: "findings.medium",
     dimension: "findings",
+    // Fires only when ≥5 medium findings are open (#580) — a real backlog
+    // worth banding, not one warning. Smaller counts fall to findings.minor.
     severity: "medium",
-    label: "Open audit warnings",
+    label: "Open medium findings",
+    category: "audits",
+    howToFix: "Open the audit detail page and work through the open warnings/missing checks",
+    scope: "project"
+  },
+  {
+    id: "findings.minor",
+    dimension: "findings",
+    // The lenient tier under findings.medium (#580): 1–4 open mediums, or
+    // only lows, read as backlog — visible but never banding.
+    severity: "low",
+    label: "Minor findings",
     category: "audits",
     howToFix: "Open the audit detail page and work through the open warnings/missing checks",
     scope: "project"
@@ -55026,7 +55077,8 @@ var ISSUE_RULES2 = [
   {
     id: "audit.never",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Coverage nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Never audited",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on the repo to create the baseline",
@@ -55036,7 +55088,8 @@ var ISSUE_RULES2 = [
   {
     id: "audit.stale",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Staleness nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Audit over 90 days old",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on the repo to refresh the baseline",
@@ -55058,7 +55111,8 @@ var ISSUE_RULES2 = [
   {
     id: "audit.partial",
     dimension: "audit-coverage",
-    severity: "medium",
+    // Coverage nudge — demoted Medium → Low in the #580 lenient phase.
+    severity: "low",
     label: "Some repos never audited",
     category: "audits",
     howToFix: "Run `/melt-dev-tech-audit` on each unaudited repo to create its baseline",
@@ -55907,6 +55961,7 @@ async function getSupportEffort(client, input) {
       asOf: data.asOf,
       byProject: data.byProject,
       byArchitect: data.byArchitect,
+      byProjectMonthly: data.byProjectMonthly,
       trend: data.trend,
       // Surface the count prominently; the full actionable list is available via
       // the read API / dashboard page (Slice 2) rather than flooding the tool.
@@ -55919,7 +55974,7 @@ function registerSupportEffortTools(server, getClient2) {
     "get_support_effort",
     {
       title: "Get tech-support effort",
-      description: "Tech-support / DevOps effort rollup for the 'Tech Support Ops' Linear team (key DEV). Returns logged hours (parsed from each ticket's self-reported 'Time Spent' label \u2014 the architect's active effort, NOT cycle time) and ticket counts rolled up two ways: `byProject` (which client/product the support load lands on) and `byArchitect` (who is carrying it). Each rollup entry has ticketCount, totalLoggedMinutes, avgLoggedMinutes, and missingTimeCount. Also returns `missingTimeCount`: the number of Done tickets with no time label (a data-quality gap that makes the hours less trustworthy \u2014 the dashboard page surfaces the actionable list). `period` selects the trend granularity (week|month, default week). Manager-gated. Use for 'how much support work did <project> need?', 'who's carrying the support load?', and 'is our support time logged completely?'.",
+      description: "Tech-support / DevOps effort rollup for the 'Tech Support Ops' Linear team (key DEV). Returns logged hours (parsed from each ticket's self-reported 'Time Spent' label \u2014 the architect's active effort, NOT cycle time) and ticket counts rolled up two ways: `byProject` (which client/product the support load lands on) and `byArchitect` (who is carrying it). Each rollup entry has ticketCount, totalLoggedMinutes, avgLoggedMinutes, and missingTimeCount. `byProjectMonthly` is a project \xD7 month matrix over the last 6 months (oldest \u2192 newest, zero-filled): each entry has projectId, projectName, and months[{period 'YYYY-MM', ticketCount, totalLoggedMinutes}] \u2014 use it for 'how much did project X cost us in June?' or 'how is support spend distributed across projects month over month?'. Also returns `missingTimeCount`: the number of Done tickets with no time label (a data-quality gap that makes the hours less trustworthy \u2014 the dashboard page surfaces the actionable list). Only tickets completed on/after 2026-07-01 count as missing time \u2014 older gaps are not backfillable and are exempt, though their logged hours still aggregate. `period` selects the trend granularity (week|month, default week). Manager-gated. Use for 'how much support work did <project> need?', 'who's carrying the support load?', and 'is our support time logged completely?'.",
       inputSchema: {
         period: external_exports.enum(["week", "month"]).optional().describe("Trend bucket granularity. Default week.")
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meltstudio/meltctl",
-  "version": "5.13.0",
+  "version": "5.15.0",
   "description": "AI-first development tooling for Melt teams — companion CLI for the org-distributed Claude Code dev skills",
   "main": "dist/index.js",
   "type": "module",