@enrichlayer/el-linear 1.10.0 → 1.16.0

package/dist/main.js

@@ -1,4 +1,7 @@
 #!/usr/bin/env node
+import { readFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
 import { program } from "commander";
 import { setupAttachmentsCommands } from "./commands/attachments.js";
 import { setupBatchCommands } from "./commands/batch.js";
@@ -10,6 +13,7 @@ import { setupEmbedsCommands } from "./commands/embeds.js";
 import { setupGdocCommands } from "./commands/gdoc.js";
 import { setupGraphQLCommands } from "./commands/graphql.js";
 import { setupInitCommands } from "./commands/init/index.js";
+import { setupIntrospectCommand } from "./commands/introspect.js";
 import { setupIssueIdCommand } from "./commands/issue-id.js";
 import { setupIssuesCommands } from "./commands/issues.js";
 import { setupLabelsCommands } from "./commands/labels.js";
@@ -27,10 +31,17 @@ import { setActiveProfileForSession } from "./config/paths.js";
 import { setFieldsFilter, setJqFilter, setOutputFormat, setRawMode, } from "./utils/output.js";
 import { outputUsageInfo } from "./utils/usage.js";
 import { splitList } from "./utils/validators.js";
+// Read the version from package.json at startup so `--version` can never
+// drift from the published release (pre-fix: a stale 1.8.1 literal lived
+// here while package.json was at 1.10.0). `dist/main.js` lives one
+// directory below the package root, so `../package.json` resolves
+// correctly in both `pnpm dev` (tsx) and `node dist/main.js` invocations.
+const __dirname_main = dirname(fileURLToPath(import.meta.url));
+const packageJson = JSON.parse(readFileSync(join(__dirname_main, "..", "package.json"), "utf-8"));
 program
     .name("el-linear")
     .description("A pragmatic CLI for Linear.app — deterministic resolution, structured validation, GraphQL escape hatch.")
-    .version("1.8.1")
+    .version(packageJson.version)
     .option("--api-token <token>", "Linear API token")
     .option("--profile <name>", "named profile (under ~/.config/el-linear/profiles/<name>/) for this invocation. Overrides EL_LINEAR_PROFILE env + the on-disk active-profile marker.")
     .option("--json", "output as JSON (default, accepted for compatibility)")
@@ -117,6 +128,7 @@ setupConfigCommands(program);
 setupInitCommands(program);
 setupProfileCommands(program);
 setupRefsCommands(program);
+setupIntrospectCommand(program);
 setupReadShortcut(program);
 program
     .command("usage")

package/dist/output.d.ts

@@ -0,0 +1,82 @@
+/**
+ * Public output utilities — secondary entry point for cross-CLI reuse.
+ *
+ * Other Enrich Layer CLIs (el-slack, el-sheets, el-audit, el-git,
+ * el-elasticsearch — currently in the `tools` monorepo) should depend on
+ * `@enrichlayer/el-linear` and import this module to share the same
+ * `--jq` / `--fields` / `--raw` / `--format summary` behavior and the
+ * canonical `{ data, meta }` envelope shape. DEV-3799.
+ *
+ * Why this exists rather than a separate package: linctl is the OSS
+ * canonical source of these patterns (DEV-3619, DEV-3637, DEV-3798); it
+ * already publishes to npm and ships compiled JS in `dist/`. Treating it
+ * as the host of the shared utilities means there is exactly one
+ * implementation, exactly one set of tests, and exactly one place where
+ * the envelope contract is documented. Tools-repo CLIs pick it up via
+ * `pnpm add @enrichlayer/el-linear` and `import { outputSuccess, ... }
+ * from "@enrichlayer/el-linear/output"`.
+ *
+ * Stable API — semver-tracked. Anything re-exported here MUST stay
+ * backwards-compatible across minor releases. Adding exports is fine;
+ * renaming or removing them is a breaking change.
+ *
+ * # Wiring (consumer recipe)
+ *
+ * Each CLI's `main.ts` registers four global options and a `preAction`
+ * hook to read them into the shared state:
+ *
+ * ```ts
+ * import { Command } from "commander";
+ * import {
+ *   setRawMode, setJqFilter, setFieldsFilter, setOutputFormat,
+ * } from "@enrichlayer/el-linear/output";
+ *
+ * const program = new Command()
+ *   .option("--raw", "strip { data, meta } wrapper from list output")
+ *   .option("--jq <filter>", "apply a jq filter to the JSON output")
+ *   .option("--fields <fields>", "comma-separated field allow-list")
+ *   .option("--format <fmt>", "json | summary", "json");
+ *
+ * program.hook("preAction", (_thisCommand, actionCommand) => {
+ *   const o = actionCommand.optsWithGlobals();
+ *   if (o.raw) setRawMode(true);
+ *   if (o.jq) setJqFilter(o.jq);
+ *   if (o.fields) {
+ *     setFieldsFilter(o.fields.split(",").map((s: string) => s.trim()));
+ *   }
+ *   setOutputFormat(o.format === "summary" ? "summary" : "json");
+ * });
+ * ```
+ *
+ * Then in each subcommand handler emit results via `outputList(data)` /
+ * `outputSingle(data)` / `outputSuccess(payload)`, wrap async actions in
+ * `handleAsyncCommand`, and buffer informational messages via
+ * `outputWarning`. The shared state in this module takes care of `--jq`,
+ * `--fields`, `--raw`, and summary rendering uniformly.
+ *
+ * Adapt the option names and flags to your CLI's existing conventions —
+ * the contract is the four setter calls (`setRawMode`, `setJqFilter`,
+ * `setFieldsFilter`, `setOutputFormat`), not the literal `--jq` /
+ * `--fields` / `--raw` / `--format` names. A CLI that already exposes
+ * `--json` / `--summary` shorthands can keep them as long as the
+ * preAction hook ends up calling the same setters with equivalent values.
+ *
+ * # What is NOT exported
+ *
+ * - `--format summary` dispatch tables are linctl-specific (Linear
+ *   resources). Other CLIs that want summary rendering should either
+ *   ship `--format json` only or register their own per-command summary
+ *   path that does not consume this module's `setOutputFormat("summary")`.
+ * - `outputError` is intentionally internal — it calls `process.exit(1)`
+ *   directly. Consumers funnel errors through `handleAsyncCommand`, which
+ *   in turn calls `outputError`. Don't re-export the bare function; the
+ *   wrapper is the contract.
+ * - Token-sanitization (`sanitizeForLog`) is internal to the error path.
+ *   Consumers that route errors through `handleAsyncCommand` automatically
+ *   get token redaction on the error path — no separate redactor needed
+ *   for that case. If a consumer wants sanitization for something OTHER
+ *   than thrown errors (e.g. a custom debug log), it should pull a small
+ *   redactor of its own; coupling token redaction to the output layer
+ *   would make this API surface stickier than it needs to be.
+ */
+export { type CliListEnvelope, getOutputFormat, handleAsyncCommand, type ListExtraMeta, type ListMeta, outputList, outputSingle, outputSuccess, outputWarning, resetWarnings, setFieldsFilter, setJqFilter, setOutputFormat, setRawMode, warnIfTruncated, } from "./utils/output.js";

package/dist/output.js

@@ -0,0 +1,82 @@
+/**
+ * Public output utilities — secondary entry point for cross-CLI reuse.
+ *
+ * Other Enrich Layer CLIs (el-slack, el-sheets, el-audit, el-git,
+ * el-elasticsearch — currently in the `tools` monorepo) should depend on
+ * `@enrichlayer/el-linear` and import this module to share the same
+ * `--jq` / `--fields` / `--raw` / `--format summary` behavior and the
+ * canonical `{ data, meta }` envelope shape. DEV-3799.
+ *
+ * Why this exists rather than a separate package: linctl is the OSS
+ * canonical source of these patterns (DEV-3619, DEV-3637, DEV-3798); it
+ * already publishes to npm and ships compiled JS in `dist/`. Treating it
+ * as the host of the shared utilities means there is exactly one
+ * implementation, exactly one set of tests, and exactly one place where
+ * the envelope contract is documented. Tools-repo CLIs pick it up via
+ * `pnpm add @enrichlayer/el-linear` and `import { outputSuccess, ... }
+ * from "@enrichlayer/el-linear/output"`.
+ *
+ * Stable API — semver-tracked. Anything re-exported here MUST stay
+ * backwards-compatible across minor releases. Adding exports is fine;
+ * renaming or removing them is a breaking change.
+ *
+ * # Wiring (consumer recipe)
+ *
+ * Each CLI's `main.ts` registers four global options and a `preAction`
+ * hook to read them into the shared state:
+ *
+ * ```ts
+ * import { Command } from "commander";
+ * import {
+ *   setRawMode, setJqFilter, setFieldsFilter, setOutputFormat,
+ * } from "@enrichlayer/el-linear/output";
+ *
+ * const program = new Command()
+ *   .option("--raw", "strip { data, meta } wrapper from list output")
+ *   .option("--jq <filter>", "apply a jq filter to the JSON output")
+ *   .option("--fields <fields>", "comma-separated field allow-list")
+ *   .option("--format <fmt>", "json | summary", "json");
+ *
+ * program.hook("preAction", (_thisCommand, actionCommand) => {
+ *   const o = actionCommand.optsWithGlobals();
+ *   if (o.raw) setRawMode(true);
+ *   if (o.jq) setJqFilter(o.jq);
+ *   if (o.fields) {
+ *     setFieldsFilter(o.fields.split(",").map((s: string) => s.trim()));
+ *   }
+ *   setOutputFormat(o.format === "summary" ? "summary" : "json");
+ * });
+ * ```
+ *
+ * Then in each subcommand handler emit results via `outputList(data)` /
+ * `outputSingle(data)` / `outputSuccess(payload)`, wrap async actions in
+ * `handleAsyncCommand`, and buffer informational messages via
+ * `outputWarning`. The shared state in this module takes care of `--jq`,
+ * `--fields`, `--raw`, and summary rendering uniformly.
+ *
+ * Adapt the option names and flags to your CLI's existing conventions —
+ * the contract is the four setter calls (`setRawMode`, `setJqFilter`,
+ * `setFieldsFilter`, `setOutputFormat`), not the literal `--jq` /
+ * `--fields` / `--raw` / `--format` names. A CLI that already exposes
+ * `--json` / `--summary` shorthands can keep them as long as the
+ * preAction hook ends up calling the same setters with equivalent values.
+ *
+ * # What is NOT exported
+ *
+ * - `--format summary` dispatch tables are linctl-specific (Linear
+ *   resources). Other CLIs that want summary rendering should either
+ *   ship `--format json` only or register their own per-command summary
+ *   path that does not consume this module's `setOutputFormat("summary")`.
+ * - `outputError` is intentionally internal — it calls `process.exit(1)`
+ *   directly. Consumers funnel errors through `handleAsyncCommand`, which
+ *   in turn calls `outputError`. Don't re-export the bare function; the
+ *   wrapper is the contract.
+ * - Token-sanitization (`sanitizeForLog`) is internal to the error path.
+ *   Consumers that route errors through `handleAsyncCommand` automatically
+ *   get token redaction on the error path — no separate redactor needed
+ *   for that case. If a consumer wants sanitization for something OTHER
+ *   than thrown errors (e.g. a custom debug log), it should pull a small
+ *   redactor of its own; coupling token redaction to the output layer
+ *   would make this API surface stickier than it needs to be.
+ */
+export { getOutputFormat, handleAsyncCommand, outputList, outputSingle, outputSuccess, outputWarning, resetWarnings, setFieldsFilter, setJqFilter, setOutputFormat, setRawMode, warnIfTruncated, } from "./utils/output.js";

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

@@ -2,25 +2,30 @@
  * Typed response shapes for the queries in `./comments.ts`.
  * See `./issues-types.ts` for the rationale (ALL-937).
  */
-export interface CommentUserRef {
+interface CommentUserRef {
     id: string;
     name: string;
     displayName: string | null;
     url: string | null;
 }
 /**
- * Mirrors the comment selection set used by `LIST_COMMENTS_QUERY`,
- * `CREATE_COMMENT_MUTATION`, and (with `issue` overlay)
- * `UPDATE_COMMENT_MUTATION`.
+ * Comment shape returned by the standalone comment queries:
+ * `LIST_COMMENTS_QUERY`, `CREATE_COMMENT_MUTATION`, and (with `issue`
+ * overlay) `UPDATE_COMMENT_MUTATION`. Distinct from
+ * `issues-types.ts:IssueCommentNode`, which is the embedded-in-issue
+ * shape — that one allows `user: null`, this one does not (a standalone
+ * comment without an author isn't a valid Linear state). The two were
+ * a single `CommentNode` interface pre-DEV-4068 T2, but with incompatible
+ * `user` shapes — renamed to disambiguate the per-context contract.
  */
-export interface CommentNode {
+export interface CommentResourceNode {
     id: string;
     body: string;
     createdAt: string;
     updatedAt: string;
     user: CommentUserRef;
 }
-export interface UpdatedCommentNode extends CommentNode {
+interface UpdatedCommentResourceNode extends CommentResourceNode {
     issue: {
         id: string;
         identifier: string;
@@ -31,19 +36,20 @@ export interface ListCommentsResponse {
         id: string;
         identifier: string;
         comments: {
-            nodes: CommentNode[];
+            nodes: CommentResourceNode[];
         };
     } | null;
 }
 export interface CreateCommentResponse {
     commentCreate: {
         success: boolean;
-        comment: CommentNode | null;
+        comment: CommentResourceNode | null;
     };
 }
 export interface UpdateCommentResponse {
     commentUpdate: {
         success: boolean;
-        comment: UpdatedCommentNode | null;
+        comment: UpdatedCommentResourceNode | null;
     };
 }
+export {};

package/dist/queries/common.d.ts

@@ -1,2 +1,2 @@
-export declare const COMPLETE_ISSUE_FRAGMENT = "\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";
-export declare const COMPLETE_ISSUE_WITH_COMMENTS_FRAGMENT = "\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  comments {\n    nodes {\n      id\n      body\n      createdAt\n      updatedAt\n      user {\n        id\n        name\n        url\n      }\n    }\n  }\n\n";
+export declare const COMPLETE_ISSUE_FRAGMENT = "\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";
+export declare const COMPLETE_ISSUE_WITH_COMMENTS_FRAGMENT = "\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  comments {\n    nodes {\n      id\n      body\n      createdAt\n      updatedAt\n      user {\n        id\n        name\n        url\n      }\n    }\n  }\n\n";

package/dist/queries/common.js

@@ -25,6 +25,13 @@ const ISSUE_ASSIGNEE_FRAGMENT = `
     url
   }
 `;
+const ISSUE_DELEGATE_FRAGMENT = `
+  delegate {
+    id
+    name
+    url
+  }
+`;
 const ISSUE_TEAM_FRAGMENT = `
   team {
     id
@@ -95,6 +102,7 @@ export const COMPLETE_ISSUE_FRAGMENT = `
   ${ISSUE_CORE_FIELDS}
   ${ISSUE_STATE_FRAGMENT}
   ${ISSUE_ASSIGNEE_FRAGMENT}
+  ${ISSUE_DELEGATE_FRAGMENT}
   ${ISSUE_TEAM_FRAGMENT}
   ${ISSUE_PROJECT_FRAGMENT}
   ${ISSUE_LABELS_FRAGMENT}

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

@@ -6,15 +6,15 @@
  * `Record<string, unknown>` casts. See `./issues-types.ts` for the
  * full rationale and pattern (ALL-937).
  */
-export interface DocumentCreatorRef {
+interface DocumentCreatorRef {
     id: string;
     name: string;
 }
-export interface DocumentProjectRef {
+interface DocumentProjectRef {
     id: string;
     name: string;
 }
-export interface DocumentIssueRef {
+interface DocumentIssueRef {
     id: string;
     identifier: string;
     title: string;
@@ -59,3 +59,4 @@ export interface DeleteDocumentResponse {
         success: boolean;
     };
 }
+export {};

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

@@ -7,38 +7,38 @@
  * fields whose types contain fields…). We model the recursion
  * shallowly — only as deep as the queries actually select.
  */
-export interface IntrospectTypeRefShallow {
+interface IntrospectTypeRefShallow {
     name: string | null;
     kind: string;
     ofType: {
         name: string | null;
     } | null;
 }
-export interface IntrospectTypeRef {
+interface IntrospectTypeRef {
     name: string | null;
     kind: string;
     ofType: IntrospectTypeRefShallow | null;
 }
-export interface IntrospectArg {
+interface IntrospectArg {
     name: string;
     type: IntrospectTypeRef;
 }
-export interface IntrospectField {
+interface IntrospectField {
     name: string;
     description: string | null;
     type: IntrospectTypeRef;
     args: IntrospectArg[];
 }
-export interface IntrospectEnumValue {
+interface IntrospectEnumValue {
     name: string;
     description: string | null;
 }
-export interface IntrospectInputField {
+interface IntrospectInputField {
     name: string;
     type: IntrospectTypeRef;
 }
 /** Mirrors the inner `__type` shape selected by `INTROSPECT_TYPE_QUERY`. */
-export interface IntrospectTypeNode {
+interface IntrospectTypeNode {
     name: string;
     kind: string;
     description: string | null;
@@ -55,3 +55,4 @@ export interface IntrospectRootResponse {
         fields: IntrospectField[];
     } | null;
 }
+export {};

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

@@ -20,46 +20,66 @@
  *
  * Refs ALL-937.
  */
+import type { LinearPriority } from "../types/linear.js";
 /** A reference to a related entity — id + display fields. */
-export interface IdNameRef {
+interface IdNameRef {
     id: string;
     name: string;
 }
-export interface IdKeyNameRef {
+interface IdKeyNameRef {
     id: string;
     key: string;
     name: string;
 }
-export interface IdIdentifierTitleRef {
+interface IdIdentifierTitleRef {
     id: string;
     identifier: string;
     title: string;
 }
-export interface AssigneeNode {
+interface AssigneeNode {
     id: string;
     name: string;
     url?: string;
 }
-export interface CommentNode {
+/**
+ * Comment shape as embedded inside `COMPLETE_ISSUE_WITH_COMMENTS_FRAGMENT`
+ * (i.e. comments fetched as part of an issue query). Distinct from
+ * `comments-types.ts:CommentResourceNode`, which is the shape returned by
+ * the standalone comment queries (`LIST_COMMENTS_QUERY`,
+ * `CREATE_COMMENT_MUTATION`, `UPDATE_COMMENT_MUTATION`). The two have
+ * incompatible `user` shapes — this one allows `null` and uses the
+ * issue-page \"assignee\"-style fields, while the standalone resource
+ * shape always populates `user` and includes the comment-author-only
+ * `CommentUserRef` fields (DEV-4068 T2).
+ */
+export interface IssueCommentNode {
     id: string;
     body: string;
     createdAt: string;
     updatedAt: string;
     user: AssigneeNode | null;
 }
-export interface CycleNode {
+interface CycleNode {
     id: string;
     name: string | null;
     number: number;
 }
-export interface ProjectMilestoneNode {
+interface ProjectMilestoneNode {
     id: string;
     name: string;
     targetDate: string | null;
 }
-export interface IssueSummary {
+/**
+ * Linear's documented generation states for issue summaries. If Linear
+ * adds a new state in the future the runtime API would deserialize the
+ * new string verbatim — TypeScript wouldn't catch the divergence, but
+ * the typical `=== "completed"` check keeps working safely. Widen the
+ * union here when Linear documents a new state.
+ */
+type IssueSummaryGenerationStatus = "completed" | "pending" | "failed";
+interface IssueSummary {
     content: unknown;
-    generationStatus: "completed" | "pending" | "failed" | string;
+    generationStatus: IssueSummaryGenerationStatus;
 }
 /**
  * Mirrors `COMPLETE_ISSUE_FRAGMENT` from `src/queries/common.ts`.
@@ -74,7 +94,7 @@ export interface IssueNode {
     description: string | null;
     summary: IssueSummary | null;
     branchName: string;
-    priority: number;
+    priority: LinearPriority;
     estimate: number | null;
     dueDate: string | null;
     url: string;
@@ -82,6 +102,7 @@ export interface IssueNode {
     updatedAt: string;
     state: IdNameRef | null;
     assignee: AssigneeNode | null;
+    delegate: AssigneeNode | null;
     team: IdKeyNameRef | null;
     project: IdNameRef | null;
     labels: {
@@ -100,7 +121,7 @@ export interface IssueNode {
  */
 export interface IssueWithCommentsNode extends IssueNode {
     comments: {
-        nodes: CommentNode[];
+        nodes: IssueCommentNode[];
     };
 }
 /** Response shape for `GET_ISSUE_BY_ID_QUERY`. */
@@ -125,12 +146,6 @@ export interface SearchIssuesResponse {
         nodes: IssueNode[];
     };
 }
-/**
- * Response shape for `FILTERED_SEARCH_ISSUES_QUERY`. Same shape as
- * `GetIssuesResponse` (both return `issues.nodes`) but kept as a
- * named alias so the call site documents intent.
- */
-export type FilteredSearchIssuesResponse = GetIssuesResponse;
 /** Response shape for `CREATE_ISSUE_MUTATION`. */
 export interface CreateIssueResponse {
     issueCreate: {
@@ -148,7 +163,7 @@ export interface UpdateIssueResponse {
 export interface IssueArchiveEntity {
     id: string;
 }
-export interface IssueArchivePayload {
+interface IssueArchivePayload {
     success: boolean;
     lastSyncId: number;
     entity: IssueArchiveEntity | null;
@@ -169,6 +184,35 @@ export interface GetIssueTeamResponse {
         } | null;
     } | null;
 }
+type WorkflowStateType = "triage" | "backlog" | "unstarted" | "started" | "completed" | "canceled";
+export interface IssueStartContextResponse {
+    issue: {
+        id: string;
+        identifier: string;
+        state: {
+            id: string;
+            name: string;
+            type: WorkflowStateType;
+        } | null;
+        team: {
+            id: string;
+            key: string;
+            name: string;
+        } | null;
+        delegate: AssigneeNode | null;
+    } | null;
+}
+export interface TeamStartedStatusesResponse {
+    team: {
+        states: {
+            nodes: {
+                id: string;
+                name: string;
+                position: number;
+            }[];
+        };
+    } | null;
+}
 /**
  * Issue summary returned by `GET_ISSUE_RELATIONS_QUERY` on the
  * `relatedIssue` / `issue` peer of each relation. Smaller than
@@ -182,7 +226,7 @@ export interface RelationPeerNode {
         id: string;
         name: string;
     } | null;
-    priority: number | null;
+    priority: LinearPriority | null;
     assignee: {
         id: string;
         name: string;
@@ -207,7 +251,7 @@ export interface BatchResolveProjectMilestoneRef {
     id: string;
     name: string;
 }
-export interface BatchResolveProjectNode {
+interface BatchResolveProjectNode {
     id: string;
     name: string;
     /** Present on `BATCH_RESOLVE_FOR_CREATE_QUERY`. */
@@ -230,7 +274,7 @@ export interface BatchResolveLabelNode {
         id: string;
     } | null;
 }
-export interface BatchResolveIssueForUpdate {
+interface BatchResolveIssueForUpdate {
     id: string;
     identifier: string;
     team: {
@@ -258,10 +302,13 @@ export interface BatchResolveForCreateResponse {
             name: string;
         }[];
     };
-    projects: {
+    projectsByName?: {
+        nodes: BatchResolveProjectNode[];
+    };
+    projectsById?: {
         nodes: BatchResolveProjectNode[];
     };
-    milestones: {
+    milestones?: {
         nodes: BatchResolveProjectMilestoneRef[];
     };
     parentIssues: {
@@ -272,6 +319,13 @@ export interface BatchResolveForCreateResponse {
     };
 }
 export interface BatchResolveForSearchResponse {
+    delegates?: {
+        nodes: {
+            id: string;
+            name: string;
+            email: string;
+        }[];
+    };
     teams: {
         nodes: {
             id: string;
@@ -279,7 +333,7 @@ export interface BatchResolveForSearchResponse {
             name: string;
         }[];
     };
-    projects: {
+    projects?: {
         nodes: BatchResolveProjectNode[];
     };
     users: {
@@ -291,10 +345,13 @@ export interface BatchResolveForSearchResponse {
     };
 }
 export interface BatchResolveForUpdateResponse {
-    projects: {
+    projectsByName?: {
+        nodes: BatchResolveProjectNode[];
+    };
+    projectsById?: {
         nodes: BatchResolveProjectNode[];
     };
-    milestones: {
+    milestones?: {
         nodes: BatchResolveProjectMilestoneRef[];
     };
     issues: {
@@ -338,6 +395,13 @@ export interface BatchResolveResult {
             email: string;
         }[];
     };
+    delegates?: {
+        nodes: {
+            id: string;
+            name: string;
+            email: string;
+        }[];
+    };
     issues?: {
         nodes: BatchResolveIssueForUpdate[];
     };
@@ -394,7 +458,7 @@ export interface ScanIssuesResponse {
         }[];
     };
 }
-export interface IssueStateSpanNode {
+interface IssueStateSpanNode {
     state: {
         id: string;
         name: string;
@@ -414,3 +478,4 @@ export interface GetIssueStateHistoryResponse {
         };
     } | null;
 }
+export {};