@taiga-ai/mcp-server 0.2.3-dev.278 → 0.2.3-dev.279

package/dist/index.js

@@ -169,13 +169,24 @@ const featureFlagDefinitions = Object.freeze({
 	*     flag flip would suddenly send
 	*   - web: the notification-contacts card is not rendered in project settings
 	*
-	* Release toggle: ON in local/dev/staging, OFF in prod while per-user
-	* recipients, the preference matrix and digests land behind it.
-	* **Remove this flag (and its gates) at GA.**
+	* Release toggle: ON everywhere as of 2026-09-13. What ships is the
+	* PROJECT-scoped contact: the org scope exists in the schema, the routing
+	* and the API, but no UI offers it and the docs page does not mention it,
+	* so it is dormant capability rather than a shipped feature. Per-user
+	* recipients, the preference matrix and digests are still unbuilt; they no
+	* longer sit behind this flag and want their own gate if they need one.
+	*
+	* The gate stays in place for one release so the feature can be turned off
+	* without a revert if prod surprises us. Turning it off is safe by
+	* construction and does not strand mail: with the flag false the routing
+	* path writes no `notification_deliveries` rows at all, so nothing
+	* accumulates to flood on a later flip.
+	* **Remove this flag (and its gates) once prod has run a release with it
+	* on.**
 	*/
 	notifications: {
 		description: "Notification delivery: verified per-scope email contacts (alternate contacts) that receive inbox items, plus the delivery queue and worker behind them.",
-		availability: "non-prod"
+		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.278",
+  "version": "0.2.3-dev.279",
   "description": "MCP server for Taiga -- gives AI assistants access to documents, skills, and projects",
   "type": "module",
   "main": "./dist/index.js",