Summary

Method 5 (Multi-Root Workspace) in the HVE Core installer skill and documentation uses VS Code folder display names (the "name" field from .code-workspace files) as path prefixes in chat.*Locations settings. These display names are UI labels for the Explorer sidebar and do not resolve on the filesystem, causing all agent, prompt, instruction, and skill paths to fail silently.

Root Cause

In a .code-workspace file, each folder entry has two fields:

The Method 5 templates used the "name" value (e.g., HVE-Core Fork/.github/agents/ado) as the path prefix in settings like chat.agentFilesLocations, chat.promptFilesLocations, chat.instructionsFilesLocations, and chat.agentSkillsLocations. No directory named "HVE-Core Fork" exists on disk, so VS Code cannot resolve those paths.

Evidence

All five other installation methods use actual filesystem paths and work correctly:

• Method 1 (Peer Clone): ../hve-core/.github/agents/ado
• Method 2 (Git-Ignored): .hve-core/.github/agents/ado
• Method 3 (Submodule): hve-core/.github/agents/ado
• Method 4 (Codespaces): /workspaces/hve-core/.github/agents/ado
• Method 6 (Mounted): ../.hve-core/.github/agents/ado

Method 5 was the only method using folder display names instead of filesystem paths.

Affected Files

• .github/skills/installer/hve-core-installer/SKILL.md — Method 5 installation section and method comparison table
• docs/getting-started/methods/multi-root.md — Workspace settings examples, path resolution table, and troubleshooting section

Fix

Replace folder display names with actual clone paths in both files:

• Codespaces/Devcontainers: Use absolute path /workspaces/hve-core
• Local VS Code: Use relative path from the workspace file to the clone location (e.g., ../../hve-core)

Update the path resolution documentation to mark folder display names as unreliable and recommend filesystem paths exclusively.