Update download buttons to point to VS Code Marketplace listing page

[aj47]

Summary

Changed the /vsx redirect destination from the direct .vspackage download URL to the VS Code Marketplace listing page:

Before: https://marketplace.visualstudio.com/_apis/public/gallery/publishers/augment/vsextensions/vscode-augment/latest/vspackage

After: https://marketplace.visualstudio.com/items?itemName=augment.vscode-augment

Changes

• vercel.json — updated /vsx redirect destination
• next.config.js — updated /vsx redirect destination

All three "Download Extension" buttons (desktop nav, mobile menu, and primary CTA) use href="/vsx", so they all now point to the Marketplace listing page.

---

Pull Request opened by Augment Code with guidance from the PR author

Summary by CodeRabbit

• Chores
  • Updated redirect configuration for the VS Code extension marketplace integration to point to the current marketplace endpoint.

[coderabbitai]

📝 Walkthrough

Walkthrough

The /vsx redirect destination was updated in both next.config.js and vercel.json configuration files to point to the VS Marketplace items URL for the augment.vscode-augment extension instead of the previous vspackage endpoint URL.

Changes

Cohort / File(s)	Summary
Configuration Redirects next.config.js, vercel.json	Updated /vsx path redirect destination from VS Marketplace vspackage API endpoint to marketplace items URL (augment.vscode-augment).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A path once wandered, now takes a new turn,
From vspackage to items, the knowledge we learn,
Augment finds its home in the Marketplace bright,
Two configs aligned, everything's right! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating redirect URLs from direct download endpoints to the VS Code Marketplace listing page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Docstrings were successfully generated.

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Docstrings generation - FAILED

No docstrings were generated.