feat: dashboard weighs quality and splits work by a list field

The insights reading adds quality (open bugs per priority, bugs created
and closed per week for 8 weeks, QA returns and passes per area over 90
days, bugs reported in the 14 days after each of the last three
releases) and, for each list custom field, open tickets per option. The
dashboard shows both; the field to split by can be picked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

apps/mcp/src/app/api/taskstream.schema.ts

@@ -2229,6 +2229,50 @@ export interface components {
             stale: number;
             staleDays: number;
         };
+        PriorityCountDto: {
+            priority: components["schemas"]["IssuePriority"];
+            count: number;
+        };
+        BugWeekDto: {
+            /**
+             * Format: date
+             * @description Monday (UTC)
+             */
+            week: string;
+            created: number;
+            closed: number;
+        };
+        QaByAreaDto: {
+            /** @description Null: no area */
+            area: string | null;
+            returned: number;
+            passed: number;
+        };
+        EscapedBugsDto: {
+            /** Format: uuid */
+            releaseId: string;
+            name: string;
+            releasedAt: string;
+            /** @description Bugs reported in the 14 days after */
+            bugs: number;
+        };
+        QualityDto: {
+            openBugsByPriority: components["schemas"]["PriorityCountDto"][];
+            /** @description Last 8 weeks, oldest first */
+            bugWeeks: components["schemas"]["BugWeekDto"][];
+            qaByArea: components["schemas"]["QaByAreaDto"][];
+            escaped: components["schemas"]["EscapedBugsDto"][];
+        };
+        OptionCountDto: {
+            value: string;
+            count: number;
+        };
+        FieldBreakdownDto: {
+            fieldId: string;
+            counts: components["schemas"]["OptionCountDto"][];
+            /** @description Open tickets with no value */
+            none: number;
+        };
         ProjectInsightsDto: {
             generatedAt: string;
             sprint: components["schemas"]["SprintPulseDto"] | null;
@@ -2240,6 +2284,9 @@ export interface components {
             changes: components["schemas"]["ChangesSinceDto"] | null;
             team: components["schemas"]["TeamLoadDto"][];
             backlog: components["schemas"]["BacklogHealthDto"];
+            quality: components["schemas"]["QualityDto"];
+            /** @description One per active list custom field */
+            fields: components["schemas"]["FieldBreakdownDto"][];
         };
         ActivityDto: {
             id: string;

apps/mcp/src/app/tools/projects.resolver.ts

@@ -207,7 +207,7 @@ export class ProjectsResolver {
   @Tool({
     name: 'get_project_insights',
     description:
-      "The project's dashboard: the sprint under way (pace against time, behind or not), overdue, due-soon, blocked and stuck tickets, how long the work under way has been where it is (against the p85 cycle time), average days in each in-progress and QA status with WIP limits, when each planned release would be finished at the real pace (Monte Carlo), each person's open points against what they close per sprint, and open tickets missing an estimate, an area or an assignee. With since, also what changed after it.",
+      "The project's dashboard: the sprint under way (pace against time, behind or not), overdue, due-soon, blocked and stuck tickets, how long the work under way has been where it is (against the p85 cycle time), average days in each in-progress and QA status with WIP limits, when each planned release would be finished at the real pace (Monte Carlo), each person's open points against what they close per sprint, open tickets missing an estimate, an area or an assignee, quality (open bugs per priority, bugs created and closed per week, QA returns per area, bugs reported after each release) and open tickets per option of each list custom field. With since, also what changed after it.",
     paramsSchema: z.object({
       project: projectRef,
       since: z