feat: per-project workflow settings, statistics and "my work" home

Per-project settings (owners/admins, «Configuración» tab):
- Statuses with category (TODO, IN_PROGRESS, QA, DONE, CANCELLED), colour and
  "requires reason"; configurable transitions; ticket types (icon, colour) and
  areas. Defaults are the previous fixed values; projects created before keep
  them without migration.
- Values are archived, never deleted: tickets, history and statistics keep
  referring to them. Validated in the domain (ProjectSettingsChangedEvent).
- Releases, board, tracking and "my work" use categories, so custom statuses
  keep working. Status changes carry name/category metadata for history.
- GraphQL: status/type/area are strings (breaking for clients sending enum
  literals); Project.settings, updateProjectSettings, statusCategory,
  myIssues(categories). REST: PUT /projects/{project}/settings, category filters.
- Read model: statusCategory on issues (backfilled at startup).

Statistics («Estadísticas» tab):
- New issue_timeline projection; pure functions compute created vs resolved,
  cumulative flow, cycle/lead time (avg + p85), throughput per person, QA
  pass/fail and release burnup. GraphQL Project.analytics(days),
  Release.burnup; REST /projects/{project}/analytics, /releases/{id}/burnup.
- Web: SVG charts with validated light/dark palette, crosshair tooltip,
  keyboard navigation, legend and data table.

Home "Mi trabajo": my open tickets across projects grouped by category (QA
failures first), tickets waiting for QA, upcoming releases and "Ir a…".

Tests: domain/application specs, e2e scenario for settings and analytics,
facade tests. Docs, READMEs, schema.gql/openapi.json and Word/PDF updated.

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

libs/api/tracker/infrastructure/src/lib/mongo/upsert-materialized.repositories.ts

@@ -6,14 +6,17 @@ import {
   UpsertMaterializedIssueRepository,
   UpsertMaterializedProjectRepository,
   UpsertMaterializedReleaseRepository,
+  UpsertMaterializedTimelineRepository,
 } from '@task-stream/api/tracker/application';
 import {
   ActivityReadModel,
   CommentReadModel,
   IssueLinkReadModel,
   IssueReadModel,
+  IssueTimelineEntry,
   ProjectReadModel,
   ReleaseReadModel,
+  StatusCategory,
 } from '@task-stream/api/tracker/domain';
 import { Model } from 'mongoose';
 import {
@@ -23,6 +26,7 @@ import {
   ProjectDoc,
   ReadModels,
   ReleaseDoc,
+  TimelineDoc,
 } from './read-model.schemas';
 import { upsertIfNewer } from './upsert-if-newer';
 
@@ -101,6 +105,19 @@ export class MongoUpsertMaterializedIssueRepository extends UpsertMaterializedIs
     await this.issues.updateOne({ _id: issueId }, { $set: { commentCount } });
   }
 
+  async recategorize(
+    projectId: string,
+    categories: Record<string, StatusCategory>,
+  ) {
+    const ops = Object.entries(categories).map(([status, category]) => ({
+      updateMany: {
+        filter: { projectId, status, statusCategory: { $ne: category } },
+        update: { $set: { statusCategory: category } },
+      },
+    }));
+    if (ops.length) await this.issues.bulkWrite(ops);
+  }
+
   async renameRelease(releaseId: string, name: string) {
     await this.issues.updateMany(
       { 'release.id': releaseId },
@@ -167,3 +184,21 @@ export class MongoUpsertMaterializedActivityRepository extends UpsertMaterialize
     return result.upsertedCount > 0;
   }
 }
+
+@Injectable()
+export class MongoUpsertMaterializedTimelineRepository extends UpsertMaterializedTimelineRepository {
+  constructor(
+    @InjectModel(ReadModels.Timeline)
+    private readonly timeline: Model<TimelineDoc>,
+  ) {
+    super();
+  }
+
+  async record({ id, ...fields }: IssueTimelineEntry): Promise<void> {
+    await this.timeline.updateOne(
+      { _id: id },
+      { $setOnInsert: fields },
+      { upsert: true },
+    );
+  }
+}