@taiga-ai/mcp-server 0.28.0-dev.592 → 0.28.0-dev.594

package/dist/index.js

@@ -23159,7 +23159,8 @@ const TURN_EVENT_TRIGGERS = [
 	"archived",
 	"unarchived",
 	"changes_requested",
-	"changes_answered"
+	"changes_answered",
+	"run_replanned"
 ];
 /**
 * The events the feed reads beside the turn log (PRO-3156): a board move and
@@ -23436,6 +23437,7 @@ const BUILD_RUN_STATUSES = [
 	"ci_fixing",
 	"needs_review",
 	"reviewing",
+	"replanning",
 	"completed",
 	"failed",
 	"stopped",
@@ -23457,6 +23459,7 @@ const RUN_DISPOSITION = {
 	ci_fixing: "in_flight",
 	needs_review: "gated",
 	reviewing: "in_flight",
+	replanning: "in_flight",
 	completed: "succeeded",
 	failed: "failed",
 	stopped: "stopped",
@@ -23518,6 +23521,7 @@ const BUILD_RUN_ACTIVE_STATUSES = BUILD_RUN_STATUSES.filter((s) => runDispositio
 * DIFFERENT, narrower concept: transitions a user command may never leave.
 */
 const BUILD_RUN_TERMINAL_STATUSES = BUILD_RUN_STATUSES.filter((s) => runDisposition(s) !== "in_flight");
+[...BUILD_RUN_TERMINAL_STATUSES];
 /**
 * Why the agent kept a pull request a draft, as recorded in its description
 * (PRO-2298). The API reads these markers; the run's escalation carries them.
@@ -23548,6 +23552,10 @@ const READY_BLOCKERS = [
 *   some of them unfixed (PRO-3126). Each thread says what was tried and what
 *   stopped it; with nothing pushed, nothing new arrives to review, so without
 *   this the run sat on "waiting for merge" with the comments unanswered.
+* - `changes_not_planned`: a person asked for changes at the review gate and
+*   the planner refused or failed to plan them (PRO-3165). The pull request is
+*   unchanged and waits for the person again; auto-merge must not take it
+*   before they decide.
 */
 const REVIEW_ESCALATION_REASONS = [
 	"ci_fix_cap",
@@ -23557,7 +23565,8 @@ const REVIEW_ESCALATION_REASONS = [
 	"check_weakened",
 	"review_bot_cap",
 	"ci_never_settled",
-	"review_fix_stalled"
+	"review_fix_stalled",
+	"changes_not_planned"
 ];
 /** One failing check as stored: the name is required, and the link survives only as http(s). */
 const storedFailingCheck = object({
@@ -27282,7 +27291,8 @@ const RUNNING = {
 	pushing: "pushing the branch",
 	ci_checking: "waiting for the pull request's CI",
 	ci_fixing: "fixing what CI found",
-	reviewing: "answering review comments on the pull request"
+	reviewing: "answering review comments on the pull request",
+	replanning: "revising the steps left to build for a request for changes"
 };
 /** Why the agent handed a run back, in the web's words (apps/web handback), with the checks it names. */
 function handbackSaid(escalation) {
@@ -27299,6 +27309,7 @@ function handbackSaid(escalation) {
 		case "review_bot_cap": return `review bots still have open comments${rounds}`;
 		case "ci_never_settled": return "CI did not finish in time";
 		case "review_fix_stalled": return "Taiga could not fix some review comments; its replies say what it tried";
+		case "changes_not_planned": return "the planner did not plan the request for changes, so the pull request is as it was";
 		case "ready_blocked": return `CI is green, but Taiga kept the pull request a draft${blockers.length ? `: ${blockers.join("; ")}` : ""}`;
 		case "check_weakened": return `CI went green only after a fix changed ${typeof e.file === "string" ? e.file : "a CI workflow or a test"}`;
 		default: return typeof e.reason === "string" ? e.reason : null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taiga-ai/mcp-server",
-  "version": "0.28.0-dev.592",
+  "version": "0.28.0-dev.594",
   "description": "Taiga for AI coding assistants: read products, policies, initiatives and runs, and operate the line, over MCP",
   "mcpName": "ga.tai/mcp-server",
   "license": "UNLICENSED",