fix(vscode-readme): use repo-relative paths for gifs in extensions\vscode\README.md

[supreethmv]

…code/README.md

Description

Updated four gif image links in README.md to use ../../docs/images/*.gif so the gifs render correctly when viewing the README from the extensions/vscode folder.

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• I've read the contributing guide
• The relevant docs have been updated (extensions/vscode/README.md)
• The relevant tests, if any, have been updated or created

Screen recording or screenshot

Before:

Now:

Tests

[ What tests were added or updated to ensure the changes work as expected? ]
None — documentation link fix only.

---

Summary by cubic

Fix broken GIFs in the VS Code extension README by switching to repo‑relative paths. Updated four links to ../../docs/images/*.gif so images render correctly when viewing README in extensions/vscode.

^{Written for commit 8f70f7b. Summary will update automatically on new commits.}

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[supreethmv]

I have read the CLA Document and I hereby sign the CLA.

[cubic-dev-ai]

No issues found across 1 file

[Patrick-Erichsen]

thanks for the catch!

[Patrick-Erichsen]

Actually there is a reason they are relatively linked like they currently are, the above is the screenshot on the actual marketplace. I believe when we are actually bundling the extension the pathing is different than when developing.

@supreethmv , to be clear, you're only seeing this issue when viewing the local codebase?

[Patrick-Erichsen]

see above

[supreethmv]

Actually there is a reason they are relatively linked like they currently are, the above is the screenshot on the actual marketplace. I believe when we are actually bundling the extension the pathing is different than when developing.

@supreethmv , to be clear, you're only seeing this issue when viewing the local codebase?

@Patrick-Erichsen thank you for the clarification. The issue is not just locally, the problem persists also when viewing the repo at https://github.com/continuedev/continue/tree/main/extensions/vscode