@vibe-forge/workspace-assets 0.9.1 → 0.9.2-alpha.0

package/__tests__/__snapshots__/workspace-assets-rich.snapshot.json

@@ -467,7 +467,7 @@
       ]
     },
     "options": {
-      "systemPrompt": "<system-prompt>\nThe project system rules are:\n# review\n\n> 必须检查发布改动的回归风险。\n\n# demo/security\n\n> Use when: 插件安全规则\n> Rule file path: node_modules/@vibe-forge/plugin-demo/rules/security.md\n> Only read this rule file when the task matches the scenario above.\n</system-prompt>\n\n\n<system-prompt>\nThe following skill modules are loaded for the project:\n# research\n\n> Skill description: 检索资料\n> Skill file path: .ai/skills/research/SKILL.md\n> Resolve relative paths in the resource content relative to the directory containing this skill file.\n\n<skill-content>\n先阅读 README.md，再补充结论。\n</skill-content>\n</system-prompt>\n\n\n<system-prompt>\nThe project includes the following entities:\n  - architect: 负责拆解方案的实体\n\nWhen solving user problems, you may specify entities through `vibe-forge.StartTasks` as needed and have them coordinate multiple entity types to complete the work; use `GetTaskInfo` and `wait` to track progress when needed.\n</system-prompt>\n\n\n\n\n<system-prompt>\nYou are a professional project execution manager who can skillfully direct other entities to work toward your goal. Expectations:\n\n- Never complete code development work alone\n- You must coordinate other developers to complete tasks\n- You must keep them aligned with the goal and verify that their completion reports meet the requirements\n\nChoose the appropriate workflow based on the user's needs and the actual development goal, and resolve the matching definition by workflow identifier.\n- Pass the identifier based on the actual need. This is not a path; use the standard workflow-loading capability to resolve it.\n- Decide how to pass parameters based on their descriptions and actual usage scenarios.\nThe project includes the following workflows:\n- Workflow name: release\n  - Description: 正式发布流程\n  - Identifier: release\n  - Parameters:\n    - None\n\n- Workflow name: demo/release\n  - Description: 插件发布流程\n  - Identifier: demo/release\n  - Parameters:\n    - None\n\n</system-prompt>\n\n\n执行正式发布，并整理变更摘要。",
+      "systemPrompt": "<system-prompt>\nThe project system rules are:\n# review\n\n> 必须检查发布改动的回归风险。\n\n# demo/security\n\n> Use when: 插件安全规则\n> Rule file path: node_modules/@vibe-forge/plugin-demo/rules/security.md\n> Only read this rule file when the task matches the scenario above.\n</system-prompt>\n\n\n<system-prompt>\nThe following skill modules are loaded for the project:\n# research\n\n> Skill description: 检索资料\n> Skill file path: .ai/skills/research/SKILL.md\n> Resolve relative paths in the resource content relative to the directory containing this skill file.\n\n<skill-content>\n先阅读 README.md，再补充结论。\n</skill-content>\n</system-prompt>\n\n\n<system-prompt>\nThe project includes the following entities:\n  - architect: 负责拆解方案的实体\n\nWhen solving user problems, you may specify entities through `vibe-forge.StartTasks` as needed and have them coordinate multiple entity types to complete the work; use `GetTaskInfo` and `wait` to track progress.\n</system-prompt>\n\n\n\n\n<system-prompt>\nYou are a professional project execution manager who can skillfully direct other entities to work toward your goal. Expectations:\n\n- Never complete code development work alone\n- You must coordinate other developers to complete tasks\n- You must keep them aligned with the goal and verify that their completion reports meet the requirements\n\nChoose the appropriate workflow based on the user's needs and the actual development goal, and use the workflow identifier to locate and load the corresponding definition.\n- Pass the identifier based on the actual need. This is not a path; use the standard workflow loading capability to resolve it.\n- Decide how to pass parameters based on their descriptions and actual usage scenarios.\nThe project includes the following workflows:\n- Workflow name: release\n  - Description: 正式发布流程\n  - Identifier: release\n  - Parameters:\n    - None\n\n- Workflow name: demo/release\n  - Description: 插件发布流程\n  - Identifier: demo/release\n  - Parameters:\n    - None\n\n</system-prompt>\n\n\n执行正式发布，并整理变更摘要。",
       "tools": {
         "include": [
           "Edit",

package/__tests__/prompt-builders.spec.ts

@@ -113,6 +113,8 @@ describe('workspace asset prompt builders', () => {
     expect(prompt).toContain('Workflow name: release')
     expect(prompt).toContain('Identifier: release')
     expect(prompt).toContain('    - version: 版本号')
+    expect(prompt).toContain('use the workflow identifier to locate and load the corresponding definition')
+    expect(prompt).not.toContain('load-spec')
   })
 
   it('builds spec route prompts without exposing file paths', () => {
@@ -144,6 +146,8 @@ describe('workspace asset prompt builders', () => {
     expect(prompt).toContain('Description: 发布流程')
     expect(prompt).toContain('Identifier: release')
     expect(prompt).toContain('    - version: 版本号')
+    expect(prompt).toContain('use the workflow identifier to locate and load the corresponding definition')
+    expect(prompt).not.toContain('load-spec')
     expect(prompt).not.toContain('professional project execution manager')
     expect(prompt).not.toContain('.ai/specs/release/index.md')
     expect(prompt).not.toContain('internal')
@@ -169,6 +173,10 @@ describe('workspace asset prompt builders', () => {
     ])
 
     expect(prompt).toContain('reviewer: 负责代码审查')
+    expect(prompt).toContain('`vibe-forge.StartTasks`')
+    expect(prompt).toContain('`GetTaskInfo`')
+    expect(prompt).toContain('`wait`')
+    expect(prompt).not.toContain('run-tasks')
     expect(prompt).not.toContain('需要关注变更风险')
     expect(prompt).not.toContain('hidden')
   })

package/__tests__/selection-internal.spec.ts

@@ -0,0 +1,42 @@
+import { describe, expect, it } from 'vitest'
+
+import type { WorkspaceAssetBundle } from '@vibe-forge/types'
+
+import { resolveSelectedMcpNames } from '#~/selection-internal.js'
+
+const createBundle = (): WorkspaceAssetBundle => ({
+  cwd: '/tmp/workspace',
+  pluginConfigs: [],
+  pluginInstances: [],
+  assets: [],
+  rules: [],
+  specs: [],
+  entities: [],
+  skills: [],
+  hookPlugins: [],
+  opencodeOverlayAssets: [],
+  defaultIncludeMcpServers: [],
+  defaultExcludeMcpServers: ['TypeScriptLanguageService'],
+  mcpServers: {
+    TypeScriptLanguageService: {
+      kind: 'mcpServer',
+      id: 'mcp:TypeScriptLanguageService',
+      scope: 'workspace',
+      name: 'TypeScriptLanguageService',
+      displayName: 'TypeScriptLanguageService',
+      source: '/tmp/workspace/.ai.config.json',
+      command: 'node',
+      args: ['tslspmcp']
+    }
+  }
+})
+
+describe('resolveSelectedMcpNames', () => {
+  it('lets an explicit include override default excludes', () => {
+    const selected = resolveSelectedMcpNames(createBundle(), {
+      include: ['TypeScriptLanguageService']
+    })
+
+    expect(selected).toEqual(['TypeScriptLanguageService'])
+  })
+})

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibe-forge/workspace-assets",
-  "version": "0.9.1",
+  "version": "0.9.2-alpha.0",
   "description": "Workspace asset resolution and adapter asset planning for Vibe Forge",
   "imports": {
     "#~/*.js": {
@@ -29,10 +29,10 @@
     "fast-glob": "^3.3.3",
     "front-matter": "^4.0.2",
     "js-yaml": "^4.1.1",
-    "@vibe-forge/config": "^0.9.0",
+    "@vibe-forge/utils": "^0.9.0",
+    "@vibe-forge/definition-core": "^0.9.0",
     "@vibe-forge/types": "^0.9.0",
-    "@vibe-forge/utils": "^0.9.1",
-    "@vibe-forge/definition-core": "^0.9.0"
+    "@vibe-forge/config": "^0.9.1-alpha.0"
   },
   "devDependencies": {
     "@types/js-yaml": "^4.0.9"

package/src/prompt-builders.ts

@@ -155,8 +155,8 @@ export const generateSpecRoutePrompt = (
     : ''
 
   return (
-    `<system-prompt>\n${activeIdentityPrompt}Choose the appropriate workflow based on the user's needs and the actual development goal, and resolve the matching definition by workflow identifier.\n` +
-    '- Pass the identifier based on the actual need. This is not a path; use the standard workflow-loading capability to resolve it.\n' +
+    `<system-prompt>\n${activeIdentityPrompt}Choose the appropriate workflow based on the user's needs and the actual development goal, and use the workflow identifier to locate and load the corresponding definition.\n` +
+    '- Pass the identifier based on the actual need. This is not a path; use the standard workflow loading capability to resolve it.\n' +
     '- Decide how to pass parameters based on their descriptions and actual usage scenarios.\n' +
     'The project includes the following workflows:\n' +
     `${specsRouteStr}\n` +
@@ -178,7 +178,7 @@ export const generateEntitiesRoutePrompt = (entities: Definition<Entity>[]) => {
         })
         .join('')
     }\n` +
-    'When solving user problems, you may specify entities through `vibe-forge.StartTasks` as needed and have them coordinate multiple entity types to complete the work; use `GetTaskInfo` and `wait` to track progress when needed.\n' +
+    'When solving user problems, you may specify entities through `vibe-forge.StartTasks` as needed and have them coordinate multiple entity types to complete the work; use `GetTaskInfo` and `wait` to track progress.\n' +
     '</system-prompt>\n'
   )
 }

package/src/selection-internal.ts

@@ -219,7 +219,11 @@ export const resolveSelectedMcpNames = (
   const includeRefs = selection?.include ??
     (bundle.defaultIncludeMcpServers.length > 0 ? bundle.defaultIncludeMcpServers : undefined)
   const excludeRefs = selection?.exclude ??
-    (bundle.defaultExcludeMcpServers.length > 0 ? bundle.defaultExcludeMcpServers : undefined)
+    (
+      selection?.include == null && bundle.defaultExcludeMcpServers.length > 0
+        ? bundle.defaultExcludeMcpServers
+        : undefined
+    )
 
   const resolveRefs = (refs: string[] | undefined) => {
     if (refs == null || refs.length === 0) return undefined