fix(docs): use actual clone paths instead of folder display names in multi-root workspace settings

[katriendg]

Multi-root workspace chat.*Locations settings previously used folder display names (e.g., "HVE-Core Fork/.github/agents/ado") as path prefixes, but VS Code does not resolve these reliably. This PR replaces all folder-name-based prefixes with actual filesystem paths — absolute paths for Codespaces/Devcontainer environments and relative paths for local VS Code — and restructures the documentation to call out this distinction clearly.

Description

Documentation update

The multi-root workspace setup guide was restructured to address the path resolution reliability issue reported in #983.

Folder display names label roots in the Explorer sidebar but do not resolve reliably as path prefixes in chat.*Locations settings.

• Replaced all "HVE-Core Fork/..." prefixes in multi-root.md with absolute paths (/workspaces/hve-core/...) for the Codespaces / Devcontainer configuration example.
• Added a new Local VS Code section with a complete .code-workspace configuration using relative paths (../../hve-core/...), expanded from the previous minimal snippet.
• Added an [!IMPORTANT] callout at the top of the workspace creation step warning that folder display names do not resolve reliably.
• Restructured the Path Resolution table to recommend absolute paths for Codespaces, relative paths for local development, and mark folder names as unreliable.
• Updated the troubleshooting entry to reflect the corrected guidance.

Copilot skill

• Updated the Method 5 summary table in SKILL.md to show "Actual clone path" instead of "Per workspace file" for the settings prefix column.
• Split the single workspace example into separate codespaces and local variants with distinct HTML comment markers (method-5-workspace-codespaces, method-5-workspace-local).

Related Issue(s)

Fixes #983

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)
• Copilot skill (.github/skills/*/SKILL.md)

Note for AI Artifact Contributors:

• Agents: Research, indexing/referencing other project (using standard VS Code GitHub Copilot/MCP tools), planning, and general implementation agents likely already exist. Review .github/agents/ before creating new ones.
• Skills: Must include both bash and PowerShell scripts. See Skills.
• Model Versions: Only contributions targeting the latest Anthropic and OpenAI models will be accepted. Older model versions (e.g., GPT-3.5, Claude 3) will be rejected.
• See Agents Not Accepted and Model Version Requirements.

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Sample Prompts (for AI Artifact Contributions)

User Request:

Execution Flow:

Output Artifacts:

Success Indicators:

For detailed contribution requirements, see:

• Common Standards: docs/contributing/ai-artifacts-common.md - Shared standards for XML blocks, markdown quality, RFC 2119, validation, and testing
• Agents: docs/contributing/custom-agents.md - Agent configurations with tools and behavior patterns
• Prompts: docs/contributing/prompts.md - Workflow-specific guidance with template variables
• Instructions: docs/contributing/instructions.md - Technology-specific standards with glob patterns
• Skills: docs/contributing/skills.md - Task execution utilities with cross-platform scripts

Testing

• Markdown linting (npm run lint:md): Passed
• Spell checking (npm run spell-check): Passed
• Frontmatter validation (npm run lint:frontmatter): Passed
• Skill structure validation (npm run validate:skills): Passed
• Link validation (npm run lint:md-links): Passed
• PowerShell analysis (npm run lint:ps): Passed
• Plugin freshness (npm run plugin:generate): Passed
• Security analysis: No credentials, tokens, or sensitive data in changes. No dependency modifications. No privilege scope changes.
• Diff-based assessment: All chat.*Locations settings consistently use filesystem paths across both modified files. Merge conflict with upstream security-planning -> security rename resolved correctly with no stale references remaining.
• Manual testing was not performed.

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable) (N/A — documentation-only change with no API surface)
• Tests added for new functionality (if applicable) (N/A — documentation-only change)

AI Artifact Contributions

• Used /prompt-analyze to review contribution
• Addressed all feedback from prompt-builder review
• Verified contribution follows common standards and type-specific requirements

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Skill structure validation: npm run validate:skills
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps
• Plugin freshness: npm run plugin:generate

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues (N/A — no dependency changes)
• Security-related scripts follow the principle of least privilege (N/A — no security script changes)

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None