feat: dashboard maps the activity, follows a ticket's way and the proposals

Three more blocks on the project dashboard, also by REST, GraphQL and
MCP:
- Activity: what moved each day of the last 12 weeks, in a heatmap,
  with the busiest weekday and the longest lull.
- A ticket's way: for the tickets done in the last 90 days, where the
  time from created to done went, status by status (waiting included),
  and how much of it was work (flow efficiency).
- The public's proposals: received, waiting, under way, done and
  discarded, and the most voted still unanswered.

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

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

@@ -2441,6 +2441,46 @@ export interface components {
             /** @description Open tickets with no value */
             none: number;
         };
+        ActivityDayDto: {
+            /** @example 2026-10-15 */
+            day: string;
+            count: number;
+        };
+        JourneyStepDto: {
+            /** @description Status id of the project settings */
+            status: string;
+            /** @description Average days a closed ticket spent in it */
+            days: number;
+            /** @description Its part of the whole lead time, 0-100 */
+            share: number;
+        };
+        JourneyDto: {
+            /** @description Tickets done in the last 90 days */
+            samples: number;
+            leadDays: number | null;
+            /** @description Part of the lead time in an in-progress status, 0-100 */
+            flowEfficiency: number | null;
+            steps: components["schemas"]["JourneyStepDto"][];
+        };
+        WaitingProposalDto: {
+            id: string;
+            key: string;
+            title: string;
+            votes: number;
+            /** @description Days since it came in */
+            days: number;
+        };
+        ProposalsFunnelDto: {
+            received: number;
+            /** @description In the last 30 days */
+            receivedLately: number;
+            /** @description Open, not started, in no sprint nor release */
+            waiting: number;
+            underWay: number;
+            done: number;
+            discarded: number;
+            topWaiting: components["schemas"]["WaitingProposalDto"][];
+        };
         ProjectInsightsDto: {
             generatedAt: string;
             sprint: components["schemas"]["SprintPulseDto"] | null;
@@ -2455,6 +2495,11 @@ export interface components {
             quality: components["schemas"]["QualityDto"];
             /** @description One per active list custom field */
             fields: components["schemas"]["FieldBreakdownDto"][];
+            /** @description The last 12 weeks from a Monday, oldest first (84 days) */
+            heatmap: components["schemas"]["ActivityDayDto"][];
+            journey: components["schemas"]["JourneyDto"];
+            /** @description Null while the project has never had a proposal */
+            proposals: components["schemas"]["ProposalsFunnelDto"] | null;
         };
         ActivityDto: {
             id: string;

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

@@ -253,7 +253,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, 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.",
+      "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) open tickets per option of each list custom field, activity per day over the last 12 weeks, where the time of the tickets done lately went from created to done (days and share per status, and the part spent at work: flow efficiency) and, if the public has proposed anything, the proposals funnel (received, waiting, under way, done, discarded, most voted waiting). With since, also what changed after it.",
     paramsSchema: z.object({
       project: projectRef,
       since: z