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/presenters/src/lib/common/settings.ts

@@ -0,0 +1,56 @@
+import {
+  ProjectSettings,
+  SettingColor,
+  StatusCategory,
+  TypeIcon,
+} from '@task-stream/api/tracker/domain';
+
+/** Settings as the APIs carry them: transitions as a list instead of a map. */
+export interface SettingsPayload {
+  statuses: {
+    id: string;
+    name: string;
+    category: StatusCategory;
+    color: string;
+    requiresReason: boolean;
+    archived: boolean;
+  }[];
+  transitions: { from: string; to: string[] }[];
+  issueTypes: {
+    id: string;
+    name: string;
+    icon: string;
+    color: string;
+    archived: boolean;
+  }[];
+  areas: { id: string; name: string; archived: boolean }[];
+}
+
+export function toSettingsPayload(settings: ProjectSettings): SettingsPayload {
+  return {
+    ...settings,
+    transitions: settings.statuses.map((s) => ({
+      from: s.id,
+      to: settings.transitions[s.id] ?? [],
+    })),
+  };
+}
+
+/** Colours and icons are checked by the domain (validateProjectSettings). */
+export function fromSettingsPayload(payload: SettingsPayload): ProjectSettings {
+  return {
+    statuses: payload.statuses.map((s) => ({
+      ...s,
+      color: s.color as SettingColor,
+    })),
+    transitions: Object.fromEntries(
+      payload.transitions.map((t) => [t.from, t.to]),
+    ),
+    issueTypes: payload.issueTypes.map((t) => ({
+      ...t,
+      icon: t.icon as TypeIcon,
+      color: t.color as SettingColor,
+    })),
+    areas: payload.areas,
+  };
+}