@akira-tl/forgerelay 1.3.2 → 1.3.3

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable ForgeRelay changes are documented here.
 
 ## [Unreleased]
 
+## [1.3.3] - 2026-10-15
+
+### Fixed
+
+- `open_workspace` 现在明确区分 Host 顶层 Core tool、`capabilityCatalog` 与 `capabilityFingerprint`：`minimal` / `full` 的核心工具仍由 Host 当前 `tools/list` snapshot 决定，不再允许仅因 fingerprint/catalog 未列出 `write`、`edit` 或 `bash` 就把 ForgeRelay 判断为只读；模型可见标签也改为明确的 Capability catalog 与 semantic feature fingerprint 表述。
+
 ## [1.3.2] - 2026-10-08
 
 ### Security

package/dist/mcp/server/workspace/runtime/workspace-open-presentation.js

@@ -12,7 +12,7 @@ import { logToolCall, workspaceLogContext } from "../../core/tool-support.js";
 import { buildExecutionShellContext } from "../../../server-instructions.js";
 import { workspaceColorFor, workspaceIdentityName } from "../../../../workspace-colors.js";
 export const workspaceTaskUsageInstruction = "Use workspace.tasks proactively for work that spans multiple steps or sessions: create or update Tasks to preserve useful next steps and current state, and read its summary when resuming relevant unfinished work. Do not query it mechanically on every open_workspace call.";
-export const capabilityDiscoveryInstruction = "For capability describe/run, use only names present in capabilityCatalog. capabilityFingerprint.capabilities is a semantic feature fingerprint, not a callable registry; capabilityGuides are documentation descriptors, not callable capabilities.";
+export const capabilityDiscoveryInstruction = "Core MCP tools are separate from capabilityCatalog and capabilityFingerprint; the Host's current tools/list snapshot determines which top-level tools can be called. In toolMode=minimal or full, ForgeRelay's regular core surface is open_workspace, capability, close_workspace, read, write, edit, rename, delete, and bash. Do not infer that write, edit, or bash are unavailable merely because they are absent from capabilityCatalog or capabilityFingerprint. If an expected core tool is missing from the Host tool snapshot, treat the Host MCP metadata as stale or incomplete rather than describing ForgeRelay as read-only. For capability describe/run, use only names present in capabilityCatalog. capabilityFingerprint.capabilities is a semantic feature fingerprint, not a callable registry; capabilityGuides are documentation descriptors, not callable capabilities.";
 export async function presentLocalWorkspaceOpen(options, input, contextData) {
     const { config, forgerelayVersion: FORGERELAY_VERSION, workspaces, workspaceTasks, reviewCheckpoints, capabilityRegistry, subagentProviders, hooks, rememberWorkspacePanelState, } = options;
     const { path, workspaceId, mode, baseRef, targetBranch, newWorktree, newWorkspace, context } = input;
@@ -155,7 +155,7 @@ export async function presentLocalWorkspaceOpen(options, input, contextData) {
                     ? `Available skills: ${visibleSkills.map((skill) => skill.name).join(", ")}`
                     : undefined,
                 capabilityCatalog.length > 0
-                    ? `Optional capabilities: ${capabilityCatalog.map((entry) => entry.name).join(", ")}`
+                    ? `Capability catalog entries: ${capabilityCatalog.map((entry) => entry.name).join(", ")}`
                     : undefined,
                 visibleCapabilityGuides.length > 0
                     ? `Capability guides: ${visibleCapabilityGuides.map((guide) => guide.name).join(", ")}`
@@ -175,7 +175,7 @@ export async function presentLocalWorkspaceOpen(options, input, contextData) {
                 staleWorkspaces.length > 0
                     ? `This Workspace has been idle for more than 2 days: ${staleWorkspaces.map((stale) => `${stale.workspaceId} last-used=${stale.lastUsedAt}`).join(", ")}. It remains available to resume or explicitly close; do not clean it up automatically.`
                     : undefined,
-                `ForgeRelay ${capabilityFingerprint.version} capabilities: ${capabilityFingerprint.capabilities.join(", ")}`,
+                `ForgeRelay semantic feature fingerprint (${capabilityFingerprint.version}): ${capabilityFingerprint.capabilities.join(", ")}`,
                 instruction,
                 resourceUpdate?.text,
             ].filter(Boolean).join("\n"),

package/dist/mcp/server/workspace/runtime/workspace-open.js

@@ -503,7 +503,7 @@ async function handleOpenWorkspace(options, input, requestContext) {
                 ? `Available skills: ${relayedSkills.map((skill) => String(skill.name ?? "")).filter(Boolean).join(", ")}`
                 : undefined,
             relayedCapabilities.length > 0
-                ? `Optional capabilities: ${relayedCapabilities.map((entry) => String(entry.name ?? "")).filter(Boolean).join(", ")}`
+                ? `Capability catalog entries: ${relayedCapabilities.map((entry) => String(entry.name ?? "")).filter(Boolean).join(", ")}`
                 : undefined,
             opened.instruction,
         ].filter(Boolean).join("\n");

package/docs/configuration.md

@@ -453,7 +453,12 @@ version, tool mode, and stable semantic capability names. The fingerprint also
 reports enabled optional domains such as subagent profile discovery, native
 artifact download, MCP App UI, or aggregate `review.changes` when those
 features are actually available; it remains a semantic summary rather than a
-copy of `tools/list`.
+copy of `tools/list`. Neither `capabilityFingerprint` nor `capabilityCatalog`
+is evidence that an omitted Core tool is unavailable. The Host's current
+`tools/list` snapshot is authoritative for top-level callability; in
+`minimal` and `full`, the expected regular Core surface remains
+`open_workspace`, `capability`, `close_workspace`, `read`, `write`,
+`edit`, `rename`, `delete`, and `bash`.
 
 Bootstrap responses also return `capabilityGuides`, which are compact descriptors
 for built-in ForgeRelay documentation that the Agent can explicitly load with
@@ -466,11 +471,14 @@ context.
 
 There is no separate progressive-disclosure configuration switch. Capability
 Guide discovery is built in, while optional low-frequency actions are advertised
-through the workspace Capability catalog instead of adding top-level tools. If the
-fingerprint reports a capability that is missing from the Host's current tool
-snapshot, treat that as stale Host MCP metadata: reconnect/refresh the integration
-or use a Host context that reloads `tools/list`. The ForgeRelay process cannot
-force a Host to invalidate its cached schema.
+through the workspace Capability catalog instead of adding top-level tools. If an
+expected Core tool is missing from the Host's current tool snapshot, or the
+fingerprint reports a semantic feature that the Host metadata does not reflect,
+treat that as stale or incomplete Host MCP metadata: reconnect/refresh the
+integration or use a Host context that reloads `tools/list`. Do not describe
+ForgeRelay as read-only merely because `write`, `edit`, or `bash` is absent
+from the fingerprint or Capability catalog. The ForgeRelay process cannot force
+a Host to invalidate its cached schema.
 
 ### LSP code intelligence
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akira-tl/forgerelay",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "description": "Local development control plane for MCP coding agents.",
   "type": "module",
   "homepage": "https://github.com/Akira-TL/forgerelay#readme",