@taiga-ai/mcp-server 0.2.3-dev.261 → 0.2.3-dev.262
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js
CHANGED
|
@@ -75,23 +75,28 @@ const featureFlagDefinitions = Object.freeze({
|
|
|
75
75
|
availability: "non-prod"
|
|
76
76
|
},
|
|
77
77
|
/**
|
|
78
|
-
* UI
|
|
79
|
-
*
|
|
80
|
-
*
|
|
81
|
-
*
|
|
82
|
-
*
|
|
83
|
-
*
|
|
78
|
+
* UI Studio (PRO-630) — the workbench for AI-generated UI concepts of the
|
|
79
|
+
* CUSTOMER's app: the concept gallery, the sparring chat, iterate, and
|
|
80
|
+
* promoting an element into a Design Standards component. When `false` the
|
|
81
|
+
* workbench is fully dormant:
|
|
82
|
+
* - web: the concept gallery, the Studio, the initiative cockpit's
|
|
83
|
+
* direction card and the `/dev/ui-artifact-test` route are not
|
|
84
84
|
* registered
|
|
85
|
+
* - api: the Studio's own routes (persist, delete, feedback, iterate,
|
|
86
|
+
* promote-component) are not registered, and their job assemblers refuse
|
|
85
87
|
*
|
|
86
|
-
*
|
|
87
|
-
*
|
|
88
|
+
* NOT under this flag: the Look & Feel document (PRO-1376) and everything it
|
|
89
|
+
* runs on -- the concept compile/list/read/choose routes, the direction job,
|
|
90
|
+
* "Propose 2 more", the planner's direction summary and the build-time
|
|
91
|
+
* direction. Those shipped in PRO-1537. The flow surface moved out from under
|
|
92
|
+
* this flag in PRO-1029 and graduated to production in PRO-1535; it carries
|
|
93
|
+
* no flag any more.
|
|
88
94
|
*
|
|
89
|
-
* Release toggle: ON in local/dev/staging, OFF in prod
|
|
90
|
-
*
|
|
91
|
-
* **Remove this flag (and its gates) at GA.**
|
|
95
|
+
* Release toggle: ON in local/dev/staging, OFF in prod until the workbench
|
|
96
|
+
* has its own rollout decision. **Remove this flag (and its gates) at GA.**
|
|
92
97
|
*/
|
|
93
98
|
uiSparring: {
|
|
94
|
-
description: "UI
|
|
99
|
+
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.",
|
|
95
100
|
availability: "non-prod"
|
|
96
101
|
},
|
|
97
102
|
/**
|
|
@@ -145,40 +150,6 @@ const featureFlagDefinitions = Object.freeze({
|
|
|
145
150
|
questionnaires: {
|
|
146
151
|
description: "Questionnaire filling: answer an uploaded requirement spreadsheet from project evidence with citations, attest, and write the answers back.",
|
|
147
152
|
availability: "non-prod"
|
|
148
|
-
},
|
|
149
|
-
/**
|
|
150
|
-
* UI Studio Wizard (PRO-1030) — the guided three-choice route through the UI
|
|
151
|
-
* decisions, for the person finishing Discovery who does not want a
|
|
152
|
-
* workbench. When `false` the feature is fully dormant:
|
|
153
|
-
* - web: the `/ui-wizard` route is not registered, and Discovery's UI
|
|
154
|
-
* Studio card offers only the studio itself
|
|
155
|
-
*
|
|
156
|
-
* Split out of {@link FeatureFlags.uiSparring} rather than riding it, for the
|
|
157
|
-
* reason the user-flows surface once was (PRO-1029): the wizard and the studio are
|
|
158
|
-
* two front doors onto the same concepts, and they will not graduate on the
|
|
159
|
-
* same day. Everything the wizard reaches is gated on `uiSparring` server-side
|
|
160
|
-
* (the concept job's own assembler throws without it), so every gate on this
|
|
161
|
-
* flag ANDs the two — a wizard released alone would offer a button that 500s.
|
|
162
|
-
*
|
|
163
|
-
* Release toggle: ON in local/dev/staging, OFF in prod.
|
|
164
|
-
* **Remove this flag (and its gates) at GA.**
|
|
165
|
-
*/
|
|
166
|
-
uiStudioWizard: {
|
|
167
|
-
description: "UI Studio Wizard: the guided three-choice route through the UI decisions. Only works when uiSparring is also on, including on the API.",
|
|
168
|
-
availability: "non-prod"
|
|
169
|
-
},
|
|
170
|
-
/**
|
|
171
|
-
* Design-system emitter (PRO-887): materialise an organisation's INTERNAL
|
|
172
|
-
* Design Standards into `src/styles/design-tokens.css` + `DESIGN.md` in the
|
|
173
|
-
* generated application at build bootstrap. Never active for a tenant with a
|
|
174
|
-
* linked design-system repository (that repo is the source of truth).
|
|
175
|
-
*
|
|
176
|
-
* Release toggle: ON in local/dev/staging, OFF in prod until the first
|
|
177
|
-
* internal-DS build has been verified end to end.
|
|
178
|
-
*/
|
|
179
|
-
designEmitter: {
|
|
180
|
-
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.",
|
|
181
|
-
availability: "non-prod"
|
|
182
153
|
}
|
|
183
154
|
});
|
|
184
155
|
/** Every flag name, in registry order. */
|
package/package.json
CHANGED
|
Binary file
|
|
Binary file
|