@meltstudio/meltctl 4.165.0 → 4.166.1

package/dist/index.js

@@ -14,7 +14,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/utils/version.ts"() {
     "use strict";
-    CLI_VERSION = "4.165.0";
+    CLI_VERSION = "4.166.1";
   }
 });
 
@@ -1494,7 +1494,9 @@ var ISSUE_RULES = [
   {
     id: "roadmap.none",
     dimension: "roadmap",
-    severity: "high",
+    // Setup/hygiene gap — Medium, not High (#446 follow-up: process-hygiene
+    // rules softened so the portfolio's genuinely-critical signals stand out).
+    severity: "medium",
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
@@ -1521,17 +1523,26 @@ var ISSUE_RULES = [
   {
     id: "roadmap.no-features-with-active-phase",
     dimension: "roadmap",
-    severity: "high",
+    severity: "medium",
     label: "Active phase but no features",
     category: "sprint",
     howToFix: "Run a backlog-seeding session and add features to the active phase before the team starts",
     scope: "project"
   },
+  {
+    id: "roadmap.closed-phase-open-work",
+    dimension: "roadmap",
+    severity: "medium",
+    label: "Closed phase has unfinished features",
+    category: "gaps",
+    howToFix: "A closed phase still has features that aren't done/canceled. Decide per feature: mark it done in that phase if the work landed (update_phase_feature), or move it to an active phase if it's still in flight. (#446 stage 7)",
+    scope: "project"
+  },
   // Delivery — Board
   {
     id: "board.no-mapping",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
@@ -1540,7 +1551,7 @@ var ISSUE_RULES = [
   {
     id: "tracker.no-oauth",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     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",
@@ -1558,7 +1569,7 @@ var ISSUE_RULES = [
   {
     id: "board.health-low",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     label: "Board health below 40%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
@@ -4462,7 +4473,9 @@ var ISSUE_RULES2 = [
   {
     id: "roadmap.none",
     dimension: "roadmap",
-    severity: "high",
+    // Setup/hygiene gap — Medium, not High (#446 follow-up: process-hygiene
+    // rules softened so the portfolio's genuinely-critical signals stand out).
+    severity: "medium",
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
@@ -4489,17 +4502,26 @@ var ISSUE_RULES2 = [
   {
     id: "roadmap.no-features-with-active-phase",
     dimension: "roadmap",
-    severity: "high",
+    severity: "medium",
     label: "Active phase but no features",
     category: "sprint",
     howToFix: "Run a backlog-seeding session and add features to the active phase before the team starts",
     scope: "project"
   },
+  {
+    id: "roadmap.closed-phase-open-work",
+    dimension: "roadmap",
+    severity: "medium",
+    label: "Closed phase has unfinished features",
+    category: "gaps",
+    howToFix: "A closed phase still has features that aren't done/canceled. Decide per feature: mark it done in that phase if the work landed (update_phase_feature), or move it to an active phase if it's still in flight. (#446 stage 7)",
+    scope: "project"
+  },
   // Delivery — Board
   {
     id: "board.no-mapping",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
@@ -4508,7 +4530,7 @@ var ISSUE_RULES2 = [
   {
     id: "tracker.no-oauth",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     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",
@@ -4526,7 +4548,7 @@ var ISSUE_RULES2 = [
   {
     id: "board.health-low",
     dimension: "board",
-    severity: "high",
+    severity: "medium",
     label: "Board health below 40%",
     category: "sprint",
     howToFix: "Open the project's Linear board and triage the failing audit checks",
@@ -5051,7 +5073,7 @@ Mandatory caller behavior: present the phase's name + id + active/closed status
     "update_phase_feature",
     {
       title: "Update phase-feature membership",
-      description: "Edits the per-phase intent for a feature in a phase: targetStage (what this phase aims to bring the feature to), phaseDescription (PM-authored note about what this jump means in this phase), linearEpicUrl (per-phase Linear epic). The same feature can have different per-phase targets \u2014 e.g. 'prototype' in phase 1, 'MVP' in phase 2. Use after assign_feature_to_phase when the PM wants per-membership values different from the feature-row defaults. The PM should review the proposed change before this is called \u2014 this is a write operation. Pass linearEpicUrl=null to clear the per-phase Linear link.",
+      description: "Edits the per-phase intent for a feature in a phase: targetStage (what this phase aims to bring the feature to), phaseDescription (PM-authored note about what this jump means in this phase), linearEpicUrl (per-phase Linear epic), status (per-phase status \u2014 a feature can be done in one phase and in_progress in another). The same feature can have different per-phase values across phases. Use after assign_feature_to_phase when the PM wants per-membership values different from the feature-row defaults. The PM should review the proposed change before this is called \u2014 this is a write operation. Pass linearEpicUrl=null to clear the per-phase Linear link.",
       inputSchema: {
         phaseId: z3.string().uuid().describe("Phase id from list_phases."),
         featureId: z3.string().uuid().describe("Feature id of the membership to edit."),
@@ -5063,6 +5085,9 @@ Mandatory caller behavior: present the phase's name + id + active/closed status
         ),
         linearEpicUrl: z3.string().url().nullable().optional().describe(
           "Per-phase Linear epic URL. Each phase's work on a feature can be its own epic. Pass null to clear."
+        ),
+        status: z3.enum(["not_started", "in_progress", "done", "canceled"]).optional().describe(
+          "Per-phase status (#446 stage 7). Lets a feature be 'done' in a closed phase while still 'in_progress' in the active phase. Use this to resolve the close-phase warning when work for that phase is actually complete."
         )
       }
     },

package/package.json

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