@meltstudio/meltctl 4.190.0 → 4.191.0
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 -5
- 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.
|
|
17
|
+
CLI_VERSION = "4.191.0";
|
|
18
18
|
}
|
|
19
19
|
});
|
|
20
20
|
|
|
@@ -1179,9 +1179,16 @@ function createPmResource(config) {
|
|
|
1179
1179
|
* findings, board health, plan recency, activity, standup compliance,
|
|
1180
1180
|
* tickets) into a single response. Powers the `get_project_health`
|
|
1181
1181
|
* MCP tool.
|
|
1182
|
+
*
|
|
1183
|
+
* Pass `{ expandFindings: true }` to also receive `findingIssues`: the
|
|
1184
|
+
* project's open `audit_findings` rendered as per-finding `HealthIssue`s
|
|
1185
|
+
* for the project page's unified Issues section (#460/#461). The flag is
|
|
1186
|
+
* opt-in so MCP tool calls keep their lean shape and findings-heavy
|
|
1187
|
+
* projects don't blow up agent token budgets.
|
|
1182
1188
|
*/
|
|
1183
|
-
async getProjectHealth(projectId) {
|
|
1184
|
-
const
|
|
1189
|
+
async getProjectHealth(projectId, options) {
|
|
1190
|
+
const query = options?.expandFindings ? "?expandFindings=1" : "";
|
|
1191
|
+
const res = await apiFetch(config, `/pm/project-health/${projectId}${query}`);
|
|
1185
1192
|
return unwrap("get project health", res);
|
|
1186
1193
|
},
|
|
1187
1194
|
// ─── Detailed risks (per-project + cross-project) ────────────────────
|
|
@@ -4409,9 +4416,16 @@ function createPmResource2(config) {
|
|
|
4409
4416
|
* findings, board health, plan recency, activity, standup compliance,
|
|
4410
4417
|
* tickets) into a single response. Powers the `get_project_health`
|
|
4411
4418
|
* MCP tool.
|
|
4419
|
+
*
|
|
4420
|
+
* Pass `{ expandFindings: true }` to also receive `findingIssues`: the
|
|
4421
|
+
* project's open `audit_findings` rendered as per-finding `HealthIssue`s
|
|
4422
|
+
* for the project page's unified Issues section (#460/#461). The flag is
|
|
4423
|
+
* opt-in so MCP tool calls keep their lean shape and findings-heavy
|
|
4424
|
+
* projects don't blow up agent token budgets.
|
|
4412
4425
|
*/
|
|
4413
|
-
async getProjectHealth(projectId) {
|
|
4414
|
-
const
|
|
4426
|
+
async getProjectHealth(projectId, options) {
|
|
4427
|
+
const query = options?.expandFindings ? "?expandFindings=1" : "";
|
|
4428
|
+
const res = await apiFetch2(config, `/pm/project-health/${projectId}${query}`);
|
|
4415
4429
|
return unwrap2("get project health", res);
|
|
4416
4430
|
},
|
|
4417
4431
|
// ─── Detailed risks (per-project + cross-project) ────────────────────
|
package/package.json
CHANGED