release 2026.6.0 to stable channel

.claude-plugin/marketplace.json

@@ -0,0 +1,22 @@
+{
+  "name": "linearis",
+  "owner": {
+    "name": "linearis-oss",
+    "url": "https://github.com/linearis-oss/linearis"
+  },
+  "metadata": {
+    "description": "Marketplace for the linearis Claude Code plugin.",
+    "version": "1.0.0"
+  },
+  "plugins": [
+    {
+      "name": "linearis",
+      "source": "./",
+      "description": "Agent skill teaching agents to use the linearis Linear.app CLI.",
+      "version": "1.0.0",
+      "author": { "name": "linearis-oss" },
+      "homepage": "https://github.com/linearis-oss/linearis",
+      "license": "MIT"
+    }
+  ]
+}

.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "linearis",
+  "description": "Agent skill for the linearis Linear.app CLI: preflight, discover-then-act usage protocol, JSON output, ID resolution, discussions, files.",
+  "version": "1.0.0",
+  "author": {
+    "name": "linearis-oss",
+    "url": "https://github.com/linearis-oss/linearis"
+  },
+  "homepage": "https://github.com/linearis-oss/linearis",
+  "license": "MIT"
+}

.conductor/settings.toml

@@ -0,0 +1,137 @@
+#:schema https://conductor.build/schemas/settings.repo.schema.json
+"$schema" = "https://conductor.build/schemas/settings.repo.schema.json"
+
+[scripts]
+# `npm install` also runs the `prepare` hook: GraphQL codegen (src/gql/) + lefthook install.
+setup = "npm install"
+# Stateless JSON-output CLI — no shared port/db/stack — so workspaces can run side by side.
+run_mode = "concurrent"
+# Remove per-workspace build output on archive; leaves source untouched.
+archive = "npm run clean"
+
+[scripts.run.test]
+command = "npm test"
+default = true
+icon = "test-tube"
+
+[scripts.run.build]
+command = "npm run build"
+icon = "package"
+
+[scripts.run.check]
+command = "npm run check:ci"
+icon = "wrench"
+
+[prompts]
+# Appended to EVERY agent session. Keep lean — AGENTS.md (loaded as CLAUDE.md) is the
+# single source of truth for architecture, the P0 invariants, and the verification
+# checklist; do not restate them here.
+general = """
+You are a senior engineer on Linearis, a JSON-only CLI for Linear.app (TypeScript strict, \
+ESM). Always respond in English, even when addressed in another language.
+
+AGENTS.md (loaded as CLAUDE.md) is authoritative for the 5-layer architecture, the P0 \
+invariants, and the verification checklist — follow it; do not re-derive or restate its rules.
+
+Be a careful git operator. Before starting substantial work, bring the branch up to date \
+with its base branch (the branch it will merge into) — fetch, then rebase onto it rather \
+than merging it in — so your changes apply cleanly and the history stays linear.
+
+Treat the commit history as durable context for future contributors, held to the same \
+standard as the code. Make each commit well-scoped and single-purpose, and give it an \
+extended body explaining not just what changed but why: the problem, the approach, and any \
+trade-offs or alternatives considered. Any TODO you leave must reference an issue.
+
+Verify with the AGENTS.md checklist, scoped to what you touched, and report exactly what you \
+ran — never claim a check passed without running it. Skip the build/test checklist for \
+docs-, comment-, or config-only changes; run the full checklist before opening a PR.
+
+Never touch CHANGELOG.md — it is owned by the release workflow.
+"""
+
+# Commit history is a first-class deliverable. Conventional Commits are enforced by
+# commitlint in CI over the whole PR range, so malformed messages fail the build.
+create_pr = """
+In addition to Conductor's standard Create PR behavior, hold the commit history and PR to \
+these repo rules.
+
+Commits — Conventional Commits, enforced by commitlint over the full PR range:
+- Format `type(scope): subject`; lower-case scope; imperative subject, >= 10 chars.
+- Allowed types only: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test.
+- Choose the type by real impact: feat/fix/perf/revert trigger a release, the rest do not — \
+  do not inflate a chore into a feat.
+- One logical change per commit; a blank line before any body/footer. Reference issues in the \
+  body (Closes #n, Refs #n, Part of #n) when applicable.
+- Give every non-trivial commit an extended body written as context for future contributors: \
+  what changed and, more importantly, why — the problem, the approach, and any trade-offs or \
+  alternatives considered. Structure it (short prose or bullets); do not just restate the subject.
+- Do NOT add AI co-author or Co-authored-by trailers.
+- Never include CHANGELOG.md in the branch history — it is release-workflow-owned.
+
+History hygiene — before opening the PR, rework the branch into a clean, linear history:
+- Rebase onto the latest base branch (resolve conflicts; do not merge the base in).
+- Reshape the commits into well-isolated, correctly-scoped Conventional Commits: split commits \
+  that mix concerns, squash fixup/wip noise, and reorder so each commit stands on its own, \
+  builds, and passes its own checks.
+- Ensure each resulting commit carries the extended what/why body above.
+- Only rewrite history that is yours and unmerged — never rewrite commits already on the base \
+  branch or that teammates build on.
+
+PR:
+- The title must itself be a valid Conventional Commit subject.
+- Body: what changed and why, the risk/impact, and which AGENTS.md checks you ran to verify. \
+  Keep it tight and skimmable.
+- Remove design artifacts (e.g. plan files under docs/plans/) before opening the PR.
+"""
+
+# Correctness first, then the repo's own invariants; reference AGENTS.md rather than
+# transcribing the full (drift-prone) invariant list.
+code_review = """
+In addition to Conductor's standard review, report only real, verifiable issues, most severe \
+first. Do not pad with style nitpicks the linter already covers.
+
+Prioritise:
+- Correctness and reliability: edge cases, error handling, resource/lifecycle bugs, races, \
+  wrong assumptions.
+- Every P0 invariant in AGENTS.md — especially strict layer separation, ID resolution only in \
+  resolvers, no `any`, and explicit return types on exports.
+- Test coverage: happy path + primary error case per changed function; tests mock exactly one \
+  layer down.
+- Maintainability and readability: naming, duplication, unnecessary complexity.
+- Commit history: a clean, linear series of well-scoped Conventional Commits with informative \
+  what/why bodies — flag mixed-concern, wip, or fixup commits that should be split, squashed, \
+  or rebased before merge.
+For each finding give file:line, why it is wrong, and a concrete fix. If the change is sound, \
+say so plainly rather than inventing problems.
+"""
+
+# Root cause, minimal fix, verification scaled to the size of the change.
+fix_errors = """
+Diagnose the root cause before changing anything — do not patch symptoms or silence the type \
+checker with casts. Make the smallest correct fix, matching surrounding style. When the bug is \
+testable, add or adjust a test that fails before the fix and passes after. Verify with the \
+AGENTS.md checklist scoped to the fix: always run the type check and tests; add the full build \
+and knip when the fix touches generated code, exports, or dependencies. Report exactly what you \
+ran and its result. If chasing the fix left the branch history messy (wip/fixup commits, mixed \
+concerns), fold it back into clean, well-scoped Conventional Commits with what/why bodies before \
+finishing.
+"""
+
+# Never silently drop a side; regenerate generated code from resolved sources, in that order.
+resolve_merge_conflicts = """
+Resolve conflicts by understanding the intent of both sides, not by picking one blindly. \
+Preserve every behavioural change from both branches; if two changes are genuinely \
+incompatible, stop and surface it rather than dropping one. For conflicts in generated files \
+(src/gql/), resolve the .graphql sources first, then run `npm run generate` to regenerate \
+rather than hand-merging. Never resurrect CHANGELOG.md edits. After resolving, run \
+`npx tsc --noEmit` and `npm test` to confirm the merged tree is coherent.
+"""
+
+# Conventional-Commit-aligned, descriptive, kebab-case; issue number first when one exists.
+rename_branch = """
+Name the branch after the change: `type/short-kebab-summary`, where type is a Conventional \
+Commit type (feat, fix, chore, docs, refactor, ...). Lower-case, hyphen-separated, concise but \
+descriptive. When an issue exists, put its number first: `type/NNN-short-summary` \
+(e.g. fix/142-null-token, feat/issue-search-filters). Conductor may add its own branch prefix; \
+keep the descriptive part in this form regardless.
+"""

.github/actions/setup/action.yml

@@ -0,0 +1,47 @@
+name: Setup Node and install
+description: >-
+  Sets up Node (version from .nvmrc), restores the npm cache, runs `npm ci`, and
+  optionally builds the project. Centralizes the checkout-adjacent boilerplate
+  shared by every CI job. The caller must run actions/checkout first so this
+  local action and .nvmrc are present on disk.
+
+inputs:
+  build:
+    description: Whether to run `npm run build` after install (runs codegen + tsc + usage).
+    required: false
+    default: "true"
+  node-version:
+    description: >-
+      Explicit Node version to use, overriding .nvmrc. Leave empty to use the
+      project default from .nvmrc. Set by matrix jobs that test multiple versions.
+    required: false
+    default: ""
+  registry-url:
+    description: Optional npm registry URL to configure for publishing (leave empty for CI-only jobs).
+    required: false
+    default: ""
+
+runs:
+  using: composite
+  steps:
+    # node-version (when set by a matrix job) takes precedence over
+    # node-version-file; an empty node-version falls back to .nvmrc.
+    - name: Setup Node
+      uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
+      with:
+        node-version: ${{ inputs.node-version }}
+        node-version-file: .nvmrc
+        cache: npm
+        registry-url: ${{ inputs.registry-url }}
+
+    # `npm ci` runs `prepare`, which is CI-guarded (scripts/prepare.mjs) so it
+    # does NOT hit the live Linear GraphQL schema here. Jobs needing generated
+    # types must run the build step below (or `npm pack`).
+    - name: Install dependencies
+      shell: bash
+      run: npm ci
+
+    - name: Build project
+      if: ${{ inputs.build == 'true' }}
+      shell: bash
+      run: npm run build

.github/workflows/ci-post-merge.yml

@@ -15,24 +15,15 @@ concurrency:
 
 jobs:
   sentinel:
-    name: Post-merge sentinel (node v22)
+    name: Post-merge sentinel
     runs-on: ubuntu-latest
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v6
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
 
-      - name: Setup node v22
-        uses: actions/setup-node@v6
-        with:
-          node-version: 24
-          cache: npm
-
-      - name: Install deps
-        run: npm ci
-
-      - name: Build project
-        run: npm run build
+      - name: Setup and build
+        uses: ./.github/actions/setup
 
       - name: Verify packed binaries
         run: npm run verify:packed-binaries