Create GraphQL endpoints to: 1. Get all workflows given a Linkable (e.g. given an issue, find all workflows created from it) 2. Get all Linkables given a workflow (e.g. get all MRs created from a Workflow) ## Proposal ### Design decision We will not expose a single merged "all linkables" connection. Instead, each linkable type gets its own field. This keeps every connection single-table, so pagination is trivial (standard keyset, no cross-table UNION, no composite cursor, no union type, no per-type batch-loading), and each field's linkType filter can use that join model's own enum directly. ### Query 1 — Linkable → Workflows Add a linkedDuoWorkflows(linkType:) field to each linkable's GraphQL type (starting with WorkItemType), backed by the existing linked_duo_workflows association. Optional linkType filter scopes the join table. ### Query 2 — Workflow → Linkables Add per-type fields to WorkflowType: workItemLinks(linkType:), and later mergeRequestLinks, pipelineLinks, noteLinks. Each is a single-table connection with an optional linkType filter. - The "filter by linkable class" requirement is satisfied by choosing which field to query. - All fields are backed by one generic resolver class parameterized by the join model, driven off the JOIN_MODELS registry — so adding a linkable type = new join model + one field declaration, no new resolver. ### Query 3 — Linkable → Workflows → Linkables No new query needed. GraphQL composes nested fields, so this falls out for free by nesting Query 2's field inside Query 1's: ```graphql { workItem(id: ID) { linkedDuoWorkflows { nodes { workItemLinks { nodes { linkType workItem { iid } } } } } } } ```