@meltstudio/meltctl 5.1.0 → 5.3.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.1.0";
+    CLI_VERSION = "5.3.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",
@@ -27273,6 +27278,29 @@ function createPmResource(config2) {
       });
       return unwrap("close phase", res);
     },
+    /**
+     * Lock a scenario into a proposed phase (scenario-planner slice 1):
+     * `scenario → proposed`. The phase starts feeding the planning baseline.
+     * Manager-only; throws if the phase isn't in the `scenario` state.
+     */
+    async lockPhase(id) {
+      const res = await apiFetch(config2, `/pm/phases/${id}/lock`, {
+        method: "POST"
+      });
+      return unwrap("lock phase", res);
+    },
+    /**
+     * Activate a proposed phase into the project's live primary (scenario-
+     * planner slice 1): `proposed → active`. Demotes any existing primary to
+     * `proposed`. Manager-only; throws if the phase isn't in the `proposed`
+     * state.
+     */
+    async activatePhase(id) {
+      const res = await apiFetch(config2, `/pm/phases/${id}/activate`, {
+        method: "POST"
+      });
+      return unwrap("activate phase", res);
+    },
     async deletePhase(id) {
       const res = await apiFetch(config2, `/pm/phases/${id}`, {
         method: "DELETE"
@@ -27325,6 +27353,11 @@ function createPmResource(config2) {
      * Patch the per-phase intent for a feature in a phase (#446 stage 2).
      * Edits the through-table row's `targetStage`, `phaseDescription`, and/or
      * `linearEpicUrl`. Server returns the updated membership row.
+     *
+     * Editing a membership inside a LOCKED phase (state `proposed`/`active`)
+     * ripples through downstream baselines on the next read, so it requires
+     * `force: true` (scenario-planner slice 1); without it the server rejects
+     * with 409. Ignored for scenario/completed phases.
      */
     async updatePhaseFeature(phaseId, featureId, patch) {
       const res = await apiFetch(config2, `/pm/phases/${phaseId}/features/${featureId}`, { method: "PATCH", body: JSON.stringify(patch) });
@@ -53430,6 +53463,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",
@@ -53515,6 +53553,29 @@ function createPmResource2(config2) {
       });
       return unwrap2("close phase", res);
     },
+    /**
+     * Lock a scenario into a proposed phase (scenario-planner slice 1):
+     * `scenario → proposed`. The phase starts feeding the planning baseline.
+     * Manager-only; throws if the phase isn't in the `scenario` state.
+     */
+    async lockPhase(id) {
+      const res = await apiFetch2(config2, `/pm/phases/${id}/lock`, {
+        method: "POST"
+      });
+      return unwrap2("lock phase", res);
+    },
+    /**
+     * Activate a proposed phase into the project's live primary (scenario-
+     * planner slice 1): `proposed → active`. Demotes any existing primary to
+     * `proposed`. Manager-only; throws if the phase isn't in the `proposed`
+     * state.
+     */
+    async activatePhase(id) {
+      const res = await apiFetch2(config2, `/pm/phases/${id}/activate`, {
+        method: "POST"
+      });
+      return unwrap2("activate phase", res);
+    },
     async deletePhase(id) {
       const res = await apiFetch2(config2, `/pm/phases/${id}`, {
         method: "DELETE"
@@ -53567,6 +53628,11 @@ function createPmResource2(config2) {
      * Patch the per-phase intent for a feature in a phase (#446 stage 2).
      * Edits the through-table row's `targetStage`, `phaseDescription`, and/or
      * `linearEpicUrl`. Server returns the updated membership row.
+     *
+     * Editing a membership inside a LOCKED phase (state `proposed`/`active`)
+     * ripples through downstream baselines on the next read, so it requires
+     * `force: true` (scenario-planner slice 1); without it the server rejects
+     * with 409. Ignored for scenario/completed phases.
      */
     async updatePhaseFeature(phaseId, featureId, patch) {
       const res = await apiFetch2(config2, `/pm/phases/${phaseId}/features/${featureId}`, { method: "PATCH", body: JSON.stringify(patch) });
@@ -54836,7 +54902,7 @@ function registerPhaseTools(server, getClient2) {
     "update_phase",
     {
       title: "Update phase",
-      description: "Patches fields on an existing phase. Pass only the fields you want to change. Common uses: rename, switch target shape, override or clear the computed current shape, set or clear primary, mark a phase closed/reopened. The PM should review the proposed change before this is called \u2014 this is a write operation. Setting closedAt non-null forces isActive=false + isPrimary=false; setting isActive=false also clears isPrimary.",
+      description: "Patches fields on an existing phase. Pass only the fields you want to change. Common uses: rename, switch target shape, override or clear the computed current shape, set or clear primary, mark a phase closed/reopened. The PM should review the proposed change before this is called \u2014 this is a write operation. Setting closedAt non-null forces isActive=false + isPrimary=false; setting isActive=false also clears isPrimary. Editing a LOCKED phase (state active/proposed) requires force=true.",
       inputSchema: {
         id: external_exports.string().uuid().describe("Phase id from list_phases or create_phase."),
         name: external_exports.string().min(1).optional(),
@@ -54856,6 +54922,9 @@ function registerPhaseTools(server, getClient2) {
         ),
         jumpDurationWeeks: external_exports.number().positive().optional().describe(
           "Override the project default jump duration for this phase, in weeks. Tighter (0.25-0.5) for fast iteration / proof-of-concept; longer (2-3) for hardening. The audit will eventually flag mismatches between jump duration and per-feature target stages."
+        ),
+        force: external_exports.boolean().optional().describe(
+          "Set true to edit a LOCKED phase (state active or proposed). Locked phases feed the planning baseline, so an edit recomputes every downstream phase/scenario \u2014 the server rejects with 409 unless force=true. Not needed for scenario (draft) phases."
         )
       }
     },
@@ -54902,7 +54971,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), 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.",
+      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. Editing a membership in a LOCKED phase (state active/proposed) requires force=true.",
       inputSchema: {
         phaseId: external_exports.string().uuid().describe("Phase id from list_phases."),
         featureId: external_exports.string().uuid().describe("Feature id of the membership to edit."),
@@ -54917,6 +54986,9 @@ Mandatory caller behavior: present the phase's name + id + active/closed status
         ),
         status: external_exports.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."
+        ),
+        force: external_exports.boolean().optional().describe(
+          "Set true to edit a membership in a LOCKED phase (state active or proposed). Without it the server rejects with 409, because editing a locked phase recomputes downstream planning baselines. Not needed for scenario (draft) phases."
         )
       }
     },

package/package.json

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