feat(web): dependencies between epics on the roadmap

Arrows from an epic to the ones that wait for it («bloquea» / «depende
de»), drawn over the bars; dashed red, plus a note in words, when one
starts before the epic blocking it ends. The next batch and the ideas
kept or dropped are written down in docs/10-futuro.

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

libs/web/tracker/infrastructure/src/lib/adapters/graphql-issues.gateway.ts

@@ -50,7 +50,12 @@ import {
   UpdateIssueDocument,
 } from '../graphql/generated';
 import { GraphqlOperations } from './graphql-operations';
-import { toCommandResult, toIssue, toIssueSummary } from './mappers';
+import {
+  toCommandResult,
+  toIssue,
+  toIssueLink,
+  toIssueSummary,
+} from './mappers';
 
 @Injectable()
 export class GraphqlIssuesGateway extends IssuesGateway {
@@ -214,6 +219,7 @@ export class GraphqlIssuesGateway extends IssuesGateway {
         d.epics.map((epic) => ({
           issue: toIssueSummary(epic.issue),
           progress: { ...epic.progress },
+          links: epic.issue.links.map((l) => toIssueLink(l)),
         })),
       ),
     );

libs/web/tracker/infrastructure/src/lib/adapters/mappers.ts

@@ -3,6 +3,7 @@ import type {
   Comment,
   CommandResult,
   Issue,
+  IssueLink,
   IssueSummary,
   Project,
   ProjectSettings,
@@ -39,6 +40,12 @@ export const toProject = (p: ProjectFieldsFragment): Project => ({
 export const toIssueSummary = (i: IssueSummaryFieldsFragment): IssueSummary =>
   as<IssueSummary>(i);
 export const toIssue = (i: IssueFieldsFragment): Issue => as<Issue>(i);
+export const toIssueLink = (l: {
+  type: string;
+  direction: string;
+  issueId: string;
+  issueKey: string;
+}): IssueLink => as<IssueLink>({ ...l });
 export const toComment = (c: CommentFieldsFragment): Comment => c;
 export const toActivity = (a: ActivityFieldsFragment): Activity => a;
 export const toCommandResult = (