@meltstudio/meltctl 4.179.0 → 4.179.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +19 -1
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -14,7 +14,7 @@ var CLI_VERSION;
|
|
|
14
14
|
var init_version = __esm({
|
|
15
15
|
"src/utils/version.ts"() {
|
|
16
16
|
"use strict";
|
|
17
|
-
CLI_VERSION = "4.179.
|
|
17
|
+
CLI_VERSION = "4.179.2";
|
|
18
18
|
}
|
|
19
19
|
});
|
|
20
20
|
|
|
@@ -1586,6 +1586,15 @@ var ISSUE_RULES = [
|
|
|
1586
1586
|
howToFix: "Write a PRD for each current-phase feature and link it on the feature (prdPath) \u2014 without one the dev team plans the work blind and plans score low on PRD alignment. PRD authoring is a PM deliverable (melt-pm-tech-investigate drafts the maturity/PRD sections)",
|
|
1587
1587
|
scope: "project"
|
|
1588
1588
|
},
|
|
1589
|
+
{
|
|
1590
|
+
id: "roadmap.feature-status-mismatch",
|
|
1591
|
+
dimension: "roadmap",
|
|
1592
|
+
severity: "medium",
|
|
1593
|
+
label: "Roadmap status differs from Linear",
|
|
1594
|
+
category: "gaps",
|
|
1595
|
+
howToFix: "A current-phase feature's roadmap status (what the client sees) disagrees with its linked Linear epic. The roadmap is the source of truth and is never auto-overwritten \u2014 reconcile so the client sees reality: either move the Linear epic to match the roadmap, or update the feature status (update_feature) to match where the work actually is",
|
|
1596
|
+
scope: "project"
|
|
1597
|
+
},
|
|
1589
1598
|
// Delivery — Board
|
|
1590
1599
|
{
|
|
1591
1600
|
id: "board.no-mapping",
|
|
@@ -4642,6 +4651,15 @@ var ISSUE_RULES2 = [
|
|
|
4642
4651
|
howToFix: "Write a PRD for each current-phase feature and link it on the feature (prdPath) \u2014 without one the dev team plans the work blind and plans score low on PRD alignment. PRD authoring is a PM deliverable (melt-pm-tech-investigate drafts the maturity/PRD sections)",
|
|
4643
4652
|
scope: "project"
|
|
4644
4653
|
},
|
|
4654
|
+
{
|
|
4655
|
+
id: "roadmap.feature-status-mismatch",
|
|
4656
|
+
dimension: "roadmap",
|
|
4657
|
+
severity: "medium",
|
|
4658
|
+
label: "Roadmap status differs from Linear",
|
|
4659
|
+
category: "gaps",
|
|
4660
|
+
howToFix: "A current-phase feature's roadmap status (what the client sees) disagrees with its linked Linear epic. The roadmap is the source of truth and is never auto-overwritten \u2014 reconcile so the client sees reality: either move the Linear epic to match the roadmap, or update the feature status (update_feature) to match where the work actually is",
|
|
4661
|
+
scope: "project"
|
|
4662
|
+
},
|
|
4645
4663
|
// Delivery — Board
|
|
4646
4664
|
{
|
|
4647
4665
|
id: "board.no-mapping",
|
package/package.json
CHANGED