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/application/src/lib/workflows.service.ts

@@ -0,0 +1,45 @@
+import { Injectable } from '@nestjs/common';
+import {
+  DEFAULT_PROJECT_SETTINGS,
+  IssueReadModel,
+  ProjectWorkflow,
+} from '@task-stream/api/tracker/domain';
+import { FindProjectsRepository } from './ports/find-projects.repository';
+
+/** How long a project's workflow is reused (a board asks once per ticket). */
+const TTL_MS = 2_000;
+
+/**
+ * The workflow of each project, for presenting tickets (e.g. which statuses a
+ * ticket can move to). Commands always load the aggregate instead.
+ */
+@Injectable()
+export class WorkflowsService {
+  private readonly cache = new Map<
+    string,
+    { at: number; workflow: Promise<ProjectWorkflow> }
+  >();
+
+  constructor(private readonly projects: FindProjectsRepository) {}
+
+  of(projectId: string): Promise<ProjectWorkflow> {
+    const now = Date.now();
+    const hit = this.cache.get(projectId);
+    if (hit && now - hit.at < TTL_MS) return hit.workflow;
+    for (const [id, entry] of this.cache)
+      if (now - entry.at >= TTL_MS) this.cache.delete(id);
+    const workflow = this.projects
+      .findById(projectId)
+      .then(
+        (project) =>
+          new ProjectWorkflow(project?.settings ?? DEFAULT_PROJECT_SETTINGS),
+      );
+    this.cache.set(projectId, { at: now, workflow });
+    return workflow;
+  }
+
+  /** Active statuses the ticket can move to next. */
+  async allowedTransitions(issue: IssueReadModel): Promise<string[]> {
+    return (await this.of(issue.projectId)).allowedFrom(issue.status);
+  }
+}