a0fafedfa0
VS Code is a net-new EoS runtime that — unlike every prior migration — is NOT CLI-installed (Marketplace/VSIX extension). It has zero runtime==='vscode' branches in bin/install.js and stays that way (regression-guarded); it is driven entirely through the negotiated imperative Host-Integration adapter. Registry + validator (the hard part): - capabilities/vscode/capability.json (role:runtime): full hostIntegration block (imperative / palette / active vscode.lm model / engine hook bus / sandboxed-storage / mcp transport / sandboxed-web runtime; dispatch nested, maxDepth 5 per VS Code's documented subagent depth). - capability-validator.cjs extended so a role:runtime capability can legitimately declare "extension-distributed, no config directory": new configHome.kind:'none' + installSurface:'none' (+ GATE-A pairing + the parity maps), with localConfigDir and configHome.name made conditional on kind!=='none'. All 18 runtimes still validate; getDirName returns a distinct sentinel (not '.claude') for a no-config runtime. - The add-a-registry-runtime tax: NON_INSTALLABLE_RUNTIMES exemption in the runtime-flags drift guard, vscode added to global-config-home SPECIAL_CASED, EXPECTED_PROFILES.vscode='ide', and the config-adapter/derivation/pin-count guards updated. No golden-install fixture, model-catalog, or CONFIGURATION rows (vscode never enters allRuntimes). Dispatch + extension surface: - Fixed vscode/extension.js's createHub()-no-args bug (every dispatch was UnknownCommand, masked by a vacuous reachability test) — now reuses the shared dispatchGsdCommand subprocess-shim (Node/desktop); the reachability test is tightened to assert real dispatch. - Promoted the #1933 host binding to a shipped vscode/host-binding.js; activate() now composes the model/hookBus/stateIO seams through it. Corrected the model seam to VS Code's real API (vscode.lm.selectChatModels() -> model.sendRequest(); vscode.lm.sendRequest does not exist) so the binding actually composes on real desktop VS Code instead of throwing. - New vscode/browser.js Web Extension entry with ZERO Node APIs (the engine's config/capability loading is Node-bound, so the web entry registers the surface and directs full dispatch to the native MCP server — honestly documented). - UPGRADE 1: GSD skills as native Language Model Tools (contributes.languageModelTools + vscode.lm.registerTool), invoke() dispatching through the hub. - UPGRADE 2: native subagent dispatch wired onto #runSubagent / chat.subagents.allowInvocationsFromSubagents (fail-soft on API availability, maxDepth 5 enforced). - vscode/package.json: browser entry, engines.vscode ^1.105, chatParticipants + languageModelTools contributions; fixed a stale activationPoints->activationEvents manifest key. Added "vscode" to the package files array. Docs (## vscode matrix section) + changeset (Added). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
86 lines
2.6 KiB
JSON
86 lines
2.6 KiB
JSON
{
|
|
"name": "gsd-core-vscode",
|
|
"displayName": "GSD Core",
|
|
"description": "GSD orchestration engine embedded in VS Code (ADR-1239 IDE profile).",
|
|
"version": "1.7.0-rc.5",
|
|
"publisher": "opengsd",
|
|
"engines": {
|
|
"vscode": "^1.105.0"
|
|
},
|
|
"categories": [
|
|
"Other"
|
|
],
|
|
"activationEvents": [
|
|
"onCommand:gsd.invoke"
|
|
],
|
|
"main": "./extension.js",
|
|
"browser": "./browser.js",
|
|
"contributes": {
|
|
"commands": [
|
|
{
|
|
"command": "gsd.invoke",
|
|
"title": "GSD: Invoke Command"
|
|
}
|
|
],
|
|
"chatParticipants": [
|
|
{
|
|
"id": "gsd",
|
|
"name": "gsd",
|
|
"fullName": "GSD Core",
|
|
"description": "Invoke GSD orchestration commands from chat.",
|
|
"isSticky": true
|
|
}
|
|
],
|
|
"languageModelTools": [
|
|
{
|
|
"name": "gsd_progress",
|
|
"tags": ["gsd", "status"],
|
|
"toolReferenceName": "gsd-progress",
|
|
"displayName": "GSD Progress",
|
|
"modelDescription": "Reports GSD milestone/phase progress (percent complete, plan and summary counts) for the current project.",
|
|
"userDescription": "Check GSD project progress.",
|
|
"canBeReferencedInPrompt": true,
|
|
"inputSchema": {
|
|
"type": "object",
|
|
"properties": {},
|
|
"additionalProperties": false
|
|
}
|
|
},
|
|
{
|
|
"name": "gsd_workstreams",
|
|
"tags": ["gsd", "status"],
|
|
"toolReferenceName": "gsd-workstreams",
|
|
"displayName": "GSD Workstreams",
|
|
"modelDescription": "Lists the GSD parallel workstreams for the current project (or reports flat/single-workstream mode).",
|
|
"userDescription": "List GSD workstreams.",
|
|
"canBeReferencedInPrompt": true,
|
|
"inputSchema": {
|
|
"type": "object",
|
|
"properties": {},
|
|
"additionalProperties": false
|
|
}
|
|
},
|
|
{
|
|
"name": "gsd_plan_phase",
|
|
"tags": ["gsd", "plan"],
|
|
"toolReferenceName": "gsd-plan-phase",
|
|
"displayName": "GSD Plan Phase",
|
|
"modelDescription": "Looks up the plan index (plans, waves, checkpoints) for a named GSD phase. Read-only — does not create or modify a phase plan; use the /gsd-plan-phase chat workflow for full phase planning.",
|
|
"userDescription": "Look up a GSD phase's plan index.",
|
|
"canBeReferencedInPrompt": true,
|
|
"inputSchema": {
|
|
"type": "object",
|
|
"properties": {
|
|
"phase": {
|
|
"type": "string",
|
|
"description": "The GSD phase name to look up (e.g. \"01-core\")."
|
|
}
|
|
},
|
|
"required": ["phase"],
|
|
"additionalProperties": false
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|