mintree 0.2.4 → 0.3.0

package/dist/lib/providers/types.d.ts

@@ -1,12 +1,12 @@
 /**
  * Shared types and the IssueProvider interface implemented by the
- * github/plane providers. Keeping these in one file lets the dashboard and
+ * github/linear providers. Keeping these in one file lets the dashboard and
  * worktree commands talk to issues abstractly while each provider owns its
  * own transport details.
  *
  * `IssueId` is a string in both providers — for GitHub it's the issue number
- * stringified ("100"); for Plane it'll be the project-prefixed identifier
- * ("BACK-100"). The branch convention encodes this same string verbatim, so
+ * stringified ("100"); for Linear it's the team-prefixed identifier
+ * ("FE-123"). The branch convention encodes this same string verbatim, so
  * worktree dir names round-trip through the IssueId without re-parsing.
  */
 export type IssueId = string;
@@ -28,13 +28,13 @@ export type ProviderIssue = {
     updatedAt: string;
 };
 /**
- * The issue's membership on a project board (GitHub Projects v2 / Plane
- * project), used to group the dashboard list. `status` is the workflow
+ * The issue's membership on a project board (GitHub Projects v2 / Linear
+ * team), used to group the dashboard list. `status` is the workflow
  * state's display name (null when the issue is on the board but no state is
  * set). `statusOrder` gives the column index so the dashboard can order
  * sub-groups the same way the board does. `statusColor` is an Ink-renderable
  * colour string — a 16-colour name for GitHub's enum, or a #rrggbb hex for
- * Plane states.
+ * Linear states.
  */
 export type IssueProjectInfo = {
     projectTitle: string;
@@ -47,7 +47,7 @@ export type IssueProjectInfo = {
 /**
  * Result of transitionIssueToInProgress. Discriminated so the caller can
  * render a precise status message without inventing one. Provider-agnostic:
- * the github and plane implementations both yield these shapes.
+ * the github and linear implementations both yield these shapes.
  */
 export type TransitionResult = {
     kind: "transitioned";
@@ -82,11 +82,11 @@ export type TransitionResult = {
     hint?: string;
 };
 export interface IssueProvider {
-    readonly kind: "github" | "plane";
+    readonly kind: "github" | "linear";
     /**
      * Lists open issues assigned to the current user, scoped to whatever the
      * provider considers the active context (GH: the current repo on origin;
-     * Plane: the configured workspace/projects). Returns null on transient
+     * Linear: the configured workspace/teams). Returns null on transient
      * failure (auth, network) — the dashboard renders an error hint.
      */
     listAssignedIssues(): Promise<ProviderIssue[] | null>;

package/dist/lib/providers/types.js

@@ -1,12 +1,12 @@
 /**
  * Shared types and the IssueProvider interface implemented by the
- * github/plane providers. Keeping these in one file lets the dashboard and
+ * github/linear providers. Keeping these in one file lets the dashboard and
  * worktree commands talk to issues abstractly while each provider owns its
  * own transport details.
  *
  * `IssueId` is a string in both providers — for GitHub it's the issue number
- * stringified ("100"); for Plane it'll be the project-prefixed identifier
- * ("BACK-100"). The branch convention encodes this same string verbatim, so
+ * stringified ("100"); for Linear it's the team-prefixed identifier
+ * ("FE-123"). The branch convention encodes this same string verbatim, so
  * worktree dir names round-trip through the IssueId without re-parsing.
  */
 export {};

package/dist/lib/session-signal.d.ts

@@ -19,7 +19,7 @@ export declare function extractRepoAndDir(cwd: string): {
  * Pulls the issue id out of a `<issue>-<desc>` worktree directory name.
  * Returns null when the directory name doesn't follow the convention (e.g.
  * a manually-created worktree dropped under .mintree/worktrees/). The id
- * is either bare digits (GitHub) or a `<PROJ>-\d+` Plane identifier.
+ * is either bare digits (GitHub) or a `<TEAM>-\d+` Linear identifier.
  */
 export declare function issueIdFromWorktreeDir(worktreeDir: string): string | null;
 export type StatePayload = {

package/dist/lib/session-signal.js

@@ -35,7 +35,7 @@ export function extractRepoAndDir(cwd) {
  * Pulls the issue id out of a `<issue>-<desc>` worktree directory name.
  * Returns null when the directory name doesn't follow the convention (e.g.
  * a manually-created worktree dropped under .mintree/worktrees/). The id
- * is either bare digits (GitHub) or a `<PROJ>-\d+` Plane identifier.
+ * is either bare digits (GitHub) or a `<TEAM>-\d+` Linear identifier.
  */
 export function issueIdFromWorktreeDir(worktreeDir) {
     const m = worktreeDir.match(/^((?:[A-Z][A-Z0-9_]*-)?\d+)-/);

package/dist/lib/worktreeCreate.js

@@ -225,8 +225,8 @@ export function runCreateDetached(opts) {
         };
     }
     // Same shape as BRANCH_REGEX's issueId capture: bare digits (GitHub) or
-    // `<PROJ>-\d+` (Plane). Otherwise the detached-worktree flow rejects
-    // valid Plane ids like "AUTH-6" when they reach this entry point.
+    // `<TEAM>-\d+` (Linear). Otherwise the detached-worktree flow rejects
+    // valid Linear ids like "FE-123" when they reach this entry point.
     if (!/^(?:[A-Z][A-Z0-9_]*-)?\d+$/.test(opts.issueId)) {
         return { ok: false, message: `Invalid issueId: ${opts.issueId}` };
     }

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "mintree",
-	"version": "0.2.4",
+	"version": "0.3.0",
 	"description": "Issue-driven git worktrees + Claude Code sessions for repos with an opinionated SDD+TDD flow.",
 	"license": "MIT",
 	"author": "Martin Mineo <mmineo@canarytechnologies.com>",

package/dist/lib/providers/plane.d.ts

@@ -1,61 +0,0 @@
-/**
- * PlaneProvider — implements IssueProvider against Plane's REST API
- * (https://api.plane.so by default, overridable for self-hosted).
- *
- * Talks raw HTTP rather than going through Plane's MCP server because
- * mintree runs as a Node CLI, not inside an MCP host. The shape of the
- * calls mirrors the MCP tools (list_work_items, list_states, get_me,
- * update_work_item) so the eventual error surface looks familiar.
- *
- * Auth resolution order: `PLANE_API_KEY` env var → `~/.mintree/
- * credentials.json` (`{ plane: { apiKey: "..." } }`). Never reads or
- * writes credentials to the repo's `.mintree/` directory — workspace API
- * keys are user-scoped, not repo-scoped.
- *
- * Filtering by assignee is done client-side: Plane's documented list
- * endpoint doesn't expose an assignee filter, so the provider fetches
- * the project's work items (paginated, per_page=100) and drops ones not
- * assigned to the current user. Acceptable for typical project sizes;
- * if a workspace ever grows past a few hundred items per project we can
- * revisit (probably by switching to the `/work-items/search/` endpoint
- * when it stabilises).
- */
-import type { IssueId, IssueProjectInfo, IssueProvider, ProviderIssue, TransitionResult } from "./types.js";
-export declare class PlaneProvider implements IssueProvider {
-    private readonly repoRoot;
-    readonly kind: "plane";
-    private cachedUserId;
-    private workItemsByProject;
-    private statesByProject;
-    constructor(repoRoot: string);
-    private getConfig;
-    private getUserId;
-    private fetchAssignedWorkItems;
-    private fetchStates;
-    listAssignedIssues(): Promise<ProviderIssue[] | null>;
-    fetchProjectAssignments(): Promise<Map<IssueId, IssueProjectInfo> | null>;
-    transitionIssueToInProgress(issueId: IssueId): Promise<TransitionResult>;
-}
-/**
- * Doctor-side snapshot of the Plane integration's health. Bundles the API-
- * key resolution, `/users/me/` ping, and a per-configured-project
- * existence check into one async call so the doctor row can render
- * everything in one pass. Returns a structured result (not a boolean) so
- * the UI can surface specific hints instead of generic failures.
- */
-export type PlaneSetupCheck = {
-    configured: boolean;
-    hasApiKey: boolean;
-    authOk: boolean;
-    user?: string;
-    workspaceSlug?: string;
-    apiUrl?: string;
-    projects: Array<{
-        identifier: string;
-        id: string;
-        ok: boolean;
-        error?: string;
-    }>;
-    hint?: string;
-};
-export declare function checkPlaneSetup(repoRoot: string): Promise<PlaneSetupCheck>;