@meltstudio/meltctl 5.0.5 → 5.2.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.0.5";
+    CLI_VERSION = "5.2.0";
   }
 });
 
@@ -27188,6 +27188,11 @@ function createPmResource(config2) {
       const res = await apiFetch(config2, `/pm/features/${id}`);
       return unwrap("get feature", res);
     },
+    /** Every project's primary active phase, for the cross-project overview. */
+    async listActivePhases() {
+      const res = await apiFetch(config2, `/pm/active-phases`);
+      return unwrap("list active phases", res);
+    },
     async createFeature(input) {
       const res = await apiFetch(config2, `/pm/features`, {
         method: "POST",
@@ -53430,6 +53435,11 @@ function createPmResource2(config2) {
       const res = await apiFetch2(config2, `/pm/features/${id}`);
       return unwrap2("get feature", res);
     },
+    /** Every project's primary active phase, for the cross-project overview. */
+    async listActivePhases() {
+      const res = await apiFetch2(config2, `/pm/active-phases`);
+      return unwrap2("list active phases", res);
+    },
     async createFeature(input) {
       const res = await apiFetch2(config2, `/pm/features`, {
         method: "POST",
@@ -55049,7 +55059,7 @@ Mandatory caller behavior: present the feature's name + id + every phase it curr
     "update_feature",
     {
       title: "Update feature",
-      description: "Patches fields on an existing feature. Pass only the fields you want to change. Common uses: advancing current_stage as work progresses, flipping status to in_progress/done, setting starting_point. The PM should review the proposed change before this is called \u2014 this is a write operation. Per-phase target stage + Linear epic are NOT set here \u2014 they live on the phase membership; use update_phase_feature for those.",
+      description: "Patches fields on an existing feature. Pass only the fields you want to change. Common uses: advancing current_stage as work progresses, flipping status to in_progress/done, setting starting_point. Setting status here also updates the status the roadmap shows for the feature in its PRIMARY active phase (that per-phase status is what the board renders). To set status for a specific non-primary phase, use update_phase_feature with that phaseId instead. The PM should review the proposed change before this is called \u2014 this is a write operation. Per-phase target stage + Linear epic are NOT set here \u2014 they live on the phase membership; use update_phase_feature for those.",
       inputSchema: {
         id: external_exports.string().uuid().describe("Feature id from list_features or create_feature."),
         name: external_exports.string().min(1).optional(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meltstudio/meltctl",
-  "version": "5.0.5",
+  "version": "5.2.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",