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/issues.service.ts

@@ -5,8 +5,6 @@ import {
   IssueDetails,
   IssueLinkType,
   IssueReadModel,
-  IssueStatus,
-  IssueType,
 } from '@task-stream/api/tracker/domain';
 import { AssignIssueCommand } from './commands/assign-issue.command';
 import { ChangeIssueStatusCommand } from './commands/change-issue-status.command';
@@ -21,10 +19,15 @@ import { GetActivityQuery } from './queries/get-activity.query';
 import { GetIssueQuery } from './queries/get-issue.query';
 import { GetIssuesByIdsQuery } from './queries/get-issues-by-ids.query';
 import { SearchIssuesQuery } from './queries/search-issues.query';
+import {
+  MyIssuesFilter,
+  SearchMyIssuesQuery,
+} from './queries/search-my-issues.query';
 
 export interface CreateIssueInput extends Omit<IssueDetails, 'title' | 'type'> {
   projectId: string;
-  type: IssueType;
+  /** A type id of the project's settings. */
+  type: string;
   title: string;
   assigneeId?: string | null;
   releaseId?: string | null;
@@ -71,7 +74,7 @@ export class IssuesService {
   changeStatus(
     actorId: string,
     issueId: string,
-    status: IssueStatus,
+    status: string,
     reason?: string | null,
   ): Promise<CommandResult> {
     return this.commandBus.execute(
@@ -135,6 +138,14 @@ export class IssuesService {
     return this.queryBus.execute(new SearchIssuesQuery(viewerId, filter));
   }
 
+  /** Across all my projects: assigned to me, or any ticket (e.g. waiting for QA). */
+  mine(
+    viewerId: string,
+    filter: MyIssuesFilter,
+  ): Promise<Page<IssueReadModel>> {
+    return this.queryBus.execute(new SearchMyIssuesQuery(viewerId, filter));
+  }
+
   activity(
     viewerId: string,
     params: {