@taiga-ai/mcp-server 0.2.3-dev.260 → 0.2.3-dev.262

package/dist/index.js

@@ -75,48 +75,28 @@ const featureFlagDefinitions = Object.freeze({
 		availability: "non-prod"
 	},
 	/**
-	* UI Sparring (PRO-630) — AI-generated UI concepts for the CUSTOMER's app,
-	* rendered client-side in a sandboxed iframe styled with the tenant's
-	* design_standards tokens. When `false` the feature is fully dormant:
-	*   - web: the concept gallery, the Studio and the `/dev/ui-artifact-test`
-	*     route are not registered
-	*   - api: the `/v1/projects/:projectId/ui-artifacts/*` endpoints are not
+	* UI Studio (PRO-630) — the workbench for AI-generated UI concepts of the
+	* CUSTOMER's app: the concept gallery, the sparring chat, iterate, and
+	* promoting an element into a Design Standards component. When `false` the
+	* workbench is fully dormant:
+	*   - web: the concept gallery, the Studio, the initiative cockpit's
+	*     direction card and the `/dev/ui-artifact-test` route are not
 	*     registered
+	*   - api: the Studio's own routes (persist, delete, feedback, iterate,
+	*     promote-component) are not registered, and their job assemblers refuse
 	*
-	* The flow surface moved out from under this flag in PRO-1029 — see
-	* {@link FeatureFlags.flowStudio}.
+	* NOT under this flag: the Look & Feel document (PRO-1376) and everything it
+	* runs on -- the concept compile/list/read/choose routes, the direction job,
+	* "Propose 2 more", the planner's direction summary and the build-time
+	* direction. Those shipped in PRO-1537. 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).
-	* **Remove this flag (and its gates) at GA.**
+	* Release toggle: ON in local/dev/staging, OFF in prod until the workbench
+	* has its own rollout decision. **Remove this flag (and its gates) at GA.**
 	*/
 	uiSparring: {
-		description: "UI Sparring: AI-generated UI concepts for the customer's application, the concept gallery and the UI Studio, with their API endpoints.",
-		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.",
+		description: "UI Studio: the workbench for AI-generated UI concepts of the customer's application, with its own API endpoints. Look & Feel is not under it.",
 		availability: "non-prod"
 	},
 	/**
@@ -170,40 +150,6 @@ const featureFlagDefinitions = Object.freeze({
 	questionnaires: {
 		description: "Questionnaire filling: answer an uploaded requirement spreadsheet from project evidence with citations, attest, and write the answers back.",
 		availability: "non-prod"
-	},
-	/**
-	* UI Studio Wizard (PRO-1030) — the guided three-choice route through the UI
-	* decisions, for the person finishing Discovery who does not want a
-	* workbench. When `false` the feature is fully dormant:
-	*   - web: the `/ui-wizard` route is not registered, and Discovery's UI
-	*     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
-	* 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
-	* flag ANDs the two — a wizard released alone would offer a button that 500s.
-	*
-	* Release toggle: ON in local/dev/staging, OFF in prod.
-	* **Remove this flag (and its gates) at GA.**
-	*/
-	uiStudioWizard: {
-		description: "UI Studio Wizard: the guided three-choice route through the UI decisions. Only works when uiSparring is also on, including on the API.",
-		availability: "non-prod"
-	},
-	/**
-	* Design-system emitter (PRO-887): materialise an organisation's INTERNAL
-	* Design Standards into `src/styles/design-tokens.css` + `DESIGN.md` in the
-	* generated application at build bootstrap. Never active for a tenant with a
-	* linked design-system repository (that repo is the source of truth).
-	*
-	* Release toggle: ON in local/dev/staging, OFF in prod until the first
-	* internal-DS build has been verified end to end.
-	*/
-	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"
 	}
 });
 /** Every flag name, in registry order. */

package/package.json

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