@meltstudio/meltctl 5.14.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.14.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();
@@ -54567,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();
@@ -55961,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.
@@ -55973,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.14.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",