wave-agent-sdk 1.2.0 → 1.3.0

package/dist/prompts/memoryTypes.js

@@ -0,0 +1,191 @@
+/**
+ * Auto-memory taxonomy and shared prompt sections.
+ *
+ * These sections are shared by the main agent's memory prompt
+ * (`prompts/autoMemory.ts`) and the background extraction fork prompt
+ * (`prompts/autoMemoryExtraction.ts`). Sharing them is load-bearing, not
+ * tidiness: the fork reuses the main system prompt, so both texts land in the
+ * same request — a duplicated copy that drifts turns into a request that
+ * simultaneously tells the model to save and not to save the same category.
+ *
+ * Aligned with Claude Code's `memdir/memoryTypes.ts`, individual-only variant
+ * (no `<scope>` tags, no private/team split: Wave has a single memory
+ * directory).
+ */
+import { MEMORY_ENTRYPOINT_NAME, MEMORY_INDEX_LINE_GUIDANCE_CHARS, MEMORY_TYPES, MAX_MEMORY_ENTRYPOINT_CHARS, MAX_MEMORY_ENTRYPOINT_LINES, } from "../constants/memory.js";
+/**
+ * Appended to the memory directory line. Shipped because the model was burning
+ * turns on `ls` / `mkdir -p` before writing; the harness guarantees the
+ * directory exists (`MemoryService.ensureAutoMemoryDirectory`).
+ */
+export const DIR_EXISTS_GUIDANCE = "This directory already exists — write to it directly with the Write tool (do not run mkdir or check for its existence).";
+/**
+ * `## Types of memory` section.
+ */
+export const TYPES_SECTION = [
+    "## Types of memory",
+    "",
+    "There are several discrete types of memory that you can store in your memory system:",
+    "",
+    "<types>",
+    "<type>",
+    "    <name>user</name>",
+    "    <description>Contain information about the user's role, goals, responsibilities, and knowledge. Great user memories help you tailor your future behavior to the user's preferences and perspective. Your goal in reading and writing these memories is to build up an understanding of who the user is and how you can be most helpful to them specifically. For example, you should collaborate with a senior software engineer differently than a student who is coding for the very first time. Keep in mind, that the aim here is to be helpful to the user. Avoid writing memories about the user that could be viewed as a negative judgement or that are not relevant to the work you're trying to accomplish together.</description>",
+    "    <when_to_save>When you learn any details about the user's role, preferences, responsibilities, or knowledge</when_to_save>",
+    "    <how_to_use>When your work should be informed by the user's profile or perspective. For example, if the user is asking you to explain a part of the code, you should answer that question in a way that is tailored to the specific details that they will find most valuable or that helps them build their mental model in relation to domain knowledge they already have.</how_to_use>",
+    "    <examples>",
+    "    user: I'm a data scientist investigating what logging we have in place",
+    "    assistant: [saves user memory: user is a data scientist, currently focused on observability/logging]",
+    "",
+    "    user: I've been writing Go for ten years but this is my first time touching the React side of this repo",
+    "    assistant: [saves user memory: deep Go expertise, new to React and this project's frontend — frame frontend explanations in terms of backend analogues]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>feedback</name>",
+    "    <description>Guidance the user has given you about how to approach work — both what to avoid and what to keep doing. These are a very important type of memory to read and write as they allow you to remain coherent and responsive to the way you should approach work in the project. Record from failure AND success: if you only save corrections, you will avoid past mistakes but drift away from approaches the user has already validated, and may grow overly cautious.</description>",
+    '    <when_to_save>Any time the user corrects your approach ("no not that", "don\'t", "stop doing X") OR confirms a non-obvious approach worked ("yes exactly", "perfect, keep doing that", accepting an unusual choice without pushback). Corrections are easy to notice; confirmations are quieter — watch for them. In both cases, save what is applicable to future conversations, especially if surprising or not obvious from the code. Include *why* so you can judge edge cases later.</when_to_save>',
+    "    <how_to_use>Let these memories guide your behavior so that the user does not need to offer the same guidance twice.</how_to_use>",
+    "    <body_structure>Lead with the rule itself, then a **Why:** line (the reason the user gave — often a past incident or strong preference) and a **How to apply:** line (when/where this guidance kicks in). Knowing *why* lets you judge edge cases instead of blindly following the rule.</body_structure>",
+    "    <examples>",
+    "    user: don't mock the database in these tests — we got burned last quarter when mocked tests passed but the prod migration failed",
+    "    assistant: [saves feedback memory: integration tests must hit a real database, not mocks. Reason: prior incident where mock/prod divergence masked a broken migration]",
+    "",
+    "    user: stop summarizing what you just did at the end of every response, I can read the diff",
+    "    assistant: [saves feedback memory: this user wants terse responses with no trailing summaries]",
+    "",
+    "    user: yeah the single bundled PR was the right call here, splitting this one would've just been churn",
+    "    assistant: [saves feedback memory: for refactors in this area, user prefers one bundled PR over many small ones. Confirmed after I chose this approach — a validated judgment call, not a correction]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>project</name>",
+    "    <description>Information that you learn about ongoing work, goals, initiatives, bugs, or incidents within the project that is not otherwise derivable from the code or git history. Project memories help you understand the broader context and motivation behind the work the user is doing within this working directory.</description>",
+    '    <when_to_save>When you learn who is doing what, why, or by when. These states change relatively quickly so try to keep your understanding of this up to date. Always convert relative dates in user messages to absolute dates when saving (e.g., "Thursday" → "2026-03-05"), so the memory remains interpretable after time passes.</when_to_save>',
+    "    <how_to_use>Use these memories to more fully understand the details and nuance behind the user's request and make better informed suggestions.</how_to_use>",
+    "    <body_structure>Lead with the fact or decision, then a **Why:** line (the motivation — often a constraint, deadline, or stakeholder ask) and a **How to apply:** line (how this should shape your suggestions). Project memories decay fast, so the why helps future-you judge whether the memory is still load-bearing.</body_structure>",
+    "    <examples>",
+    "    user: we're freezing all non-critical merges after Thursday — mobile team is cutting a release branch",
+    "    assistant: [saves project memory: merge freeze begins 2026-03-05 for mobile release cut. Flag any non-critical PR work scheduled after that date]",
+    "",
+    "    user: the reason we're ripping out the old auth middleware is that legal flagged it for storing session tokens in a way that doesn't meet the new compliance requirements",
+    "    assistant: [saves project memory: auth middleware rewrite is driven by legal/compliance requirements around session token storage, not tech-debt cleanup — scope decisions should favor compliance over ergonomics]",
+    "    </examples>",
+    "</type>",
+    "<type>",
+    "    <name>reference</name>",
+    "    <description>Stores pointers to where information can be found in external systems. These memories allow you to remember where to look to find up-to-date information outside of the project directory.</description>",
+    "    <when_to_save>When you learn about resources in external systems and their purpose. For example, that bugs are tracked in a specific project in Linear or that feedback can be found in a specific Slack channel.</when_to_save>",
+    "    <how_to_use>When the user references an external system or information that may be in an external system.</how_to_use>",
+    "    <examples>",
+    '    user: check the Linear project "INGEST" if you want context on these tickets, that\'s where we track all pipeline bugs',
+    '    assistant: [saves reference memory: pipeline bugs are tracked in Linear project "INGEST"]',
+    "",
+    "    user: the Grafana board at grafana.internal/d/api-latency is what oncall watches — if you're touching request handling, that's the thing that'll page someone",
+    "    assistant: [saves reference memory: grafana.internal/d/api-latency is the oncall latency dashboard — check it when editing request-path code]",
+    "    </examples>",
+    "</type>",
+    "</types>",
+    "",
+];
+/**
+ * `## What NOT to save in memory` section. The closing paragraph is the
+ * explicit-save gate: it applies even when the user asks for something the
+ * model would otherwise happily record, which is exactly the case where
+ * activity-log noise gets in.
+ */
+export const WHAT_NOT_TO_SAVE_SECTION = [
+    "## What NOT to save in memory",
+    "",
+    "- Code patterns, conventions, architecture, file paths, or project structure — these can be derived by reading the current project state.",
+    "- Git history, recent changes, or who-changed-what — `git log` / `git blame` are authoritative.",
+    "- Debugging solutions or fix recipes — the fix is in the code; the commit message has the context.",
+    "- Anything already documented in CLAUDE.md files.",
+    "- Ephemeral task details: in-progress work, temporary state, current conversation context.",
+    "",
+    "These exclusions apply even when the user explicitly asks you to save. If they ask you to save a PR list or activity summary, ask what was *surprising* or *non-obvious* about it — that is the part worth keeping.",
+];
+/**
+ * Recall-side drift caveat, a single bullet under `## When to access memories`.
+ */
+export const MEMORY_DRIFT_CAVEAT = "- Memory records can become stale over time. Use memory as context for what was true at a given point in time. Before answering the user or building assumptions based solely on information in memory records, verify that the memory is still correct and up-to-date by reading the current state of the files or resources. If a recalled memory conflicts with current information, trust what you observe now — and update or remove the stale memory rather than acting on it.";
+/**
+ * `## When to access memories` section, including the drift caveat.
+ *
+ * The "ignore" bullet is deliberate: without it the model tends to treat
+ * "ignore memory about X" as "acknowledge memory about X, then override it",
+ * and mentions the memory anyway.
+ */
+export const WHEN_TO_ACCESS_SECTION = [
+    "## When to access memories",
+    "- When memories seem relevant, or the user references prior-conversation work.",
+    "- You MUST access memory when the user explicitly asks you to check, recall, or remember.",
+    "- If the user says to *ignore* or *not use* memory: proceed as if MEMORY.md were empty. Do not apply remembered facts, cite, compare against, or mention memory content.",
+    MEMORY_DRIFT_CAVEAT,
+];
+/**
+ * `## Before recommending from memory` section. Header wording is deliberate:
+ * the action cue at the decision point works where an abstract header
+ * ("Trusting what you recall") does not.
+ */
+export const TRUSTING_RECALL_SECTION = [
+    "## Before recommending from memory",
+    "",
+    "A memory that names a specific function, file, or flag is a claim that it existed *when the memory was written*. It may have been renamed, removed, or never merged. Before recommending it:",
+    "",
+    "- If the memory names a file path: check the file exists.",
+    "- If the memory names a function or flag: grep for it.",
+    "- If the user is about to act on your recommendation (not just asking about history), verify first.",
+    "",
+    '"The memory says X exists" is not the same as "X exists now."',
+    "",
+    "A memory that summarizes repo state (activity logs, architecture snapshots) is frozen in time. If the user asks about *recent* or *current* state, prefer `git log` or reading the code over recalling the snapshot.",
+];
+/**
+ * `## Memory and other forms of persistence` section: how memory divides
+ * labor with plans and tasks.
+ */
+export const MEMORY_AND_OTHER_PERSISTENCE_SECTION = [
+    "## Memory and other forms of persistence",
+    "Memory is one of several persistence mechanisms available to you as you assist the user in a given conversation. The distinction is often that memory can be recalled in future conversations and should not be used for persisting information that is only useful within the scope of the current conversation.",
+    "- When to use or update a plan instead of memory: If you are about to start a non-trivial implementation task and would like to reach alignment with the user on your approach you should use a Plan rather than saving this information to memory. Similarly, if you already have a plan within the conversation and you have changed your approach persist that change by updating the plan rather than saving a memory.",
+    "- When to use or update tasks instead of memory: When you need to break your work in current conversation into discrete steps or keep track of your progress use tasks instead of saving to memory. Tasks are great for persisting information about the work that needs to be done in the current conversation, but memory should be reserved for information that will be useful in future conversations.",
+    "",
+];
+/**
+ * Frontmatter format example with the `type` field.
+ */
+export const MEMORY_FRONTMATTER_EXAMPLE = [
+    "```markdown",
+    "---",
+    "name: {{memory name}}",
+    "description: {{one-line description — used to decide relevance in future conversations, so be specific}}",
+    `type: {{${MEMORY_TYPES.join(", ")}}}`,
+    "---",
+    "",
+    "{{memory content — for feedback/project types, structure as: rule/fact, then **Why:** and **How to apply:** lines}}",
+    "```",
+];
+/**
+ * `## How to save memories` section: the two-step write (topic file, then
+ * index pointer) plus the entrypoint rules.
+ */
+export function buildHowToSaveSection() {
+    return [
+        "## How to save memories",
+        "",
+        "Saving a memory is a two-step process:",
+        "",
+        "**Step 1** — write the memory to its own file (e.g., `user_role.md`, `feedback_testing.md`) using this frontmatter format:",
+        "",
+        ...MEMORY_FRONTMATTER_EXAMPLE,
+        "",
+        `**Step 2** — add a pointer to that file in \`${MEMORY_ENTRYPOINT_NAME}\`. \`${MEMORY_ENTRYPOINT_NAME}\` is an index, not a memory — each entry should be one line, under ~${MEMORY_INDEX_LINE_GUIDANCE_CHARS} characters: \`- [Title](file.md) — one-line hook\`. It has no frontmatter. Never write memory content directly into \`${MEMORY_ENTRYPOINT_NAME}\`.`,
+        "",
+        `- \`${MEMORY_ENTRYPOINT_NAME}\` is always loaded into your conversation context — lines after ${MAX_MEMORY_ENTRYPOINT_LINES} or characters past ${MAX_MEMORY_ENTRYPOINT_CHARS} will be truncated, so keep the index concise`,
+        "- Keep the name, description, and type fields in memory files up-to-date with the content",
+        "- Organize memory semantically by topic, not chronologically",
+        "- Update or remove memories that turn out to be wrong or outdated",
+        "- Do not write duplicate memories. First check if there is an existing memory you can update before writing a new one.",
+    ];
+}

package/dist/services/GitService.d.ts

@@ -8,6 +8,13 @@ export declare class GitService {
      * Clones a Git repository to a local path
      */
     clone(urlOrRepo: string, targetPath: string, ref?: string): Promise<void>;
+    /**
+     * Checks out a specific commit in an existing clone.
+     *
+     * Needed by marketplace plugin sources that pin a `sha` (spec plugin A-021):
+     * `clone -b <ref>` only guarantees the branch, not the exact commit.
+     */
+    checkout(targetPath: string, sha: string): Promise<void>;
     /**
      * Pulls the latest changes in a local repository
      */

package/dist/services/GitService.js

@@ -53,6 +53,29 @@ export class GitService {
             throw this.handleGitError(urlOrRepo, error);
         }
     }
+    /**
+     * Checks out a specific commit in an existing clone.
+     *
+     * Needed by marketplace plugin sources that pin a `sha` (spec plugin A-021):
+     * `clone -b <ref>` only guarantees the branch, not the exact commit.
+     */
+    async checkout(targetPath, sha) {
+        if (process.env.VITEST && !process.env.ALLOW_REAL_GIT) {
+            throw new Error(`Real git checkout is disabled in tests. Path: ${targetPath}, Sha: ${sha}`);
+        }
+        if (!(await this.isGitAvailable())) {
+            throw new Error("Git is not installed or not found in PATH. Please install Git to use Git/GitHub marketplaces.");
+        }
+        try {
+            await execFileAsync("git", ["-C", targetPath, "checkout", "--detach", sha], {
+                env: { ...process.env, LC_ALL: "C" },
+                timeout: this.getTimeout(),
+            });
+        }
+        catch (error) {
+            throw this.handleGitError(sha, error);
+        }
+    }
     /**
      * Pulls the latest changes in a local repository
      */

package/dist/services/MarketplaceService.d.ts

@@ -1,4 +1,4 @@
-import { KnownMarketplace, KnownMarketplacesRegistry, InstalledPlugin, InstalledPluginsRegistry, MarketplaceManifest, MarketplaceSource } from "../types/marketplace.js";
+import { KnownMarketplace, KnownMarketplacesRegistry, InstalledPlugin, InstalledPluginsRegistry, MarketplaceManifest, MarketplaceSource, PluginInstallLocation } from "../types/marketplace.js";
 import { ConfigurationService } from "./configurationService.js";
 import type { Scope } from "../types/configuration.js";
 /**
@@ -11,7 +11,18 @@ import type { Scope } from "../types/configuration.js";
  * known_marketplaces.json is kept as a cache for installLocation/lastUpdated metadata.
  */
 export declare class MarketplaceService {
-    private static isLockedInProcess;
+    /**
+     * 已持有市场操作锁的调用链标记（重入判据）。
+     *
+     * 用 AsyncLocalStorage 而不是进程内布尔值：锁内发起的嵌套调用（如
+     * refreshMarketplaces → updateMarketplace → installPlugin）必须跳过再次加锁，
+     * 否则会自锁；但**另一条并发调用链**必须老老实实排队。布尔值无法区分这两者
+     * ——第二个并发调用会以为「已在锁内」而跳过锁直接执行，于是两个操作并行改同一
+     * 个市场检出（并发两次 `git pull` 同一检出必然失败，spec 插件市场 场景 14）。
+     */
+    private static readonly lockChain;
+    /** In-flight [refreshMarketplaces] call (single-flight, spec 插件市场 场景 13). */
+    private refreshInFlight;
     private pluginsDir;
     private knownMarketplacesPath;
     private installedPluginsPath;
@@ -49,7 +60,7 @@ export declare class MarketplaceService {
     private isStaleLock;
     /**
      * Acquires a file-based lock (with PID tracking for stale lock detection) and executes the provided function.
-     * Supports re-entrancy within the same process.
+     * Supports re-entrancy within the same call chain (see [lockChain]).
      */
     private withLock;
     /**
@@ -78,6 +89,21 @@ export declare class MarketplaceService {
      * Saves the installed plugins registry
      */
     saveInstalledPlugins(registry: InstalledPluginsRegistry): Promise<void>;
+    /**
+     * Whether an install record belongs to the given install location.
+     *
+     * Records written before scopes were tracked carry no `scope`; they stand for
+     * "installed once on this machine" and match any scope, so uninstalling them
+     * keeps working (they are that plugin's only record). They still match by
+     * project path, so records of two different projects stay distinguishable.
+     */
+    private matchesInstallLocation;
+    /**
+     * The install location a record is keyed by. Scope-less legacy records are
+     * treated as user-scope when they have to be re-created (e.g. by an update).
+     */
+    private locationOf;
+    private describeInstallLocations;
     /**
      * Loads a marketplace manifest from a local path
      */
@@ -94,6 +120,18 @@ export declare class MarketplaceService {
      * Finds which scope declared a marketplace (user, project, local, or builtin)
      */
     getMarketplaceDeclaringSource(name: string): Scope | "builtin" | null;
+    /**
+     * 已注册的市场（作用域配置 + 缓存注册表合并去重），用于添加前的判重
+     */
+    private listRegisteredMarketplaces;
+    /**
+     * 添加市场前判重（spec ecosystem/plugin「设置页插件市场」场景 16）：来源重复或
+     * 清单声明的名称与已有市场同名时不允许添加。只传 source 时仅判来源（用于克隆
+     * 之前，避免为一个已存在的来源白克隆一次）。
+     */
+    private assertMarketplaceAddable;
+    /** 两个市场来源是否指向同一处（同类型比 url/repo/path，忽略 ref） */
+    private static isSameMarketplaceSource;
     /**
      * Adds a new marketplace (local directory, GitHub repo, or Git URL)
      */
@@ -114,28 +152,74 @@ export declare class MarketplaceService {
     private uninstallPluginsByMarketplace;
     /**
      * Updates a specific marketplace or all marketplaces
+     *
+     * `refreshCheckout` (default true) pulls the checkout from its upstream; pass
+     * false to upgrade plugins against the current checkout only — the interactive
+     * "批量更新插件" path does that, because opening the plugin-marketplace surface
+     * already refreshed the checkout (spec 插件市场 A-013).
+     *
+     * Returns the number of installed plugins whose version actually changed
+     * during this run (0 = everything was already up to date) — the GUI hosts
+     * use it to tell "已更新 N 个插件" apart from "已是最新" (spec 插件市场 场景 13).
      */
     updateMarketplace(name?: string, options?: {
         updatePlugins?: boolean;
-    }): Promise<void>;
-    /**
-     * Automatically updates all marketplaces that have auto-update enabled
-     */
-    autoUpdateAll(): Promise<void>;
-    /**
-     * Toggles auto-update for a marketplace
-     */
-    toggleAutoUpdate(name: string, enabled: boolean): Promise<void>;
+        refreshCheckout?: boolean;
+    }): Promise<number>;
+    /**
+     * 交互界面的「批量更新插件」：按当前清单把该市场内所有已安装且有新版本的插件
+     * 升级到最新，**不拉取检出**——清单的新鲜度由打开插件市场界面时的那次刷新保证
+     * （spec 插件市场 A-013/场景 14）。检出尚未据此刷新的场景（无界面可依赖的非交互
+     * 命令）走 [updateMarketplace] 的默认行为。
+     */
+    updateMarketplacePlugins(name?: string): Promise<number>;
+    /**
+     * Refreshes the local checkout of every registered marketplace.
+     *
+     * Callers are the plugin-marketplace surfaces (GUI settings view / CLI plugin
+     * manager), refreshed when the user opens them — the agent-startup path no
+     * longer refreshes anything (spec 插件市场 A-013 场景 5).
+     *
+     * This is a fixed behavior with no opt-in/opt-out: `autoUpdate` no longer
+     * exists, so all marketplaces are refreshed alike (A-014). Refreshing only
+     * updates the checkout — installed plugins are never reinstalled here, so a
+     * newer plugin version surfaces as an explicit "更新" (per plugin) /
+     * "批量更新插件" (batch) action instead of being applied behind the user's
+     * back.
+     *
+     * Single-flight: a call landing while a refresh is running reuses it instead
+     * of pulling every checkout twice (spec 场景 13).
+     */
+    refreshMarketplaces(): Promise<void>;
     /**
      * Installs a plugin from a marketplace
+     *
+     * @param location 该次安装记账的位置（spec plugin A-015）。缺省只在内部调用
+     *   （宿主加载时补装）出现，此时写入一条不带作用域的历史形态记录。
      */
-    installPlugin(pluginAtMarketplace: string, projectPath?: string): Promise<InstalledPlugin>;
+    installPlugin(pluginAtMarketplace: string, location?: PluginInstallLocation): Promise<InstalledPlugin>;
     /**
      * Uninstalls a plugin
-     */
-    uninstallPlugin(pluginAtMarketplace: string, projectPath?: string): Promise<void>;
-    /**
-     * Updates a plugin (uninstall followed by install)
+     *
+     * With a [location], only that scope's install record is removed — other
+     * scopes (including other projects' project/local records) keep theirs, and
+     * the shared cache directory is deleted only once no record references it
+     * (spec plugin A-015). Without one, every record of the plugin is removed
+     * (used by [updatePlugin] and the marketplace-level cleanup).
+     */
+    uninstallPlugin(pluginAtMarketplace: string, location?: PluginInstallLocation): Promise<void>;
+    /**
+     * Moves a plugin's install record to another location（「更换安装作用域」）:
+     * the record currently at [from] (or the plugin's only record when [from] is
+     * omitted or unknown) is rewritten to [to], so that uninstalling the plugin
+     * at its new scope still finds it (spec plugin A-015). A duplicate record
+     * already at [to] wins and the moved one is dropped.
+     */
+    relocatePlugin(pluginAtMarketplace: string, from: PluginInstallLocation | undefined, to: PluginInstallLocation): Promise<void>;
+    /**
+     * Updates a plugin (uninstall followed by install). Every install record of
+     * the plugin is re-created at its original location, so the install scopes
+     * stay unchanged (spec plugin「设置页插件市场」场景 12 / A-015).
      */
     updatePlugin(pluginAtMarketplace: string): Promise<InstalledPlugin>;
 }