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/web/tracker/application/src/lib/facades/project.facade.ts

@@ -3,6 +3,7 @@ import { injectDispatch } from '@ngrx/signals/events';
 import {
   CreateReleaseInput,
   ProjectRole,
+  ProjectSettings,
 } from '@task-stream/web/tracker/domain';
 import { projectPageEvents } from '../events/project.events';
 import { ProjectStore } from '../stores/project.store';
@@ -30,6 +31,16 @@ export class ProjectFacade {
   readonly canManage = this.store.canManage;
   /** Any role but viewer. */
   readonly canContribute = this.store.canContribute;
+  /** Statuses, ticket types and areas of this project (names, colours, lookups). */
+  readonly workflow = this.store.workflow;
+  readonly savingSettings = this.store.savingSettings;
+  /** Statistics of the last `analyticsDays()` days (see `loadAnalytics`). */
+  readonly analytics = this.store.analytics;
+  readonly analyticsDays = this.store.analyticsDays;
+  readonly analyticsLoading = this.store.analyticsLoading;
+  readonly analyticsError = this.store.analyticsError;
+  /** Burnup of the release asked for with `loadBurnup`. */
+  readonly burnup = this.store.burnup;
 
   /** Loads the project (by id or key) and follows its changes. */
   open(idOrKey: string): void {
@@ -74,6 +85,21 @@ export class ProjectFacade {
     this.dispatch.releaseArchiveRequested({ releaseId });
   }
 
+  /** Replaces statuses, transitions, types and areas (owners and admins). */
+  saveSettings(settings: ProjectSettings): void {
+    const projectId = this.projectId();
+    if (projectId) this.dispatch.settingsSaveRequested({ projectId, settings });
+  }
+
+  loadAnalytics(days = this.store.analyticsDays()): void {
+    const projectId = this.projectId();
+    if (projectId) this.dispatch.analyticsRequested({ projectId, days });
+  }
+
+  loadBurnup(releaseId: string): void {
+    this.dispatch.burnupRequested({ releaseId });
+  }
+
   private projectId(): string | null {
     return this.store.project()?.id ?? null;
   }