@taiga-ai/mcp-server 0.2.3-dev.259 → 0.2.3-dev.261

package/dist/index.js

@@ -83,8 +83,8 @@ const featureFlagDefinitions = Object.freeze({
 	*   - api: the `/v1/projects/:projectId/ui-artifacts/*` endpoints are not
 	*     registered
 	*
-	* The flow surface moved out from under this flag in PRO-1029 — see
-	* {@link FeatureFlags.flowStudio}.
+	* The flow surface moved out from under this flag in PRO-1029 and
+	* graduated to production in PRO-1535; it carries no flag any more.
 	*
 	* Release toggle: ON in local/dev/staging, OFF in prod while the feature is
 	* built out (foundation slice → workshop → binding).
@@ -95,31 +95,6 @@ const featureFlagDefinitions = Object.freeze({
 		availability: "non-prod"
 	},
 	/**
-	* User Flow Studio (PRO-1029) — the conversational surface for the
-	* `user_flow` document: talk the flows into shape, the ux-planning agent
-	* drafts and revises them, every agreed change lands in the document.
-	*
-	* Split out of {@link FeatureFlags.uiSparring} because working out user flows
-	* is Discovery work that stands on its own: it happens before anyone asks
-	* what a screen looks like, and it is useful to a customer who never opens
-	* the UI Studio. Sharing one flag meant flows could not ship without shipping
-	* concept generation and the sparring chat with them.
-	*
-	* Gates the web surface only — the route and the Edit control on the user
-	* flows document. The streaming endpoint (`POST
-	* /v1/conversations/:id/workshop-stream`) is deliberately NOT gated: it
-	* carries a conversation, the same as the spec-chat route beside it, and
-	* hiding a page is not a reason to make an authenticated, capability-checked
-	* endpoint conditional.
-	*
-	* Release toggle: ON in local/dev/staging, OFF in prod until the surface has
-	* proven itself there. **Remove this flag (and its gates) at GA.**
-	*/
-	flowStudio: {
-		description: "User Flow Studio: the conversational surface where the ux-planning agent drafts and revises the user flows document.",
-		availability: "non-prod"
-	},
-	/**
 	* Customer-definable check-and-stamp checklists (PRO-946..948, design
 	* PRO-933). When `false` the feature is fully dormant:
 	*   - api: the `/v1/checklist-*` endpoints are not registered
@@ -179,7 +154,7 @@ const featureFlagDefinitions = Object.freeze({
 	*     Studio card offers only the studio itself
 	*
 	* Split out of {@link FeatureFlags.uiSparring} rather than riding it, for the
-	* reason {@link FeatureFlags.flowStudio} was: the wizard and the studio are
+	* reason the user-flows surface once was (PRO-1029): the wizard and the studio are
 	* two front doors onto the same concepts, and they will not graduate on the
 	* same day. Everything the wizard reaches is gated on `uiSparring` server-side
 	* (the concept job's own assembler throws without it), so every gate on this

package/package.json

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