IDE slash-command palette doesn't index newly-added symlinked skills until window reload

Description

After adding a new Agent Skill to a project (via a marketplace-style symlink under .claude/skills/<name> pointing to .agents/skills/<name>/SKILL.md, tracked in skills-lock.json), the skill does not appear in the VSCode extension's / slash-command autocomplete palette — even after running /reload-skills.

Reproduction

1. In a project already using the .agents/skills/ + .claude/skills/<name> symlink + skills-lock.json pattern for marketplace skills (this repo already has postmark, ai-sdk, workflow-init set up this way and they show up fine).
2. Add a new skill following the same pattern (new dir under .agents/skills/<new-skill>/SKILL.md, symlink under .claude/skills/<new-skill>, entry added to skills-lock.json).
3. In the same IDE session, type / in the chat input and search for the new skill's name.
4. Observed: The new skill is not listed in the "Slash Commands" palette, even though it does appear correctly in the model-facing available-skills list (confirmed via the Skill tool's tool definitions / <system-reminder>).
5. Run /reload-skills — output confirms the skill is loaded (e.g. "Reloaded skills: 236 skills available (no changes)"), but the slash-command palette still doesn't show it.
6. Workaround: Run "Developer: Reload Window" in VSCode (full window/extension reload). After this, the skill appears correctly in the palette.

Expected behavior

/reload-skills (or an equivalent lightweight refresh) should also invalidate/rebuild the IDE extension's client-side slash-command palette index, not just the model-facing Skill-tool registry, so a full window reload isn't required to see a newly added skill as a slash command.

Environment

• Claude Code VSCode extension
• Skill added as a symlink (.claude/skills/<name> → ../../.agents/skills/<name>), matching the existing pattern used by other marketplace skills in the same repo that do show up correctly once indexed.

Additional notes

Skills that were already committed/indexed in a prior session (e.g. workflow-init, added ~30 minutes earlier in the same day but in an earlier session) showed up fine. Only the skill added live in the current session was missing from the palette until a full window reload — suggesting the palette index is built once at extension activation/workspace load rather than being live-refreshed.