@enrichlayer/el-linear 1.37.0 → 1.37.2

package/dist/commands/profile.js

@@ -23,9 +23,10 @@
 import { promises as fsp } from "node:fs";
 import path from "node:path";
 import { confirm } from "@inquirer/prompts";
-import { ACTIVE_PROFILE_FILE, CONFIG_DIR, CONFIG_PATH, isSafeProfileName as isSafeName, PROFILES_DIR, profilePaths, resolveActiveProfile, setActiveProfileForSession, TOKEN_PATH, } from "../config/paths.js";
+import { ACTIVE_PROFILE_FILE, CONFIG_DIR, CONFIG_PATH, isSafeProfileName as isSafeName, PROFILES_DIR, profilePaths, readActiveProfileMarker, resolveActiveProfile, setActiveProfileForSession, TOKEN_PATH, } from "../config/paths.js";
 import { outputSuccess, outputWarning } from "../utils/output.js";
 import { runFullWizard } from "./init/index.js";
+import { registerMembersCommands } from "./profile/members.js";
 import { registerMigrateLegacy } from "./profile/migrate-legacy.js";
 export function setupProfileCommands(program) {
     const profile = program
@@ -79,6 +80,9 @@ export function setupProfileCommands(program) {
     // self-contained and unit-testable without dragging in the full
     // profile-management surface.
     registerMigrateLegacy(profile);
+    // `el-linear profile members {list,clear,set}` — DEV-5612: direct,
+    // non-interactive alias/handle edits without hand-editing config.json.
+    registerMembersCommands(profile);
 }
 export async function runProfileList() {
     const active = resolveActiveProfile();
@@ -120,8 +124,27 @@ export async function runProfileUse(name) {
     if (!isSafeName(trimmed)) {
         throw new Error(`Profile name "${trimmed}" must contain only [a-z0-9_-]. Pick a different name.`);
     }
+    // DEV-5610: `active-profile` is a single, machine-global marker — every
+    // el-linear invocation anywhere on this machine that doesn't set
+    // --profile/$EL_LINEAR_PROFILE resolves through it. Warn loudly on an
+    // actual switch so the blast radius is visible instead of silently
+    // redirecting some other concurrent session/tool to a different
+    // workspace. `--profile`/$EL_LINEAR_PROFILE remain the correct,
+    // non-mutating choice for automation and concurrent sessions.
+    //
+    // Read the raw marker (readActiveProfileMarker), not
+    // resolveActiveProfile().name — the latter resolves through the
+    // --profile/$EL_LINEAR_PROFILE precedence layers too, so a concurrent
+    // override in place while `profile use` runs would make it report the
+    // wrong "previous" value (a false-positive warning when the marker
+    // didn't actually change, or a false-negative when it did) — cycle-1
+    // review finding on PR #229.
+    const previous = readActiveProfileMarker();
     await fsp.mkdir(CONFIG_DIR, { recursive: true, mode: 0o700 });
     await fsp.writeFile(ACTIVE_PROFILE_FILE, `${trimmed}\n`, { mode: 0o644 });
+    if (previous !== trimmed) {
+        outputWarning(`Switched the GLOBAL active profile to "${trimmed}" (${ACTIVE_PROFILE_FILE}). This affects every other el-linear invocation on this machine that doesn't set --profile/$EL_LINEAR_PROFILE explicitly — concurrent sessions/tools relying on a different profile will silently start hitting the wrong workspace.`);
+    }
 }
 export async function runProfileAdd(name) {
     const trimmed = name.trim();

package/dist/commands/projects.js

@@ -6,7 +6,7 @@ import { createGraphQLService } from "../utils/graphql-service.js";
 import { createLinearService } from "../utils/linear-service.js";
 import { logger } from "../utils/logger.js";
 import { handleAsyncCommand, outputSuccess, outputWarning, } from "../utils/output.js";
-import { getRootOpts } from "../utils/root-opts.js";
+import { effectiveOption, getRootOpts } from "../utils/root-opts.js";
 import { renderCsv, renderFixedWidthTable, renderMarkdownTable, } from "../utils/table-formatter.js";
 import { isUuid } from "../utils/uuid.js";
 import { parsePositiveInt, splitList } from "../utils/validators.js";
@@ -516,7 +516,11 @@ export function setupProjectsCommands(program) {
         // ahead of completed/canceled in every format, so the active
         // set always fits within `--limit`. DEV-4175.
         const sorted = sortActiveFirst(result);
-        const format = options.format;
+        // Resolved via effectiveOption because commander 15 hands the
+        // CLI token to the root program's same-named --format/--fields
+        // registration, leaving the subcommand's option at its default
+        // (DEV-5376).
+        const format = effectiveOption(command, "format") ?? "json";
         const isTabular = format === "table" ||
             format === "md" ||
             format === "markdown" ||
@@ -530,9 +534,8 @@ export function setupProjectsCommands(program) {
             warnProjectsTruncated(sorted.length, limit, format);
         }
         if (isTabular) {
-            const fieldList = options.fields
-                ? splitList(options.fields)
-                : undefined;
+            const fields = effectiveOption(command, "fields");
+            const fieldList = fields ? splitList(fields) : undefined;
             formatProjectsOutput(sorted, format, fieldList);
             if (format === "table") {
                 logger.info(`\n${sorted.length} projects`);

package/dist/commands/users.js

@@ -5,6 +5,15 @@ import { parsePositiveInt } from "../utils/validators.js";
 export function setupUsersCommands(program) {
     const users = program.command("users").description("User operations");
     users.action(() => users.help());
+    users
+        .command("read <id>")
+        .description("Look up a single user by UUID, email, or name (resolves ambiguity the same way as other --assignee-style lookups).")
+        .action(handleAsyncCommand(async (id, _options, command) => {
+        const rootOpts = getRootOpts(command);
+        const service = await createLinearService(rootOpts);
+        const result = await service.getUser(id);
+        outputSuccess({ data: result });
+    }));
     users
         .command("list")
         .description("List all users")

package/dist/config/config.d.ts

@@ -69,6 +69,17 @@ export interface ElLinearConfig {
          * `DEFAULT_DUPLICATE_THRESHOLD` (0.35). Lower = more aggressive.
          */
         duplicateThreshold?: number;
+        /**
+         * Jaccard title-similarity threshold (0-1) above which a duplicate
+         * candidate HARD blocks creation (throws, requires `--allow-duplicate`).
+         * A candidate scoring at/above `duplicateThreshold` but below this is
+         * advisory only — printed, creation proceeds. Defaults to
+         * `DEFAULT_HARD_BLOCK_THRESHOLD` (0.6). See DEV-5590 for why the gate
+         * is two-tier: single-threshold override-rate telemetry showed score
+         * alone doesn't separate genuine duplicates from legitimate distinct
+         * issues in the 0.35-0.6 range.
+         */
+        duplicateHardBlockThreshold?: number;
         /**
          * OPT-IN SOP-label parent gate (DEV-5378). When `true`, `issues create`
          * requires an issue carrying an SOP-type label (see `sopLabels`) to point

package/dist/config/paths.d.ts

@@ -51,3 +51,12 @@ export declare function getSessionProfileOverride(): string | null;
 export declare function resolveActiveProfile(env?: NodeJS.ProcessEnv, fsImpl?: ProfileFsOps): ProfilePaths;
 /** Build profile-relative paths for a named profile. Pure. */
 export declare function profilePaths(name: string): ProfilePaths;
+/**
+ * Read the raw on-disk marker content, bypassing the `--profile`/
+ * `EL_LINEAR_PROFILE` precedence layers `resolveActiveProfile` applies.
+ * Exported (DEV-5610) so `profile use` can detect whether *the file itself*
+ * is about to change, independent of any per-invocation override that might
+ * otherwise make `resolveActiveProfile().name` report a different "previous"
+ * value than what's actually on disk.
+ */
+export declare function readActiveProfileMarker(fsImpl?: ProfileFsOps): string | null;

package/dist/config/paths.js

@@ -127,7 +127,15 @@ export function profilePaths(name) {
         tokenPath: path.join(dir, "token"),
     };
 }
-function readActiveProfileMarker(fsImpl) {
+/**
+ * Read the raw on-disk marker content, bypassing the `--profile`/
+ * `EL_LINEAR_PROFILE` precedence layers `resolveActiveProfile` applies.
+ * Exported (DEV-5610) so `profile use` can detect whether *the file itself*
+ * is about to change, independent of any per-invocation override that might
+ * otherwise make `resolveActiveProfile().name` report a different "previous"
+ * value than what's actually on disk.
+ */
+export function readActiveProfileMarker(fsImpl = DEFAULT_FS_OPS) {
     if (!fsImpl.existsSync(ACTIVE_PROFILE_FILE))
         return null;
     try {

package/dist/main.js

@@ -70,7 +70,9 @@ program
     "Warnings (e.g. --fields fields_unresolved) can't ride on a bare array, so " +
     "they are written to stderr prefixed `_warnings: `, keeping stdout a pure JSON array")
     .option("--jq <filter>", "apply a jq filter to the JSON output")
-    .option("--fields <fields>", "filter output to specific fields (comma-separated). Unresolved fields are " +
+    .option("--fields <fields>", "filter output to specific fields (comma-separated). Dot-paths resolve nested " +
+    "values; the column aliases status (state.name) and updated (updatedAt) " +
+    "resolve too. Unresolved fields are " +
     "emitted as null plus a `fields_unresolved:` warning — in the JSON " +
     "envelope's `_warnings`, or on stderr when output is a bare array (with --raw)")
     .option("--no-cache", "bypass the on-disk cache for `teams list` / `labels list` / `projects list`");

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

@@ -153,6 +153,17 @@ export interface GetIssuesResponse {
         nodes: IssueNode[];
     };
 }
+/**
+ * Response shape for `TEAM_SCOPED_FILTERED_ISSUES_QUERY` (DEV-5578).
+ * `team` is null when the resolved team UUID does not exist.
+ */
+export interface TeamScopedFilteredIssuesResponse {
+    team: {
+        issues: {
+            nodes: IssueNode[];
+        };
+    } | null;
+}
 /** Response shape for `SEARCH_ISSUES_QUERY` (full-text). */
 export interface SearchIssuesResponse {
     searchIssues: {

package/dist/queries/issues.d.ts

@@ -1,6 +1,25 @@
 export declare const GET_ISSUES_QUERY = "\n  query GetIssues($first: Int!, $orderBy: PaginationOrderBy) {\n    issues(\n      first: $first\n      orderBy: $orderBy\n      filter: {\n        state: { type: { neq: \"completed\" } }\n      }\n    ) {\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  completedAt\n\n  \n  state {\n    id\n    name\n    type\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";
 export declare const SEARCH_ISSUES_QUERY = "\n  query SearchIssues($term: String!, $first: Int!) {\n    searchIssues(term: $term, first: $first, includeArchived: false) {\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  completedAt\n\n  \n  state {\n    id\n    name\n    type\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";
 export declare const FILTERED_SEARCH_ISSUES_QUERY = "\n  query FilteredSearchIssues(\n    $first: Int!\n    $filter: IssueFilter\n    $orderBy: PaginationOrderBy\n  ) {\n    issues(\n      first: $first\n      filter: $filter\n      orderBy: $orderBy\n      includeArchived: false\n    ) {\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  completedAt\n\n  \n  state {\n    id\n    name\n    type\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";
+/**
+ * Team-scoped variant of `FILTERED_SEARCH_ISSUES_QUERY` (DEV-5578).
+ *
+ * When a `--team` filter is present, the team boundary is applied
+ * *structurally* — the `issues` connection is rooted at the `Team` node
+ * (`team(id: $teamId).issues(...)`) rather than passed as a top-level
+ * `issues(filter: { team: { id: { eq } } })` relation filter.
+ *
+ * The top-level relation-filter form is unreliable at scale: Linear's API
+ * silently leaks issues from *other* teams once `$first` grows past a small
+ * page (~20), so `issues list --team DEV --limit 100` returned issues from
+ * EMW/INF/FE too. This is the same class of bug DEV-5325 fixed for
+ * `projects list --team` (`ProjectFilter` had no working `teams` relation, so
+ * project scoping moved to `Team.projects`). Rooting at the team node keeps
+ * the team boundary server-side and exact. The remaining `$filter`
+ * (state / labels / assignee / priority / project) is applied on top of the
+ * already-team-scoped connection.
+ */
+export declare const TEAM_SCOPED_FILTERED_ISSUES_QUERY = "\n  query TeamScopedFilteredIssues(\n    $teamId: String!\n    $first: Int!\n    $filter: IssueFilter\n    $orderBy: PaginationOrderBy\n  ) {\n    team(id: $teamId) {\n      issues(\n        first: $first\n        filter: $filter\n        orderBy: $orderBy\n        includeArchived: false\n      ) {\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  completedAt\n\n  \n  state {\n    id\n    name\n    type\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";
 /**
  * Batch-resolves a search's team/project/assignee/delegate filter inputs.
  *

package/dist/queries/issues.js

@@ -41,6 +41,45 @@ export const FILTERED_SEARCH_ISSUES_QUERY = `
     }
   }
 `;
+/**
+ * Team-scoped variant of `FILTERED_SEARCH_ISSUES_QUERY` (DEV-5578).
+ *
+ * When a `--team` filter is present, the team boundary is applied
+ * *structurally* — the `issues` connection is rooted at the `Team` node
+ * (`team(id: $teamId).issues(...)`) rather than passed as a top-level
+ * `issues(filter: { team: { id: { eq } } })` relation filter.
+ *
+ * The top-level relation-filter form is unreliable at scale: Linear's API
+ * silently leaks issues from *other* teams once `$first` grows past a small
+ * page (~20), so `issues list --team DEV --limit 100` returned issues from
+ * EMW/INF/FE too. This is the same class of bug DEV-5325 fixed for
+ * `projects list --team` (`ProjectFilter` had no working `teams` relation, so
+ * project scoping moved to `Team.projects`). Rooting at the team node keeps
+ * the team boundary server-side and exact. The remaining `$filter`
+ * (state / labels / assignee / priority / project) is applied on top of the
+ * already-team-scoped connection.
+ */
+export const TEAM_SCOPED_FILTERED_ISSUES_QUERY = `
+  query TeamScopedFilteredIssues(
+    $teamId: String!
+    $first: Int!
+    $filter: IssueFilter
+    $orderBy: PaginationOrderBy
+  ) {
+    team(id: $teamId) {
+      issues(
+        first: $first
+        filter: $filter
+        orderBy: $orderBy
+        includeArchived: false
+      ) {
+        nodes {
+          ${COMPLETE_ISSUE_FRAGMENT}
+        }
+      }
+    }
+  }
+`;
 /**
  * Batch-resolves a search's team/project/assignee/delegate filter inputs.
  *

package/dist/utils/duplicate-detection.d.ts

@@ -32,6 +32,44 @@ import type { LinearIssue } from "../types/linear.js";
  * Overridable via `config.validation.duplicateThreshold`.
  */
 export declare const DEFAULT_DUPLICATE_THRESHOLD = 0.35;
+/**
+ * Threshold above which a candidate is a HARD block (creation refuses without
+ * `--allow-duplicate`). Below this (but at/above {@link DEFAULT_DUPLICATE_THRESHOLD})
+ * a candidate is ADVISORY ONLY — printed, but creation proceeds — DEV-5590.
+ *
+ * Why a second threshold instead of just retuning the first: `el-telemetry
+ * gates` measured a 52.2% override rate on the single-threshold (0.35) gate
+ * over 144 real fires. Analyzing the real ledger (`top_score` + `outcome` per
+ * fire, no title text is ever recorded — el-linear collects nothing by
+ * default) falsifies the obvious fix of "just raise the threshold": mean/
+ * median `top_score` for `blocked` fires (0.414 / 0.40) and `overridden`
+ * fires (0.421 / 0.40) are statistically indistinguishable, and simulating
+ * every cutoff from 0.35 to 0.56 against the real corpus held the override
+ * rate flat at 52–63% — *increasing* at some higher cutoffs. Score alone does
+ * not separate genuine duplicates from legitimate distinct issues in this
+ * workspace's real usage; no single threshold in the observed range is
+ * better than a coin flip.
+ *
+ * Given that, blocking hard on a weak signal is worse than not blocking at
+ * all: over half the stops were wrong. 0.6 sits above the entire analyzed
+ * range (only 1/144 historical fires scored this high) and is reserved for
+ * near-verbatim title overlap — at Jaccard >= 0.6, more than 6 of every 10
+ * combined salient tokens are shared, which is a qualitatively different
+ * (and much rarer) signal than the "shares a few topical words" fires that
+ * dominate the false-positive population. This preserves a real backstop for
+ * the obvious copy-paste case while no longer forcing a stop-and-override
+ * ritual on the ambiguous 0.35-0.6 band, where the data shows we're wrong
+ * about as often as we're right.
+ *
+ * Caveat for future tuning: this corpus has no title text, so it cannot
+ * validate a *tokenization* fix (further stopwording per DEV-4830) — only a
+ * threshold-shape fix. A real precision improvement (distinguishing WHICH
+ * 0.35-0.6 fires are genuine) needs the title corpus, which is intentionally
+ * not collected. Revisit if `el-telemetry gates` after this ships still shows
+ * an unhealthy override rate on the >=0.6 hard-block tier specifically.
+ * Overridable via `config.validation.duplicateHardBlockThreshold`.
+ */
+export declare const DEFAULT_HARD_BLOCK_THRESHOLD = 0.6;
 /** A scored duplicate candidate, ready to print in the block. */
 export interface DuplicateCandidate {
     identifier: string;
@@ -71,6 +109,12 @@ export declare function scoreDuplicateCandidates(title: string, candidates: Line
 /**
  * Render the human/agent-facing block listing duplicate candidates, matching
  * the shape of the validation "Suggestions:" blocks (id · title · state ·
- * assignee). Used as the body of the thrown error when the gate fires.
+ * assignee).
+ *
+ * `mode: "block"` (default) is the body of the thrown error when the gate
+ * hard-blocks (score >= the hard-block threshold — DEV-5590). `mode:
+ * "advisory"` is printed as a warning when the score is below the hard-block
+ * threshold: creation already proceeded, so the trailing hint differs (no
+ * "re-run" — there's nothing to re-run).
  */
-export declare function formatDuplicateBlock(candidates: DuplicateCandidate[]): string;
+export declare function formatDuplicateBlock(candidates: DuplicateCandidate[], mode?: "block" | "advisory"): string;

package/dist/utils/duplicate-detection.js

@@ -31,6 +31,44 @@
  * Overridable via `config.validation.duplicateThreshold`.
  */
 export const DEFAULT_DUPLICATE_THRESHOLD = 0.35;
+/**
+ * Threshold above which a candidate is a HARD block (creation refuses without
+ * `--allow-duplicate`). Below this (but at/above {@link DEFAULT_DUPLICATE_THRESHOLD})
+ * a candidate is ADVISORY ONLY — printed, but creation proceeds — DEV-5590.
+ *
+ * Why a second threshold instead of just retuning the first: `el-telemetry
+ * gates` measured a 52.2% override rate on the single-threshold (0.35) gate
+ * over 144 real fires. Analyzing the real ledger (`top_score` + `outcome` per
+ * fire, no title text is ever recorded — el-linear collects nothing by
+ * default) falsifies the obvious fix of "just raise the threshold": mean/
+ * median `top_score` for `blocked` fires (0.414 / 0.40) and `overridden`
+ * fires (0.421 / 0.40) are statistically indistinguishable, and simulating
+ * every cutoff from 0.35 to 0.56 against the real corpus held the override
+ * rate flat at 52–63% — *increasing* at some higher cutoffs. Score alone does
+ * not separate genuine duplicates from legitimate distinct issues in this
+ * workspace's real usage; no single threshold in the observed range is
+ * better than a coin flip.
+ *
+ * Given that, blocking hard on a weak signal is worse than not blocking at
+ * all: over half the stops were wrong. 0.6 sits above the entire analyzed
+ * range (only 1/144 historical fires scored this high) and is reserved for
+ * near-verbatim title overlap — at Jaccard >= 0.6, more than 6 of every 10
+ * combined salient tokens are shared, which is a qualitatively different
+ * (and much rarer) signal than the "shares a few topical words" fires that
+ * dominate the false-positive population. This preserves a real backstop for
+ * the obvious copy-paste case while no longer forcing a stop-and-override
+ * ritual on the ambiguous 0.35-0.6 band, where the data shows we're wrong
+ * about as often as we're right.
+ *
+ * Caveat for future tuning: this corpus has no title text, so it cannot
+ * validate a *tokenization* fix (further stopwording per DEV-4830) — only a
+ * threshold-shape fix. A real precision improvement (distinguishing WHICH
+ * 0.35-0.6 fires are genuine) needs the title corpus, which is intentionally
+ * not collected. Revisit if `el-telemetry gates` after this ships still shows
+ * an unhealthy override rate on the >=0.6 hard-block tier specifically.
+ * Overridable via `config.validation.duplicateHardBlockThreshold`.
+ */
+export const DEFAULT_HARD_BLOCK_THRESHOLD = 0.6;
 /**
  * Function words and issue-boilerplate tokens that carry no topical signal.
  * Dropping them keeps the Jaccard score driven by the distinctive nouns
@@ -174,14 +212,26 @@ export function scoreDuplicateCandidates(title, candidates, threshold = DEFAULT_
 /**
  * Render the human/agent-facing block listing duplicate candidates, matching
  * the shape of the validation "Suggestions:" blocks (id · title · state ·
- * assignee). Used as the body of the thrown error when the gate fires.
+ * assignee).
+ *
+ * `mode: "block"` (default) is the body of the thrown error when the gate
+ * hard-blocks (score >= the hard-block threshold — DEV-5590). `mode:
+ * "advisory"` is printed as a warning when the score is below the hard-block
+ * threshold: creation already proceeded, so the trailing hint differs (no
+ * "re-run" — there's nothing to re-run).
  */
-export function formatDuplicateBlock(candidates) {
+export function formatDuplicateBlock(candidates, mode = "block") {
     const lines = candidates.map((c) => `    ${c.identifier} · ${c.title} · ${c.state} · ${c.assignee}  (similarity ${c.score})`);
-    return (`Possible duplicate issue${candidates.length > 1 ? "s" : ""} found ` +
+    const header = `Possible duplicate issue${candidates.length > 1 ? "s" : ""} found ` +
         "(by title-keyword overlap):\n" +
         `${lines.join("\n")}\n\n` +
-        "  If one of these is the same work, comment on it instead of creating a new issue.\n" +
+        "  If one of these is the same work, comment on it instead of creating a new issue.\n";
+    if (mode === "advisory") {
+        return (header +
+            "  This is advisory only (DEV-5590) — creation is proceeding. Pass " +
+            "--allow-duplicate to silence this notice next time.");
+    }
+    return (header +
         "  If this is genuinely distinct, re-run with --allow-duplicate to proceed " +
         "(and consider --related-to to link the related issue).");
 }

package/dist/utils/gate-telemetry.d.ts

@@ -29,9 +29,15 @@ export interface GateEvent {
      * `blocked` — the gate stopped creation. `overridden` — a gate-specific
      * override flag let a would-block proceed. `fail-open` — the gate could not
      * evaluate (infra/service error) and let creation proceed rather than block
-     * on trouble; tracked so degradation is measurable (DEV-5378).
+     * on trouble; tracked so degradation is measurable (DEV-5378). `advisory` —
+     * the gate fired below its hard-block threshold: printed, but never forced
+     * a stop (DEV-5590). Like `fail-open`, the tools-repo reader
+     * (`el-telemetry gates`) only recognizes `blocked`/`overridden` for the
+     * override-rate denominator — an unrecognized outcome is skipped rather
+     * than counted, so `advisory` fires are visible in the raw ledger but
+     * intentionally excluded from the metric.
      */
-    outcome: "blocked" | "overridden" | "fail-open";
+    outcome: "blocked" | "overridden" | "fail-open" | "advisory";
     /** Highest candidate similarity that triggered the gate (0–1). */
     topScore?: number;
     /** How many candidates crossed the threshold. */

package/dist/utils/graphql-issues-service.js

@@ -1,6 +1,6 @@
 import { isRegistryConfigured, resolveViaRegistry, } from "../config/registry-resolve.js";
 import { resolveUserDisplayName } from "../config/resolver.js";
-import { ARCHIVE_ISSUE_MUTATION, BATCH_GET_ISSUES_QUERY, BATCH_RESOLVE_FOR_CREATE_QUERY, BATCH_RESOLVE_FOR_SEARCH_QUERY, BATCH_RESOLVE_FOR_UPDATE_QUERY, buildResolveLabelsByNameQuery, CREATE_ISSUE_MUTATION, DELETE_ISSUE_MUTATION, FILTERED_SEARCH_ISSUES_QUERY, GET_ISSUE_BY_ID_QUERY, GET_ISSUE_BY_IDENTIFIER_QUERY, GET_ISSUE_CLAIM_CONTEXT_QUERY, GET_ISSUE_START_CONTEXT_QUERY, GET_ISSUE_TEAM_QUERY, GET_ISSUES_QUERY, SEARCH_ISSUES_QUERY, TEAM_STARTED_STATUSES_QUERY, UPDATE_ISSUE_MUTATION, } from "../queries/issues.js";
+import { ARCHIVE_ISSUE_MUTATION, BATCH_GET_ISSUES_QUERY, BATCH_RESOLVE_FOR_CREATE_QUERY, BATCH_RESOLVE_FOR_SEARCH_QUERY, BATCH_RESOLVE_FOR_UPDATE_QUERY, buildResolveLabelsByNameQuery, CREATE_ISSUE_MUTATION, DELETE_ISSUE_MUTATION, FILTERED_SEARCH_ISSUES_QUERY, GET_ISSUE_BY_ID_QUERY, GET_ISSUE_BY_IDENTIFIER_QUERY, GET_ISSUE_CLAIM_CONTEXT_QUERY, GET_ISSUE_START_CONTEXT_QUERY, GET_ISSUE_TEAM_QUERY, GET_ISSUES_QUERY, SEARCH_ISSUES_QUERY, TEAM_SCOPED_FILTERED_ISSUES_QUERY, TEAM_STARTED_STATUSES_QUERY, UPDATE_ISSUE_MUTATION, } from "../queries/issues.js";
 import { CREATE_LABEL_MUTATION } from "../queries/labels.js";
 import { TERMINAL_STATE_TYPES } from "../types/linear.js";
 import { toISOStringOrNow, toISOStringOrUndefined } from "./date-format.js";
@@ -556,8 +556,14 @@ export class GraphQLIssuesService {
                 priority: args.priority,
             });
         }
+        // DEV-5578: the team boundary is NOT put in the IssueFilter. Linear's
+        // top-level `issues(filter: { team: { id: { eq } } })` relation filter
+        // leaks other teams' issues once `first` grows past a small page (~20),
+        // so `--team` was silently contaminated on paginated (`--limit > ~20`)
+        // results. When a team is present we scope structurally through the
+        // `Team.issues` connection below (same class of fix as DEV-5325's
+        // `Team.projects`); the rest of the filter rides on top of it.
         const filter = this.buildSearchFilter({
-            teamId: finalTeamId,
             assigneeId: finalAssigneeId,
             delegateId: finalDelegateId,
             project: projectFilter,
@@ -566,10 +572,25 @@ export class GraphQLIssuesService {
             labelNames: args.labelNames,
             priority: args.priority,
         });
+        const filterArg = Object.keys(filter).length > 0 ? filter : undefined;
+        const orderBy = args.orderBy ?? "updatedAt";
+        if (finalTeamId) {
+            const teamScoped = await this.graphQLService.rawRequest(TEAM_SCOPED_FILTERED_ISSUES_QUERY, {
+                teamId: finalTeamId,
+                first: limit,
+                filter: filterArg,
+                orderBy,
+            });
+            const nodes = teamScoped.team?.issues?.nodes;
+            if (!nodes?.length) {
+                return [];
+            }
+            return nodes.map((issue) => this.transformIssueData(issue));
+        }
         const searchResult = await this.graphQLService.rawRequest(FILTERED_SEARCH_ISSUES_QUERY, {
             first: limit,
-            filter: Object.keys(filter).length > 0 ? filter : undefined,
-            orderBy: args.orderBy ?? "updatedAt",
+            filter: filterArg,
+            orderBy,
         });
         const filteredIssues = searchResult.issues;
         if (!filteredIssues?.nodes) {
@@ -999,11 +1020,12 @@ export class GraphQLIssuesService {
         }
         return filtered;
     }
+    // DEV-5578: `teamId` is intentionally NOT a member — the team boundary is
+    // applied structurally via `TEAM_SCOPED_FILTERED_ISSUES_QUERY`, never as a
+    // top-level `team` relation filter (which Linear leaks past ~20 rows). Do
+    // not reintroduce a `filter.team = …` branch here.
     buildSearchFilter(filters) {
         const filter = {};
-        if (filters.teamId) {
-            filter.team = { id: { eq: filters.teamId } };
-        }
         if (filters.assigneeId) {
             filter.assignee = { id: { eq: filters.assigneeId } };
         }

package/dist/utils/linear-service.d.ts

@@ -14,6 +14,14 @@ export declare class LinearService {
     resolveIssueId(issueId: string): Promise<string>;
     getTeams(limit?: number): Promise<LinearTeam[]>;
     resolveUserId(nameOrEmailOrId: string): Promise<string>;
+    /**
+     * Single-user lookup by UUID, email, or name (DEV-5612) — the natural
+     * complement to `getUsers`/`users list`, so identifying one actor (e.g. an
+     * unrecognized member surfaced by the alias wizard) doesn't require
+     * dumping the whole workspace. Resolution/ambiguity semantics match every
+     * other `--assignee`-style lookup in the CLI via {@link resolveUserId}.
+     */
+    getUser(nameOrEmailOrId: string): Promise<LinearUser>;
     getUsers(activeOnly?: boolean, limit?: number, nameFilter?: string): Promise<LinearUser[]>;
     getProjects(limit?: number, options?: {
         nameFilter?: string;

package/dist/utils/linear-service.js

@@ -99,6 +99,24 @@ export class LinearService {
         }
         throw notFoundError("User", nameOrEmailOrId);
     }
+    /**
+     * Single-user lookup by UUID, email, or name (DEV-5612) — the natural
+     * complement to `getUsers`/`users list`, so identifying one actor (e.g. an
+     * unrecognized member surfaced by the alias wizard) doesn't require
+     * dumping the whole workspace. Resolution/ambiguity semantics match every
+     * other `--assignee`-style lookup in the CLI via {@link resolveUserId}.
+     */
+    async getUser(nameOrEmailOrId) {
+        const id = await this.resolveUserId(nameOrEmailOrId);
+        const user = await this.client.user(id);
+        return {
+            id: user.id,
+            name: user.name,
+            displayName: user.displayName,
+            email: user.email,
+            active: user.active,
+        };
+    }
     async getUsers(activeOnly, limit = 100, nameFilter) {
         const filter = {};
         if (activeOnly) {

package/dist/utils/output.js

@@ -1,4 +1,5 @@
 import { execFileSync } from "node:child_process";
+import { resolveActiveProfile } from "../config/paths.js";
 import { dispatch as dispatchSummary, drainSummaryFieldWarnings, formatLine, inferKindFromPayload, } from "./formatters/summary.js";
 import { logger } from "./logger.js";
 import { sanitizeForLog } from "./sanitize-for-log.js";
@@ -57,6 +58,19 @@ function getNestedPath(obj, path) {
     }
     return cur;
 }
+/**
+ * Aliases for the table/csv column names that don't exist as literal keys
+ * on the JSON payload (DEV-5376). Tried only after the literal key and the
+ * dot-path both miss, and only kept when the alias target actually
+ * resolves — so a resource that genuinely lacks `state`/`updatedAt` still
+ * gets the explicit-null + `fields_unresolved` treatment. The requested
+ * name stays the output key (`{"status": "Todo"}`), matching the
+ * "consumers read exactly what they asked for" contract.
+ */
+const FIELD_ALIASES = {
+    status: "state.name",
+    updated: "updatedAt",
+};
 /**
  * Project `obj` down to the requested fields.
  *
@@ -64,6 +78,8 @@ function getNestedPath(obj, path) {
  * - Dot-separated paths (DEV-5323) resolve nested values; the requested path
  *   string becomes a flat output key (`{"pipeline.status": "success"}`), so
  *   consumers read exactly what they asked for.
+ * - Documented column aliases resolve when the literal key is absent
+ *   (`status` → `state.name`, `updated` → `updatedAt`; DEV-5376).
  * - A field that resolves nowhere is emitted as an explicit `null` AND
  *   reported via `unresolved` — never silently omitted. Silent omission made
  *   a typo'd field indistinguishable from an empty value (DEV-5323).
@@ -114,6 +130,12 @@ function filterFields(obj, fields, unresolved) {
                 result[field] = nested;
                 continue;
             }
+            const alias = FIELD_ALIASES[field];
+            const aliased = alias !== undefined ? getNestedPath(source, alias) : undefined;
+            if (aliased !== undefined) {
+                result[field] = aliased;
+                continue;
+            }
             result[field] = null;
             unresolved?.add(field);
         }
@@ -354,7 +376,25 @@ function outputError(error) {
     // `lin_oauth_…` / `Bearer <payload>` in error text can't leak a token
     // into stdout, shell history, or CI logs. The wizard already sanitizes
     // its own log paths; this is the central error path on every command.
-    const payload = JSON.stringify({ error: sanitizeForLog(error.message) }, null, 2);
+    //
+    // `activeProfile` is included so a "not found" error is distinguishable
+    // from "wrong workspace" without manually inspecting
+    // ~/.config/el-linear/active-profile (DEV-5610) — the active profile can
+    // change between commands (an explicit `profile use`, a different
+    // $EL_LINEAR_PROFILE, or another process on the machine switching the
+    // shared marker file), and a bare "X not found" reads as data loss or an
+    // API outage when the real cause is often just the wrong workspace.
+    // Guarded: resolveActiveProfile() throws on an invalid $EL_LINEAR_PROFILE
+    // value (a real, separate user error) — outputError is the last-resort
+    // error path, so this addition must not itself throw uncaught.
+    let activeProfile = "<unknown>";
+    try {
+        activeProfile = resolveActiveProfile().name ?? "<legacy default>";
+    }
+    catch {
+        // leave activeProfile as "<unknown>"
+    }
+    const payload = JSON.stringify({ error: sanitizeForLog(error.message), activeProfile }, null, 2);
     // Write to stdout (same channel as success) so machine callers always
     // receive exactly one parseable JSON object regardless of stream capture.
     logger.info(payload);

package/dist/utils/root-opts.d.ts

@@ -9,3 +9,16 @@ import type { Command, OptionValues } from "commander";
  * assertions live here so call sites can stay clean and typed.
  */
 export declare function getRootOpts(command: Command): OptionValues;
+/**
+ * Resolve an option that is registered on BOTH the root program and a
+ * subcommand (`--format` / `--fields` on `issues list|search`,
+ * `projects list`).
+ *
+ * Commander 15 hands a same-named option to the OUTERMOST registration
+ * even when it appears after the subcommand: `issues list --format table`
+ * sets the program's global `--format` and leaves the subcommand's local
+ * option at its default, so handlers reading `options.format` silently
+ * saw `"json"` (DEV-5376). Precedence here: local CLI-set value, then the
+ * nearest ancestor's CLI-set value, then the local default.
+ */
+export declare function effectiveOption(command: Command, key: string): string | undefined;