Summary

The hve-core-installer agent's Method 5 (Multi-Root Workspace) was generating workspace settings using folder display names as path prefixes, which VS Code cannot resolve.

Problem

VS Code's toAbsoluteLocations() method only handles:

• Absolute paths: Used directly
• Relative paths: Resolved against workspace folder roots

It does NOT perform variable substitution for folder display names.

Broken Configuration

"chat.modeFilesLocations": {
  "HVE-Core Library/.github/chatmodes": true,
  "My Project/.github/chatmodes": true
}

VS Code treats HVE-Core Library/.github/chatmodes as a literal directory path, not as a reference to the folder named "HVE-Core Library".

Solution

Replace folder display name prefixes with explicit relative paths:

"chat.modeFilesLocations": {
  ".github/chatmodes": true,
  "../hve-core/.github/chatmodes": true
}

Changes Required

1. Update Method 5 PowerShell workspace script with correct paths
2. Update Method 5 Bash workspace script with correct paths
3. Add explanatory comments about path resolution behavior
4. Add missing technical terms to cspell dictionary (notmatch, popd, pushd, toplevel)

Acceptance Criteria

• Method 5 uses explicit relative paths instead of folder display names
• Both PowerShell and Bash examples are updated
• Comments explain why folder display names cannot be used
• All linting and spell checks pass