@meltstudio/meltctl 4.180.0 → 4.181.0

package/dist/index.js

@@ -14,7 +14,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/utils/version.ts"() {
     "use strict";
-    CLI_VERSION = "4.180.0";
+    CLI_VERSION = "4.181.0";
   }
 });
 
@@ -1530,7 +1530,9 @@ var ISSUE_RULES = [
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"],
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.no-active-phase",
@@ -1539,7 +1541,8 @@ var ISSUE_RULES = [
     label: "Features but no active phase",
     category: "gaps",
     howToFix: "Open the Roadmap tab and mark the phase the team is currently working on as active",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.empty-phase",
@@ -1548,7 +1551,8 @@ var ISSUE_RULES = [
     label: "Active phase is empty",
     category: "gaps",
     howToFix: "Open the Roadmap tab and attach the phase's planned features, or close the phase if it's done",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.no-features-with-active-phase",
@@ -1557,7 +1561,9 @@ var ISSUE_RULES = [
     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"
+    scope: "project",
+    suppressedInStatuses: ["commercial"],
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.closed-phase-open-work",
@@ -1566,7 +1572,8 @@ var ISSUE_RULES = [
     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"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-no-epic",
@@ -1575,7 +1582,8 @@ var ISSUE_RULES = [
     label: "Primary-phase feature missing Linear epic",
     category: "gaps",
     howToFix: "Wire each current-phase feature's Linear epic via update_phase_feature (linearEpicUrl) \u2014 without it the roadmap can't sync status from the board and shows everything as not-started",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-no-prd",
@@ -1584,7 +1592,8 @@ var ISSUE_RULES = [
     label: "Primary-phase feature missing PRD",
     category: "gaps",
     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)",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-status-mismatch",
@@ -1593,7 +1602,8 @@ var ISSUE_RULES = [
     label: "Roadmap status differs from Linear",
     category: "gaps",
     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",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   // Delivery — Board
   {
@@ -1603,7 +1613,8 @@ var ISSUE_RULES = [
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "tracker.no-oauth",
@@ -1612,7 +1623,8 @@ var ISSUE_RULES = [
     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",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "board.empty",
@@ -1666,7 +1678,8 @@ var ISSUE_RULES = [
     label: "Open stories not in the active cycle",
     category: "sprint",
     howToFix: "Add this sprint\u2019s stories to the active Linear cycle (a Sprint label is not the cycle) \u2014 otherwise velocity and burndown read as empty",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.in-progress-stale",
@@ -1675,7 +1688,8 @@ var ISSUE_RULES = [
     label: "Stale in-progress tickets",
     category: "sprint",
     howToFix: "Open the project board, ask the assignees what's blocking, and either move the ticket forward or back to the backlog",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.pm-silent-critical",
@@ -1687,7 +1701,8 @@ var ISSUE_RULES = [
     label: "PM silent in active cycle",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.pm-silent-medium",
@@ -1696,7 +1711,8 @@ var ISSUE_RULES = [
     label: "PM commenting on under 60% of active-cycle tickets",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Delivery — Risks
   {
@@ -1725,7 +1741,8 @@ var ISSUE_RULES = [
     label: "No activity in 21+ days",
     category: "gaps",
     howToFix: "No meltctl activity in N days \u2014 confirm the project is still active, or mark it on-hold",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["warranty", "closed", "on_hold"]
   },
   // Delivery — Plans
   {
@@ -1735,7 +1752,8 @@ var ISSUE_RULES = [
     label: "No recent plan",
     category: "plans",
     howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "plans.unscored",
@@ -1744,7 +1762,8 @@ var ISSUE_RULES = [
     label: "Plans not yet scored",
     category: "plans",
     howToFix: "Open the plan and click 'Score plan' to run the rubric",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "plans.stuck",
@@ -1755,7 +1774,8 @@ var ISSUE_RULES = [
     label: "Plan can't be scored",
     category: "plans",
     howToFix: "Re-run `meltctl plan submit` with a valid ticket, or close the plan if it's no longer relevant",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Delivery — Standups
   {
@@ -1765,7 +1785,8 @@ var ISSUE_RULES = [
     label: "Standup submission below 50%",
     category: "standup",
     howToFix: "Remind the team that standup is set for 9am Colombia; follow up with non-submitters",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "standups.punctuality",
@@ -1774,7 +1795,8 @@ var ISSUE_RULES = [
     label: "Standups submitted but often late",
     category: "standup",
     howToFix: "The team is submitting standups but many land late \u2014 nudge toward the 9am Colombia cutoff",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Code — Findings
   {
@@ -1816,7 +1838,8 @@ var ISSUE_RULES = [
     label: "Never audited",
     category: "audits",
     howToFix: "Run `/melt-audit` on the repo to create the baseline",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "audit.stale",
@@ -1827,6 +1850,19 @@ var ISSUE_RULES = [
     howToFix: "Run `/melt-audit` on the repo to refresh the baseline",
     scope: "project"
   },
+  {
+    id: "audit.overdue",
+    dimension: "audit-coverage",
+    // Low — a re-audit nudge, not an alarm. The team reserves red/high, and
+    // the 90-day `audit.stale` stays medium; this fills the 31–90 day gap so a
+    // repo flagged "overdue" on the card actually produces an issue + score
+    // impact (low still costs −2).
+    severity: "low",
+    label: "Audit overdue (30+ days)",
+    category: "audits",
+    howToFix: "A repo's last audit is over 30 days old \u2014 re-run `/melt-audit` (or the relevant audit skill) to refresh the findings.",
+    scope: "project"
+  },
   {
     id: "audit.partial",
     dimension: "audit-coverage",
@@ -1834,7 +1870,8 @@ var ISSUE_RULES = [
     label: "Some repos never audited",
     category: "audits",
     howToFix: "Run `/melt-audit` on each unaudited repo to create its baseline",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "audit.unprocessed",
@@ -4604,7 +4641,9 @@ var ISSUE_RULES2 = [
     label: "No roadmap",
     category: "gaps",
     howToFix: "Open the project's Roadmap tab and add an active phase with at least one planned feature",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"],
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.no-active-phase",
@@ -4613,7 +4652,8 @@ var ISSUE_RULES2 = [
     label: "Features but no active phase",
     category: "gaps",
     howToFix: "Open the Roadmap tab and mark the phase the team is currently working on as active",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.empty-phase",
@@ -4622,7 +4662,8 @@ var ISSUE_RULES2 = [
     label: "Active phase is empty",
     category: "gaps",
     howToFix: "Open the Roadmap tab and attach the phase's planned features, or close the phase if it's done",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.no-features-with-active-phase",
@@ -4631,7 +4672,9 @@ var ISSUE_RULES2 = [
     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"
+    scope: "project",
+    suppressedInStatuses: ["commercial"],
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.closed-phase-open-work",
@@ -4640,7 +4683,8 @@ var ISSUE_RULES2 = [
     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"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-no-epic",
@@ -4649,7 +4693,8 @@ var ISSUE_RULES2 = [
     label: "Primary-phase feature missing Linear epic",
     category: "gaps",
     howToFix: "Wire each current-phase feature's Linear epic via update_phase_feature (linearEpicUrl) \u2014 without it the roadmap can't sync status from the board and shows everything as not-started",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-no-prd",
@@ -4658,7 +4703,8 @@ var ISSUE_RULES2 = [
     label: "Primary-phase feature missing PRD",
     category: "gaps",
     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)",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   {
     id: "roadmap.feature-status-mismatch",
@@ -4667,7 +4713,8 @@ var ISSUE_RULES2 = [
     label: "Roadmap status differs from Linear",
     category: "gaps",
     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",
-    scope: "project"
+    scope: "project",
+    requiresRoadmapOwnership: true
   },
   // Delivery — Board
   {
@@ -4677,7 +4724,8 @@ var ISSUE_RULES2 = [
     label: "No board connected",
     category: "gaps",
     howToFix: "Open Project Settings and connect a Linear team or Jira project in the mappings card",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "tracker.no-oauth",
@@ -4686,7 +4734,8 @@ var ISSUE_RULES2 = [
     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",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "board.empty",
@@ -4740,7 +4789,8 @@ var ISSUE_RULES2 = [
     label: "Open stories not in the active cycle",
     category: "sprint",
     howToFix: "Add this sprint\u2019s stories to the active Linear cycle (a Sprint label is not the cycle) \u2014 otherwise velocity and burndown read as empty",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.in-progress-stale",
@@ -4749,7 +4799,8 @@ var ISSUE_RULES2 = [
     label: "Stale in-progress tickets",
     category: "sprint",
     howToFix: "Open the project board, ask the assignees what's blocking, and either move the ticket forward or back to the backlog",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.pm-silent-critical",
@@ -4761,7 +4812,8 @@ var ISSUE_RULES2 = [
     label: "PM silent in active cycle",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "board.pm-silent-medium",
@@ -4770,7 +4822,8 @@ var ISSUE_RULES2 = [
     label: "PM commenting on under 60% of active-cycle tickets",
     category: "sprint",
     howToFix: "Comment on the active-cycle tickets to acknowledge progress, ask questions, or flag concerns",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Delivery — Risks
   {
@@ -4799,7 +4852,8 @@ var ISSUE_RULES2 = [
     label: "No activity in 21+ days",
     category: "gaps",
     howToFix: "No meltctl activity in N days \u2014 confirm the project is still active, or mark it on-hold",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["warranty", "closed", "on_hold"]
   },
   // Delivery — Plans
   {
@@ -4809,7 +4863,8 @@ var ISSUE_RULES2 = [
     label: "No recent plan",
     category: "plans",
     howToFix: "Remind the team to run `meltctl plan submit` before starting new tickets",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "plans.unscored",
@@ -4818,7 +4873,8 @@ var ISSUE_RULES2 = [
     label: "Plans not yet scored",
     category: "plans",
     howToFix: "Open the plan and click 'Score plan' to run the rubric",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "plans.stuck",
@@ -4829,7 +4885,8 @@ var ISSUE_RULES2 = [
     label: "Plan can't be scored",
     category: "plans",
     howToFix: "Re-run `meltctl plan submit` with a valid ticket, or close the plan if it's no longer relevant",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Delivery — Standups
   {
@@ -4839,7 +4896,8 @@ var ISSUE_RULES2 = [
     label: "Standup submission below 50%",
     category: "standup",
     howToFix: "Remind the team that standup is set for 9am Colombia; follow up with non-submitters",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   {
     id: "standups.punctuality",
@@ -4848,7 +4906,8 @@ var ISSUE_RULES2 = [
     label: "Standups submitted but often late",
     category: "standup",
     howToFix: "The team is submitting standups but many land late \u2014 nudge toward the 9am Colombia cutoff",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["planning"]
   },
   // Code — Findings
   {
@@ -4890,7 +4949,8 @@ var ISSUE_RULES2 = [
     label: "Never audited",
     category: "audits",
     howToFix: "Run `/melt-audit` on the repo to create the baseline",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "audit.stale",
@@ -4901,6 +4961,19 @@ var ISSUE_RULES2 = [
     howToFix: "Run `/melt-audit` on the repo to refresh the baseline",
     scope: "project"
   },
+  {
+    id: "audit.overdue",
+    dimension: "audit-coverage",
+    // Low — a re-audit nudge, not an alarm. The team reserves red/high, and
+    // the 90-day `audit.stale` stays medium; this fills the 31–90 day gap so a
+    // repo flagged "overdue" on the card actually produces an issue + score
+    // impact (low still costs −2).
+    severity: "low",
+    label: "Audit overdue (30+ days)",
+    category: "audits",
+    howToFix: "A repo's last audit is over 30 days old \u2014 re-run `/melt-audit` (or the relevant audit skill) to refresh the findings.",
+    scope: "project"
+  },
   {
     id: "audit.partial",
     dimension: "audit-coverage",
@@ -4908,7 +4981,8 @@ var ISSUE_RULES2 = [
     label: "Some repos never audited",
     category: "audits",
     howToFix: "Run `/melt-audit` on each unaudited repo to create its baseline",
-    scope: "project"
+    scope: "project",
+    suppressedInStatuses: ["commercial"]
   },
   {
     id: "audit.unprocessed",
@@ -5662,7 +5736,7 @@ var submitDailyPlanInputSchema = z11.object({
 });
 function registerDailyPlanTools(server, getClient2) {
   server.registerTool(
-    "get_daily_plan",
+    "get_pm_daily_plan",
     {
       title: "Get the PM's daily plan",
       description: "Returns the calling PM's daily plan for a day (defaults to today, Colombia time), or null if none exists. Each agenda item has a label, optional project/meeting/suggestedSkill, a status (pending/done/blocked/carried), and an optional note. Use this in melt-pm-close-my-day to read back the morning's plan and reconcile it. Self-scoped \u2014 a PM only ever reads their own plan.",
@@ -5673,7 +5747,7 @@ function registerDailyPlanTools(server, getClient2) {
     withClientArgs(getClient2, getDailyPlan)
   );
   server.registerTool(
-    "submit_daily_plan",
+    "submit_pm_daily_plan",
     {
       title: "Submit/update the PM's daily plan",
       description: "Upserts the calling PM's daily plan for a day (defaults to today). melt-pm-plan-my-day calls this once it has built the morning agenda (items with status='pending'); melt-pm-close-my-day calls it again with the same items flipped to done/blocked/carried. Idempotent per (PM, day) \u2014 calling again replaces the day's agenda. Self-scoped.",

package/package.json

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