@enrichlayer/el-linear 1.9.0 → 1.15.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/queries/attachments-types.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Typed response shapes for the queries in `./attachments.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+/** Mirrors `ATTACHMENT_FRAGMENT` from `src/queries/attachments.ts`. */
+export interface AttachmentNode {
+    id: string;
+    title: string | null;
+    url: string;
+    createdAt: string | null;
+    updatedAt: string | null;
+}
+export interface CreateAttachmentResponse {
+    attachmentCreate: {
+        success: boolean;
+        attachment: AttachmentNode | null;
+    };
+}
+export interface DeleteAttachmentResponse {
+    attachmentDelete: {
+        success: boolean;
+    };
+}
+export interface ListAttachmentsResponse {
+    issue: {
+        attachments: {
+            nodes: AttachmentNode[];
+        };
+    } | null;
+}

package/dist/queries/attachments-types.js

@@ -0,0 +1,5 @@
+/**
+ * Typed response shapes for the queries in `./attachments.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+export {};

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

@@ -0,0 +1,55 @@
+/**
+ * Typed response shapes for the queries in `./comments.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+interface CommentUserRef {
+    id: string;
+    name: string;
+    displayName: string | null;
+    url: string | null;
+}
+/**
+ * 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 CommentResourceNode {
+    id: string;
+    body: string;
+    createdAt: string;
+    updatedAt: string;
+    user: CommentUserRef;
+}
+interface UpdatedCommentResourceNode extends CommentResourceNode {
+    issue: {
+        id: string;
+        identifier: string;
+    } | null;
+}
+export interface ListCommentsResponse {
+    issue: {
+        id: string;
+        identifier: string;
+        comments: {
+            nodes: CommentResourceNode[];
+        };
+    } | null;
+}
+export interface CreateCommentResponse {
+    commentCreate: {
+        success: boolean;
+        comment: CommentResourceNode | null;
+    };
+}
+export interface UpdateCommentResponse {
+    commentUpdate: {
+        success: boolean;
+        comment: UpdatedCommentResourceNode | null;
+    };
+}
+export {};

package/dist/queries/comments-types.js

@@ -0,0 +1,5 @@
+/**
+ * Typed response shapes for the queries in `./comments.ts`.
+ * See `./issues-types.ts` for the rationale (ALL-937).
+ */
+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

@@ -0,0 +1,62 @@
+/**
+ * Typed response shapes for the queries in `./documents.ts`.
+ *
+ * Mirrors `DOCUMENT_FRAGMENT` so the consumer in
+ * `graphql-documents-service.ts` can read fields without recursive
+ * `Record<string, unknown>` casts. See `./issues-types.ts` for the
+ * full rationale and pattern (ALL-937).
+ */
+interface DocumentCreatorRef {
+    id: string;
+    name: string;
+}
+interface DocumentProjectRef {
+    id: string;
+    name: string;
+}
+interface DocumentIssueRef {
+    id: string;
+    identifier: string;
+    title: string;
+}
+/** Mirrors `DOCUMENT_FRAGMENT` from `src/queries/documents.ts`. */
+export interface DocumentNode {
+    id: string;
+    title: string;
+    content: string | null;
+    slugId: string | null;
+    url: string | null;
+    icon: string | null;
+    color: string | null;
+    createdAt: string | null;
+    updatedAt: string | null;
+    creator: DocumentCreatorRef | null;
+    project: DocumentProjectRef | null;
+    issue: DocumentIssueRef | null;
+}
+export interface CreateDocumentResponse {
+    documentCreate: {
+        success: boolean;
+        document: DocumentNode | null;
+    };
+}
+export interface UpdateDocumentResponse {
+    documentUpdate: {
+        success: boolean;
+        document: DocumentNode | null;
+    };
+}
+export interface GetDocumentResponse {
+    document: DocumentNode | null;
+}
+export interface ListDocumentsResponse {
+    documents: {
+        nodes: DocumentNode[];
+    };
+}
+export interface DeleteDocumentResponse {
+    documentDelete: {
+        success: boolean;
+    };
+}
+export {};

package/dist/queries/documents-types.js

@@ -0,0 +1,9 @@
+/**
+ * Typed response shapes for the queries in `./documents.ts`.
+ *
+ * Mirrors `DOCUMENT_FRAGMENT` so the consumer in
+ * `graphql-documents-service.ts` can read fields without recursive
+ * `Record<string, unknown>` casts. See `./issues-types.ts` for the
+ * full rationale and pattern (ALL-937).
+ */
+export {};

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

@@ -0,0 +1,58 @@
+/**
+ * Typed response shapes for `INTROSPECT_TYPE_QUERY` /
+ * `INTROSPECT_ROOT_QUERY`. See `./issues-types.ts` for the
+ * rationale (ALL-937).
+ *
+ * GraphQL introspection types are recursive (a type contains
+ * fields whose types contain fields…). We model the recursion
+ * shallowly — only as deep as the queries actually select.
+ */
+interface IntrospectTypeRefShallow {
+    name: string | null;
+    kind: string;
+    ofType: {
+        name: string | null;
+    } | null;
+}
+interface IntrospectTypeRef {
+    name: string | null;
+    kind: string;
+    ofType: IntrospectTypeRefShallow | null;
+}
+interface IntrospectArg {
+    name: string;
+    type: IntrospectTypeRef;
+}
+interface IntrospectField {
+    name: string;
+    description: string | null;
+    type: IntrospectTypeRef;
+    args: IntrospectArg[];
+}
+interface IntrospectEnumValue {
+    name: string;
+    description: string | null;
+}
+interface IntrospectInputField {
+    name: string;
+    type: IntrospectTypeRef;
+}
+/** Mirrors the inner `__type` shape selected by `INTROSPECT_TYPE_QUERY`. */
+interface IntrospectTypeNode {
+    name: string;
+    kind: string;
+    description: string | null;
+    fields: IntrospectField[] | null;
+    enumValues: IntrospectEnumValue[] | null;
+    inputFields: IntrospectInputField[] | null;
+}
+export interface IntrospectTypeResponse {
+    __type: IntrospectTypeNode | null;
+}
+/** `INTROSPECT_ROOT_QUERY` selects only fields (with args). */
+export interface IntrospectRootResponse {
+    __type: {
+        fields: IntrospectField[];
+    } | null;
+}
+export {};

package/dist/queries/introspect-types.js

@@ -0,0 +1,10 @@
+/**
+ * Typed response shapes for `INTROSPECT_TYPE_QUERY` /
+ * `INTROSPECT_ROOT_QUERY`. See `./issues-types.ts` for the
+ * rationale (ALL-937).
+ *
+ * GraphQL introspection types are recursive (a type contains
+ * fields whose types contain fields…). We model the recursion
+ * shallowly — only as deep as the queries actually select.
+ */
+export {};