@enrichlayer/el-linear 1.10.0 → 1.15.0

package/dist/queries/issues.js

@@ -41,12 +41,23 @@ export const FILTERED_SEARCH_ISSUES_QUERY = `
     }
   }
 `;
+/**
+ * Batch-resolves a search's team/project/assignee/delegate filter inputs.
+ *
+ * The `projects` block is `@include`-gated: Linear treats a null filter
+ * comparator as "no filter", so an always-on block with an unset
+ * `$projectName` would fetch an arbitrary project. (Search resolves a UUID
+ * `--project` directly without consulting this block, so only the
+ * name-resolution arm is needed here.)
+ */
 export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
   query BatchResolveForSearch(
     $teamKey: String
     $teamName: String
     $projectName: String
+    $hasProjectName: Boolean = false
     $assigneeEmail: String
+    $delegateEmail: String
   ) {
     teams(
       filter: {
@@ -64,7 +75,10 @@ export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
       }
     }
 
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
       nodes {
         id
         name
@@ -78,6 +92,14 @@ export const BATCH_RESOLVE_FOR_SEARCH_QUERY = `
         email
       }
     }
+
+    delegates: users(filter: { email: { eq: $delegateEmail } }, first: 1) {
+      nodes {
+        id
+        name
+        email
+      }
+    }
   }
 `;
 export const GET_ISSUE_BY_ID_QUERY = `
@@ -102,14 +124,46 @@ export const GET_ISSUE_BY_IDENTIFIER_QUERY = `
     }
   }
 `;
+/**
+ * Batch-resolves an update's project/milestone/issue inputs.
+ *
+ * The project and milestone blocks are `@include`-gated for the same
+ * reason as `BATCH_RESOLVE_FOR_CREATE_QUERY`: a null filter comparator is
+ * a no-op that returns an arbitrary record. A UUID `--project` is resolved
+ * by `id` (`projectsById`) so its milestones are still fetched for
+ * `--project-milestone` name resolution; a name uses `projectsByName`.
+ */
 export const BATCH_RESOLVE_FOR_UPDATE_QUERY = `
   query BatchResolveForUpdate(
     $projectName: String
+    $projectId: ID
+    $hasProjectName: Boolean = false
+    $hasProjectId: Boolean = false
     $teamKey: String
     $issueNumber: Float
     $milestoneName: String
+    $hasMilestoneName: Boolean = false
   ) {
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projectsByName: projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
+      nodes {
+        id
+        name
+        projectMilestones {
+          nodes {
+            id
+            name
+          }
+        }
+      }
+    }
+
+    projectsById: projects(
+      filter: { id: { eq: $projectId } }
+      first: 1
+    ) @include(if: $hasProjectId) {
       nodes {
         id
         name
@@ -125,7 +179,7 @@ export const BATCH_RESOLVE_FOR_UPDATE_QUERY = `
     milestones: projectMilestones(
       filter: { name: { eq: $milestoneName } }
       first: 1
-    ) {
+    ) @include(if: $hasMilestoneName) {
       nodes {
         id
         name
@@ -209,14 +263,37 @@ export const DELETE_ISSUE_MUTATION = `
     }
   }
 `;
+/**
+ * Batch-resolves a create's team/project/milestone/parent inputs in one
+ * round-trip.
+ *
+ * The project and milestone blocks are gated behind `@include` directives
+ * rather than left always-on. Linear treats a null filter comparator
+ * (`{ name: { eqIgnoreCase: null } }`) as "no filter" — so an always-on
+ * `projects` block with an unset `$projectName` returns an *arbitrary*
+ * project, which the caller would then mistake for the user's project
+ * (e.g. auto-switching the team to that unrelated project's team). The
+ * `has*` booleans ensure a block is fetched only when its input exists.
+ *
+ * A UUID `--project` is resolved by `id` (`projectsById`) so its team
+ * associations are still fetched for team-project validation; a name is
+ * resolved by `name` (`projectsByName`). The two are mutually exclusive,
+ * but GraphQL forbids two same-aliased fields with differing arguments,
+ * so they carry distinct aliases and the service folds whichever ran
+ * into `resolveResult.projects`.
+ */
 export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
   query BatchResolveForCreate(
     $teamKey: String
     $teamName: String
     $projectName: String
+    $projectId: ID
+    $hasProjectName: Boolean = false
+    $hasProjectId: Boolean = false
     $parentTeamKey: String
     $parentIssueNumber: Float
     $milestoneName: String
+    $hasMilestoneName: Boolean = false
   ) {
     teams(
       filter: {
@@ -234,7 +311,26 @@ export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
       }
     }
 
-    projects(filter: { name: { eqIgnoreCase: $projectName } }, first: 1) {
+    projectsByName: projects(
+      filter: { name: { eqIgnoreCase: $projectName } }
+      first: 1
+    ) @include(if: $hasProjectName) {
+      nodes {
+        id
+        name
+        teams {
+          nodes { id key }
+        }
+        projectMilestones {
+          nodes { id name }
+        }
+      }
+    }
+
+    projectsById: projects(
+      filter: { id: { eq: $projectId } }
+      first: 1
+    ) @include(if: $hasProjectId) {
       nodes {
         id
         name
@@ -250,7 +346,7 @@ export const BATCH_RESOLVE_FOR_CREATE_QUERY = `
     milestones: projectMilestones(
       filter: { name: { eq: $milestoneName } }
       first: 1
-    ) {
+    ) @include(if: $hasMilestoneName) {
       nodes {
         id
         name
@@ -332,6 +428,30 @@ export const GET_ISSUE_TEAM_QUERY = `
     }
   }
 `;
+export const GET_ISSUE_START_CONTEXT_QUERY = `
+  query GetIssueStartContext($id: String!) {
+    issue(id: $id) {
+      id
+      identifier
+      state { id name type }
+      team { id key name }
+      delegate { id name url }
+    }
+  }
+`;
+export const TEAM_STARTED_STATUSES_QUERY = `
+  query TeamStartedStatuses($teamId: String!) {
+    team(id: $teamId) {
+      states(filter: { type: { eq: "started" } }) {
+        nodes {
+          id
+          name
+          position
+        }
+      }
+    }
+  }
+`;
 export const ISSUE_RELATION_CREATE_MUTATION = `
   mutation IssueRelationCreate($input: IssueRelationCreateInput!) {
     issueRelationCreate(input: $input) {

package/dist/queries/labels-types.d.ts

@@ -2,17 +2,17 @@
  * Typed response shapes for the queries in `./labels.ts`.
  * See `./issues-types.ts` for the rationale (ALL-937).
  */
-export interface LabelTeamRef {
+interface LabelTeamRef {
     id: string;
     key: string;
     name: string;
 }
-export interface LabelParentRef {
+interface LabelParentRef {
     id: string;
     name: string;
 }
 /** Mirrors the issueLabel selection set on `CREATE_LABEL_MUTATION`. */
-export interface CreatedLabelNode {
+interface CreatedLabelNode {
     id: string;
     name: string;
     color: string;
@@ -20,7 +20,7 @@ export interface CreatedLabelNode {
     parent: LabelParentRef | null;
 }
 /** Mirrors the issueLabel selection set on `RETIRE_LABEL_MUTATION`. */
-export interface RetiredLabelNode {
+interface RetiredLabelNode {
     id: string;
     name: string;
     color: string;
@@ -28,13 +28,13 @@ export interface RetiredLabelNode {
     team: LabelTeamRef | null;
 }
 /** Mirrors the issueLabel selection set on `RESTORE_LABEL_MUTATION`. */
-export interface RestoredLabelNode {
+interface RestoredLabelNode {
     id: string;
     name: string;
     color: string;
     team: LabelTeamRef | null;
 }
-export interface ParentLabelNode {
+interface ParentLabelNode {
     id: string;
     name: string;
     isGroup: boolean;
@@ -62,3 +62,4 @@ export interface RestoreLabelResponse {
         issueLabel: RestoredLabelNode | null;
     };
 }
+export {};

package/dist/queries/project-milestones-types.d.ts

@@ -8,7 +8,7 @@
  * consumer reads only what was actually selected.
  */
 import type { IssueNode } from "./issues-types.js";
-export interface MilestoneProjectRef {
+interface MilestoneProjectRef {
     id: string;
     name: string;
 }
@@ -16,7 +16,7 @@ export interface MilestoneProjectRef {
  * Mirrors the milestone selection set in `LIST_PROJECT_MILESTONES_QUERY`
  * — full milestone fields without the project-back-reference.
  */
-export interface MilestoneListNode {
+interface MilestoneListNode {
     id: string;
     name: string;
     description: string | null;
@@ -29,7 +29,7 @@ export interface MilestoneListNode {
  * Mirrors the milestone selection set in `GET_PROJECT_MILESTONE_BY_ID_QUERY`
  * — list shape + project + issues connection.
  */
-export interface MilestoneDetailNode extends MilestoneListNode {
+interface MilestoneDetailNode extends MilestoneListNode {
     project: MilestoneProjectRef;
     issues: {
         nodes: IssueNode[];
@@ -50,7 +50,7 @@ export interface MilestoneLookupNode {
  * Mirrors the milestone selection set on the create / update mutations —
  * list shape + project (no issues connection).
  */
-export interface MutatedMilestoneNode extends MilestoneListNode {
+interface MutatedMilestoneNode extends MilestoneListNode {
     project: MilestoneProjectRef;
 }
 export interface ListProjectMilestonesResponse {
@@ -89,3 +89,4 @@ export interface UpdateProjectMilestoneResponse {
         projectMilestone: MutatedMilestoneNode | null;
     };
 }
+export {};

package/dist/queries/project-milestones.d.ts

@@ -1,5 +1,5 @@
 export declare const LIST_PROJECT_MILESTONES_QUERY = "\n  query ListProjectMilestones($projectId: String!, $first: Int!) {\n    project(id: $projectId) {\n      id\n      name\n      projectMilestones(first: $first) {\n        nodes {\n          id\n          name\n          description\n          targetDate\n          sortOrder\n          createdAt\n          updatedAt\n        }\n      }\n    }\n  }\n";
-export declare const GET_PROJECT_MILESTONE_BY_ID_QUERY = "\n  query GetProjectMilestone($id: String!, $issuesFirst: Int) {\n    projectMilestone(id: $id) {\n      id\n      name\n      description\n      targetDate\n      sortOrder\n      createdAt\n      updatedAt\n      project {\n        id\n        name\n      }\n      issues(first: $issuesFirst) {\n        nodes {\n          \n  \n  id\n  identifier\n  title\n  description\n  summary { content generationStatus }\n  branchName\n  priority\n  estimate\n  dueDate\n  url\n  createdAt\n  updatedAt\n\n  \n  state {\n    id\n    name\n  }\n\n  \n  assignee {\n    id\n    name\n    url\n  }\n\n  \n  team {\n    id\n    key\n    name\n  }\n\n  \n  project {\n    id\n    name\n  }\n\n  \n  labels {\n    nodes {\n      id\n      name\n    }\n  }\n\n  \n  cycle {\n    id\n    name\n    number\n  }\n\n  \n  projectMilestone {\n    id\n    name\n    targetDate\n  }\n\n  \n  parent {\n    id\n    identifier\n    title\n  }\n\n  \n  children {\n    nodes {\n      id\n      identifier\n      title\n    }\n  }\n\n\n        }\n      }\n    }\n  }\n";
+export declare const GET_PROJECT_MILESTONE_BY_ID_QUERY = "\n  query GetProjectMilestone($id: String!, $issuesFirst: Int) {\n    projectMilestone(id: $id) {\n      id\n      name\n      description\n      targetDate\n      sortOrder\n      createdAt\n      updatedAt\n      project {\n        id\n        name\n      }\n      issues(first: $issuesFirst) {\n        nodes {\n          \n  \n  id\n  identifier\n  title\n  description\n  summary { content generationStatus }\n  branchName\n  priority\n  estimate\n  dueDate\n  url\n  createdAt\n  updatedAt\n\n  \n  state {\n    id\n    name\n  }\n\n  \n  assignee {\n    id\n    name\n    url\n  }\n\n  \n  delegate {\n    id\n    name\n    url\n  }\n\n  \n  team {\n    id\n    key\n    name\n  }\n\n  \n  project {\n    id\n    name\n  }\n\n  \n  labels {\n    nodes {\n      id\n      name\n    }\n  }\n\n  \n  cycle {\n    id\n    name\n    number\n  }\n\n  \n  projectMilestone {\n    id\n    name\n    targetDate\n  }\n\n  \n  parent {\n    id\n    identifier\n    title\n  }\n\n  \n  children {\n    nodes {\n      id\n      identifier\n      title\n    }\n  }\n\n\n        }\n      }\n    }\n  }\n";
 export declare const FIND_PROJECT_MILESTONE_BY_NAME_SCOPED = "\n  query FindProjectMilestoneScoped($name: String!, $projectId: String!) {\n    project(id: $projectId) {\n      projectMilestones(filter: { name: { eq: $name } }, first: 10) {\n        nodes {\n          id\n          name\n          targetDate\n          sortOrder\n          project {\n            id\n            name\n          }\n        }\n      }\n    }\n  }\n";
 export declare const FIND_PROJECT_MILESTONE_BY_NAME_GLOBAL = "\n  query FindProjectMilestoneGlobal($name: String!) {\n    projectMilestones(filter: { name: { eq: $name } }, first: 10) {\n      nodes {\n        id\n        name\n        targetDate\n        sortOrder\n        project {\n          id\n          name\n        }\n      }\n    }\n  }\n";
 export declare const CREATE_PROJECT_MILESTONE_MUTATION = "\n  mutation CreateProjectMilestone($projectId: String!, $name: String!, $description: String, $targetDate: TimelessDate) {\n    projectMilestoneCreate(input: {\n      projectId: $projectId\n      name: $name\n      description: $description\n      targetDate: $targetDate\n    }) {\n      success\n      projectMilestone {\n        id\n        name\n        description\n        targetDate\n        sortOrder\n        createdAt\n        updatedAt\n        project {\n          id\n          name\n        }\n      }\n    }\n  }\n";

package/dist/queries/projects-types.d.ts

@@ -2,12 +2,12 @@
  * Typed response shapes for the queries in `./projects.ts`.
  * See `./issues-types.ts` for the rationale (ALL-937).
  */
-export interface ProjectTeamRef {
+interface ProjectTeamRef {
     id: string;
     key: string;
     name: string;
 }
-export interface ProjectBaseNode {
+interface ProjectBaseNode {
     id: string;
     name: string;
     teams: {
@@ -18,15 +18,15 @@ export interface ProjectBaseNode {
  * Mirrors the project selection set used by `SEARCH_PROJECTS_BY_NAME_QUERY`
  * and `CREATE_PROJECT_MUTATION` — base fields + state.
  */
-export interface ProjectWithStateNode extends ProjectBaseNode {
+interface ProjectWithStateNode extends ProjectBaseNode {
     state: string;
 }
-export interface ProjectIssueRef {
+interface ProjectIssueRef {
     id: string;
     identifier: string;
     title: string;
 }
-export interface ProjectWithIssuesNode extends ProjectBaseNode {
+interface ProjectWithIssuesNode extends ProjectBaseNode {
     issues: {
         nodes: ProjectIssueRef[];
     };
@@ -59,10 +59,10 @@ export interface UpdateProjectResponse {
         project: ProjectBaseNode | null;
     };
 }
-export interface ProjectArchiveEntity {
+interface ProjectArchiveEntity {
     id: string;
 }
-export interface ProjectArchivePayload {
+interface ProjectArchivePayload {
     success: boolean;
     lastSyncId: number;
     entity: ProjectArchiveEntity | null;
@@ -73,3 +73,4 @@ export interface ArchiveProjectResponse {
 export interface DeleteProjectResponse {
     projectDelete: ProjectArchivePayload;
 }
+export {};

package/dist/queries/releases-types.d.ts

@@ -2,17 +2,17 @@
  * Typed response shapes for the queries in `./releases.ts`.
  * See `./issues-types.ts` for the rationale (ALL-937).
  */
-export interface ReleaseStageRef {
+interface ReleaseStageRef {
     id: string;
     name: string;
     type: string;
     color: string | null;
 }
-export interface ReleasePipelineRef {
+interface ReleasePipelineRef {
     id: string;
     name: string;
 }
-export interface ReleaseDocumentRef {
+interface ReleaseDocumentRef {
     id: string;
     title: string;
     slugId: string;
@@ -56,7 +56,7 @@ export interface CreatedReleaseNode {
     createdAt: string;
     updatedAt: string;
 }
-export interface ReleasePipelineNode {
+interface ReleasePipelineNode {
     id: string;
     name: string;
     stages: {
@@ -82,3 +82,4 @@ export interface GetReleasePipelinesResponse {
         nodes: ReleasePipelineNode[];
     };
 }
+export {};

package/dist/queries/search-types.d.ts

@@ -3,11 +3,12 @@
  * templates listing in `commands/search.ts`. See `./issues-types.ts`
  * for the rationale (ALL-937).
  */
-export interface SearchIssueRef {
+import type { LinearPriority } from "../types/linear.js";
+interface SearchIssueRef {
     id: string;
     identifier: string;
     title: string;
-    priority: number | null;
+    priority: LinearPriority | null;
     state: {
         id: string;
         name: string;
@@ -27,17 +28,17 @@ export interface SearchIssueRef {
         name: string;
     } | null;
 }
-export interface SearchProjectRef {
+interface SearchProjectRef {
     id: string;
     name: string;
     state: string;
 }
-export interface SearchInitiativeRef {
+interface SearchInitiativeRef {
     id: string;
     name: string;
     status: string | null;
 }
-export interface SearchDocumentRef {
+interface SearchDocumentRef {
     id: string;
     title: string;
     slugId: string | null;
@@ -47,18 +48,32 @@ export interface SearchDocumentRef {
     } | null;
 }
 /**
- * Mirrors a single semanticSearch result. The discriminator is `type`,
- * but Linear returns *all* sub-objects nullable per row — only the one
- * matching `type` is populated. Modelled as fully-optional sub-objects
- * to match runtime reality.
+ * A single semanticSearch result. Discriminated union on `type` — given
+ * a row, only the field named by `type` is meaningful (the other three
+ * are absent / null on the wire). Consumers `switch (r.type)` and access
+ * the corresponding payload directly; the compiler statically rejects
+ * cross-arm access like `r.project` in a `case "issue"` branch.
+ *
+ * The payload itself is `| null` because Linear can return null when
+ * the underlying entity was deleted between indexing and query time —
+ * that's an orthogonal concern from the discriminant.
+ *
+ * The four `type` literals match Linear's `semanticSearch.results.type`
+ * enum verbatim — keep in lock-step with the GraphQL schema's enum.
  */
-export interface SemanticSearchResult {
-    type: string;
+export type SemanticSearchResult = {
+    type: "issue";
     issue: SearchIssueRef | null;
+} | {
+    type: "project";
     project: SearchProjectRef | null;
+} | {
+    type: "initiative";
     initiative: SearchInitiativeRef | null;
+} | {
+    type: "document";
     document: SearchDocumentRef | null;
-}
+};
 export interface SemanticSearchResponse {
     semanticSearch: {
         results: SemanticSearchResult[];
@@ -84,3 +99,4 @@ export interface SearchTemplateNode {
 export interface SearchTemplatesResponse {
     templates: SearchTemplateNode[];
 }
+export {};

package/dist/queries/templates-types.d.ts

@@ -6,12 +6,12 @@
  * than wrapped in `{ nodes: ... }`. The response type below mirrors
  * what the API actually returns, not the connection convention.
  */
-export interface TemplateTeamRef {
+interface TemplateTeamRef {
     id: string;
     key: string;
     name: string;
 }
-export interface TemplateCreatorRef {
+interface TemplateCreatorRef {
     id: string;
     name: string;
 }
@@ -59,3 +59,4 @@ export interface DeleteTemplateResponse {
         lastSyncId?: number;
     };
 }
+export {};

package/dist/types/linear.d.ts

@@ -3,6 +3,17 @@
  * These represent the public API surface — GraphQL responses are
  * transformed into these shapes at the service boundary.
  */
+/**
+ * Linear priority levels — `0` = no priority, `1` = urgent, `2` = high,
+ * `3` = medium (alias: normal), `4` = low. Sourced from Linear's
+ * `Issue.priority` enum; the GraphQL API returns a number in this range.
+ * Use this instead of `number` at every API boundary so an out-of-range
+ * value (`9`) fails to compile.
+ *
+ * The runtime parser is `validatePriority` in `src/utils/validators.ts`
+ * — it narrows arbitrary `string` input to this union.
+ */
+export type LinearPriority = 0 | 1 | 2 | 3 | 4;
 interface TeamRef {
     id: string;
     key: string;
@@ -87,6 +98,7 @@ export interface LinearIssue {
     comments?: LinearComment[];
     createdAt: string;
     cycle?: CycleRef;
+    delegate?: UserRef;
     description?: string;
     dueDate?: string;
     embeds?: import("../utils/embed-parser.js").Embed[];
@@ -95,7 +107,7 @@ export interface LinearIssue {
     identifier: string;
     labels: LabelRef[];
     parentIssue?: IssueRef;
-    priority: number;
+    priority: LinearPriority;
     project?: ProjectRef;
     projectMilestone?: MilestoneRef;
     state?: StateRef;

package/dist/utils/auto-link-references.d.ts

@@ -1,20 +1,20 @@
 import type { GraphQLService } from "./graphql-service.js";
 import { type IssueRelationType } from "./issue-reference-extractor.js";
 import type { LinearService } from "./linear-service.js";
-export interface AutoLinkLinked {
+interface AutoLinkLinked {
     identifier: string;
     /** True when source/target were swapped on the create (e.g. "blocked by X" → X→source) */
     reverse: boolean;
     title: string;
     type: IssueRelationType;
 }
-export interface AutoLinkSkipped {
+interface AutoLinkSkipped {
     existingType: string;
     identifier: string;
     /** Type that would have been created had the reference been new */
     inferredType: IssueRelationType;
 }
-export interface AutoLinkFailed {
+interface AutoLinkFailed {
     identifier: string;
     reason: string;
 }

package/dist/utils/auto-link-references.js

@@ -1,14 +1,5 @@
 import { GET_ISSUE_RELATIONS_QUERY, ISSUE_RELATION_CREATE_MUTATION, } from "../queries/issues.js";
-import { extractIssueReferences, } from "./issue-reference-extractor.js";
-function specificity(ref) {
-    if (ref.type === "duplicate") {
-        return 3;
-    }
-    if (ref.type === "blocks") {
-        return 2;
-    }
-    return 1;
-}
+import { extractIssueReferences, specificity, } from "./issue-reference-extractor.js";
 /**
  * Merge candidates from multiple sources (description, comments) into one list,
  * keeping the strongest (most-specific) inference per identifier. The first source

package/dist/utils/extract-field.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Extract a named section from a Linear issue's markdown description.
+ *
+ * Linear issue bodies follow a small set of repeated structures —
+ * "Why we need this", "Done when", "Scope", "Out of scope", etc. —
+ * usually as `##` or `###` headers, sometimes as bold pseudo-headers
+ * (`**Done when**`). Agents end up repeatedly piping
+ * `el-linear issues read X | python -c '...desc.find("Done when")...'`
+ * to pull one section out. This helper centralizes that.
+ *
+ * Matching is case-insensitive on the header text. The first matching
+ * header wins. Content is everything between that header and the next
+ * header line (any `#{1,6}` or bold pseudo-header at line start) or EOF,
+ * trimmed of surrounding whitespace.
+ *
+ * Returns `null` when the field isn't found, so callers can distinguish
+ * "missing" from "empty body".
+ */
+export declare function extractField(body: string, fieldName: string): string | null;