santree 0.7.0 → 0.7.3

package/dist/lib/trackers/linear/index.js

@@ -1,6 +1,6 @@
 import { readLinearAuthStore } from "../auth-store.js";
 import { getRepoLinearOrg, getValidTokens, removeRepoLinearOrg, revokeTokens } from "./auth.js";
-import { fetchAssignedIssues, fetchIssue } from "./api.js";
+import { fetchAssignedIssues, fetchIssue, fetchTriageSchedules } from "./api.js";
 import { cleanupLinearImages, rewriteLinearImages } from "./images.js";
 export { getRepoLinearOrg, setRepoLinearOrg, removeRepoLinearOrg, getValidTokens, revokeTokens, startOAuthFlow, } from "./auth.js";
 async function getAuthStatus(repoRoot) {
@@ -59,6 +59,20 @@ async function listAssigned(repoRoot) {
     }
     return { ok: true, value: issues };
 }
+async function getTriageSchedules(repoRoot) {
+    const orgSlug = getRepoLinearOrg(repoRoot);
+    if (!orgSlug)
+        return [];
+    const tokens = await getValidTokens(orgSlug);
+    if (!tokens)
+        return [];
+    try {
+        return await fetchTriageSchedules(tokens.access_token);
+    }
+    catch {
+        return [];
+    }
+}
 async function getIssue(identifier, repoRoot) {
     const orgSlug = getRepoLinearOrg(repoRoot);
     if (!orgSlug) {
@@ -91,10 +105,12 @@ export const linearTracker = {
     kind: "linear",
     displayName: "Linear",
     issueNoun: "ticket",
+    supportsTriage: true,
     getAuthStatus,
     signOut,
     extractIdFromBranch,
     cleanupCache: cleanupLinearImages,
     listAssigned,
     getIssue,
+    getTriageSchedules,
 };

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

@@ -9,6 +9,18 @@ export interface State {
     name: string;
     type: string;
 }
+/** Readiness of an issue given its blocking dependencies:
+ *   "ready"   — no unresolved blockers (or none at all)
+ *   "blocked" — at least one blocker isn't done yet
+ *   "unknown" — the tracker doesn't expose dependency data */
+export type Readiness = "ready" | "blocked" | "unknown";
+export declare function issueReadiness(blockedBy: IssueRef[] | undefined): Readiness;
+/** A lightweight reference to a related issue, with whether it's resolved
+ * (state.type is completed/canceled). Used for dependency (blocks) relations. */
+export interface IssueRef {
+    identifier: string;
+    done: boolean;
+}
 export interface AssignedIssue {
     identifier: string;
     title: string;
@@ -20,10 +32,50 @@ export interface AssignedIssue {
     labels: string[];
     projectId: string | null;
     projectName: string | null;
+    /** Issues that block this one ("blocked by"). An issue is ready to start when
+     * every blocker is `done`. `undefined` when the tracker doesn't expose
+     * dependency relations (only Linear does); `[]` means no blockers. */
+    blockedBy?: IssueRef[];
+    /** Issues this one blocks (downstream dependents). */
+    blocking?: IssueRef[];
+    /** When the issue's triage SLA breaches, as an ISO timestamp, or null when
+     * no SLA applies. Only trackers with a native SLA concept populate it
+     * (Linear today); others leave it undefined. Surfaced on the Triage tab as a
+     * colored, urgency-coded countdown badge. */
+    slaBreachesAt?: string | null;
+    /** When the issue is snoozed until, as an ISO timestamp, or null when not
+     * snoozed. A snooze in the future means the issue is parked — surfaced on the
+     * Triage tab as a greyed, sunk-to-the-bottom row so active work stands out.
+     * Linear-only today. */
+    snoozedUntilAt?: string | null;
 }
 export interface Issue extends AssignedIssue {
     comments: Comment[];
 }
+/** One slot in a triage on-call rotation. */
+export interface TriageShift {
+    startsAt: string;
+    endsAt: string;
+    /** Resolved display name (falls back to email, then "Unknown"). */
+    name: string;
+    /** True when this shift covers the current moment. */
+    isCurrent: boolean;
+    /** True when this shift belongs to the authenticated viewer. */
+    isMe: boolean;
+}
+/** A team's triage responsibility rotation (Linear "Triage responsibility"
+ * backed by a time schedule). */
+export interface TriageSchedule {
+    teamKey: string;
+    teamName: string;
+    scheduleName: string;
+    /** Display name of whoever is on call right now, if known. */
+    currentName: string | null;
+    /** Whether the viewer is the one currently on call. */
+    currentIsMe: boolean;
+    /** Chronological list of shifts. */
+    shifts: TriageShift[];
+}
 export interface AuthStatus {
     authenticated: boolean;
     accountLabel?: string;
@@ -65,6 +117,17 @@ export interface IssueTracker {
     cleanupCache(identifier: string): void;
     listAssigned(repoRoot: string): Promise<IssueTrackerResult<AssignedIssue[]>>;
     getIssue(identifier: string, repoRoot: string): Promise<IssueTrackerResult<Issue>>;
+    /** When true, this tracker has a native triage concept (incoming issues in
+     * a `state.type === "triage"` inbox). The dashboard surfaces a dedicated
+     * Triage tab only when the active tracker sets this — feature detection,
+     * never a `kind === "linear"` string check, per the
+     * no-tracker-conditionals-outside-the-factory policy. Linear sets it;
+     * GitHub/Local leave it undefined. */
+    readonly supportsTriage?: boolean;
+    /** Triage on-call rotations for the viewer's teams. Optional — implemented
+     * only by trackers with a triage scheduling concept (Linear). Returns an
+     * empty array on failure or when no schedules exist; never throws. */
+    getTriageSchedules?(repoRoot: string): Promise<TriageSchedule[]>;
     /** When true, the tracker implements createIssue/updateIssue/deleteIssue.
      * Read-only trackers (Linear, GitHub) leave this undefined; UI surfaces
      * gate every mutation path on `tracker.canMutate === true` (feature

package/dist/lib/trackers/types.js

@@ -1 +1,5 @@
-export {};
+export function issueReadiness(blockedBy) {
+    if (blockedBy === undefined)
+        return "unknown";
+    return blockedBy.some((b) => !b.done) ? "blocked" : "ready";
+}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "santree",
-	"version": "0.7.0",
+	"version": "0.7.3",
 	"description": "Git worktree manager",
 	"license": "MIT",
 	"author": "Santiago Toscanini",

package/prompts/ask.njk

@@ -0,0 +1,10 @@
+You are helping triage an incoming issue. Below is the full issue with all of its comments. Answer the question that follows concisely and directly, grounded in what the issue and its discussion actually say.
+
+When the question is about whether or how the issue can be fixed, you may inspect the codebase read-only (Read/Grep/Glob) to ground your answer in the real code — name the relevant files. Do not make any changes, and do not ask the user to run commands.
+
+Keep the answer short and skimmable: a few sentences or a short bullet list. If the issue lacks the information needed to answer, say what's missing.
+
+{{ ticket_content }}
+
+## Question
+{{ user_question }}