@tplog/pi-zendy 0.4.0 → 0.4.1

package/README.md

@@ -14,6 +14,7 @@ zendy is a single pi extension that provides:
 - **Slash Commands** — `/zendy-config` to set up credentials, `/zendy-status` to check connectivity.
 - **Skill** — a `zendy` skill (also `/skill:zendy`) that teaches the agent the ticket-analysis workflow, so "analyze ticket #1959" reliably uses the right tools in the right order.
 - **Session Safety** — Automatic workspace isolation and cleanup for source code analysis.
+- **Source Registry** — Bundled Dify source repository defaults. Enterprise repos use SSH URLs, so GitHub SSH permissions remain the access gate.
 
 Typical workflow:
 
@@ -73,7 +74,7 @@ The agent can call these tools directly:
 | `zendy_whoami` | Check the currently authenticated Zendesk identity |
 | `zendy_helm_get` | Query Helm chart values, images, validation by version |
 | `zendy_kg_search` | Semantic search over historical tickets |
-| `zendy_source_status` | Check source analysis workspace |
+| `zendy_source_status` | Check source analysis workspace and bundled Dify source repository registry |
 
 ## How it works
 
@@ -81,3 +82,5 @@ zendy registers as a pi extension package. The extension provides tools (callabl
 slash commands (for human engineers), and session lifecycle hooks (workspace creation, cleanup).
 All data access goes through direct REST APIs — no `zcli`, `zendesk-kg`, or other CLI tools
 are required at runtime.
+
+For source analysis, zendy ships default repository entries for Dify Enterprise backend/frontend and related public Dify repositories. The Enterprise entries are SSH URLs; users without GitHub SSH access can install zendy, but source clone attempts will fail at Git authentication.

package/dist/config/schema.d.ts

@@ -1,6 +1,7 @@
 export interface ZendyConfig {
     zendesk?: ZendeskConfig;
     zendeskKg?: ZendeskKgConfig;
+    sourceRepos?: Record<string, SourceRepoConfig>;
 }
 export interface ZendeskConfig {
     subdomain?: string;
@@ -11,4 +12,11 @@ export interface ZendeskKgConfig {
     apiUrl?: string;
     apiKey?: string;
 }
+export interface SourceRepoConfig {
+    url: string;
+    description?: string;
+    visibility?: "private" | "public";
+    area?: "backend" | "frontend" | "oss" | "plugin" | "sandbox";
+}
 export declare const DEFAULT_KG_API_URL = "https://zendesk-ticket-retriever.vercel.app";
+export declare const DEFAULT_SOURCE_REPOS: Record<string, SourceRepoConfig>;

package/dist/config/schema.js

@@ -1,2 +1,34 @@
 // Config schema and types for zendy configuration (~/.zendy/config.json).
 export const DEFAULT_KG_API_URL = "https://zendesk-ticket-retriever.vercel.app";
+export const DEFAULT_SOURCE_REPOS = {
+    enterpriseBackend: {
+        url: "git@github.com:langgenius/dify-enterprise.git",
+        description: "Dify Enterprise backend code",
+        visibility: "private",
+        area: "backend",
+    },
+    enterpriseFrontend: {
+        url: "git@github.com:langgenius/dify-enterprise-frontend.git",
+        description: "Dify Enterprise frontend code",
+        visibility: "private",
+        area: "frontend",
+    },
+    difyOss: {
+        url: "https://github.com/langgenius/dify.git",
+        description: "Open-source Dify repository",
+        visibility: "public",
+        area: "oss",
+    },
+    pluginDaemon: {
+        url: "https://github.com/langgenius/dify-plugin-daemon.git",
+        description: "Dify plugin daemon",
+        visibility: "public",
+        area: "plugin",
+    },
+    sandbox: {
+        url: "https://github.com/langgenius/dify-sandbox.git",
+        description: "Dify sandbox",
+        visibility: "public",
+        area: "sandbox",
+    },
+};

package/dist/config/store.d.ts

@@ -1,4 +1,4 @@
-import type { ZendyConfig } from "./schema.js";
+import { type ZendyConfig } from "./schema.js";
 export declare function getConfig(): ZendyConfig;
 export declare function writeConfig(config: ZendyConfig): void;
 export declare function configPath(): string;

package/dist/config/store.js

@@ -3,6 +3,7 @@
 import { readFileSync, writeFileSync, existsSync, mkdirSync } from "node:fs";
 import { join } from "node:path";
 import { homedir } from "node:os";
+import { DEFAULT_SOURCE_REPOS } from "./schema.js";
 const CONFIG_DIR = join(homedir(), ".zendy");
 const CONFIG_PATH = join(CONFIG_DIR, "config.json");
 // ── Env overrides ─────────────────────────────────────────────────────
@@ -52,6 +53,10 @@ export function getConfig() {
             ...fileConfig.zendeskKg,
             ...envK,
         },
+        sourceRepos: {
+            ...DEFAULT_SOURCE_REPOS,
+            ...fileConfig.sourceRepos,
+        },
     };
 }
 export function writeConfig(config) {

package/extensions/commands.ts

@@ -66,6 +66,9 @@ async function configCommand(_args: string, ctx: {
     lines.push(
       `KG: ${c.zendeskKg?.apiKey ? `apiKey=*** (set), apiUrl=${c.zendeskKg.apiUrl || "default"}` : "not configured"}`,
     );
+    const repoEntries = Object.entries(c.sourceRepos ?? {});
+    const privateCount = repoEntries.filter(([, repo]) => repo.visibility === "private").length;
+    lines.push(`Source repos: ${repoEntries.length} configured (${privateCount} private SSH-gated)`);
     ctx.ui.notify(`[zendy-config]\n${lines.join("\n")}`, "info");
   }
 }
@@ -105,6 +108,10 @@ async function statusCommand(_args: string, ctx: {
     srcDir ? `  ✓ Source workspace — ${srcDir}` : "  - Source workspace — not active (will be created on session start)",
   );
 
+  const repoEntries = Object.entries(getConfig().sourceRepos ?? {});
+  const privateCount = repoEntries.filter(([, repo]) => repo.visibility === "private").length;
+  lines.push(`  ✓ Source repos — ${repoEntries.length} configured (${privateCount} private SSH-gated)`);
+
   ctx.ui.notify(`Zendy Status:\n${lines.join("\n")}`, hasIssue ? "error" : "info");
 }
 

package/extensions/tools.ts

@@ -6,6 +6,7 @@ import { Type } from "typebox";
 import * as zendesk from "../dist/clients/zendesk.js";
 import * as helm from "../dist/clients/helm-watchdog.js";
 import * as kg from "../dist/clients/zendesk-kg.js";
+import { getConfig } from "../dist/config/store.js";
 
 // IMPORTANT: only `content` is sent to the model; `details` is UI/extension
 // metadata the model never sees (verified empirically against pi 0.79). Any
@@ -248,15 +249,26 @@ function registerSourceTools(pi: ExtensionAPI): void {
   pi.registerTool({
     name: "zendy_source_status",
     label: "Zendy Source Status",
-    description: "Report the zendy source-analysis workspace path and whether source cloning is authorized.",
-    promptSnippet: "Check source workspace status with zendy_source_status.",
+    description: "Report the zendy source-analysis workspace path, bundled source repositories, and source-cloning authorization rules.",
+    promptSnippet: "Check source workspace and repo registry with zendy_source_status.",
     parameters: Type.Object({}),
     async execute() {
       const workspace = process.env["ZENDY_SRC_DIR"] ?? null;
-      const note = "Source cloning/search requires explicit user permission per zendy workflow rules. Ask before cloning private source.";
+      const repos = getConfig().sourceRepos ?? {};
+      const repoLines = Object.entries(repos).map(([name, repo]) => {
+        const visibility = repo.visibility ?? "public";
+        const access = visibility === "private" ? "SSH access required" : "public";
+        return `- ${name}: ${repo.url} (${access})${repo.description ? ` — ${repo.description}` : ""}`;
+      });
+      const note = "Source cloning/search requires explicit user permission per zendy workflow rules. Private Enterprise repos are SSH-gated; clone failures usually mean the user lacks GitHub access.";
       return textResult(
-        `Source workspace: ${workspace ?? "(not active — created on session start)"}\n${note}`,
-        { workspace, note },
+        [
+          `Source workspace: ${workspace ?? "(not active — created on session start)"}`,
+          "Configured source repositories:",
+          repoLines.length ? repoLines.join("\n") : "- (none configured)",
+          note,
+        ].join("\n"),
+        { workspace, repos, note },
       );
     },
   });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tplog/pi-zendy",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Pi package for Dify Enterprise support ticket analysis",
   "repository": {
     "type": "git",

package/skills/zendy/SKILL.md

@@ -25,7 +25,7 @@ support engineer can analyze a ticket end-to-end without leaving the terminal.
 | `zendy_whoami` | Verify which Zendesk account is authenticated |
 | `zendy_helm_get` | Dify Helm chart data by exact version: values.yaml, images, validation, latest |
 | `zendy_kg_search` | Semantic search over historical tickets; returns ticketIds |
-| `zendy_source_status` | Check the source-analysis workspace path and authorization rules |
+| `zendy_source_status` | Check the source-analysis workspace, bundled repo registry, and authorization rules |
 
 Use these tools for all data access. Do not use zcli, curl, or any external Zendesk
 CLI. If credentials are missing, tell the user to run `/zendy-config`; check
@@ -55,6 +55,8 @@ connectivity with `/zendy-status`.
 - **Source code analysis requires explicit user permission.** If config-level
   analysis cannot settle the question, ask the user whether to check the source
   (e.g. "需要我去源码确认吗？") — never clone without permission. Use
-  `zendy_source_status` to find the workspace.
+  `zendy_source_status` to find the workspace and bundled source repo URLs.
+  Enterprise backend/frontend repos are SSH-gated; if cloning fails, ask the user
+  to confirm their GitHub SSH access rather than trying alternate credentials.
 - **Inspect before filtering.** On the first call to an unfamiliar response shape,
   look at the structure before writing filter expressions; never assume field names.