@taiga-ai/mcp-server 0.2.3-dev.233 → 0.2.3-dev.234

package/dist/index.js

@@ -204,28 +204,6 @@ const featureFlagDefinitions = Object.freeze({
 	designEmitter: {
 		description: "Design-system emitter: writes an organization's internal design standards into design-tokens.css and DESIGN.md in the generated application at build bootstrap.",
 		availability: "non-prod"
-	},
-	/**
-	* Autonomous merge (project "Autonomous Merge") -- Taiga decides when an
-	* agent-authored pull request merges, under a customer-set autonomy policy,
-	* instead of parking every green PR at `needs_review` for a person.
-	*
-	* NOT the customer's switch, and the distinction is the whole reason this
-	* comment is long. THIS flag is a per-ENVIRONMENT constant answering "does
-	* the capability exist in this build at all". The customer's consent is a
-	* separate per-TENANT policy resolved across org -> team -> project ->
-	* initiative, where org defaults to off. Reading this flag as "the tenant
-	* enabled auto-merge" would merge into a repository whose owner never asked
-	* for it. One is the kill switch, the other is the consent; they are never
-	* interchangeable.
-	*
-	* Release toggle: ON in local/dev/staging, OFF in prod while the policy core,
-	* forge preflight, executor and safety net land.
-	* **Remove this flag (and its gates) at GA.**
-	*/
-	autoMerge: {
-		description: "Autonomous merge: Taiga merges green agent-authored pull requests under the customer's autonomy policy. This is the capability kill switch, not the tenant's consent.",
-		availability: "everywhere"
 	}
 });
 /** Every flag name, in registry order. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@taiga-ai/mcp-server",
-  "version": "0.2.3-dev.233",
+  "version": "0.2.3-dev.234",
   "description": "MCP server for Taiga -- gives AI assistants access to documents, skills, and projects",
   "type": "module",
   "main": "./dist/index.js",