chore: change ownership

[ahmed-agabani-snyk]

Description

Changes ownership

Checklist

• Tests added and all succeed
• Linted
• README.md updated, if user-facing

🚨After having merged, please update the snyk-ls and CLI go.mod to pull in latest client.

[CLAassistant]

All committers have signed the CLA.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues
✅	Secrets	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Breaking Auth Change 🟠 [major] Renaming the authentication environment variable from SMOKE_TEST_TOKEN to SNYK_TOKEN without a fallback is a breaking change for local development and downstream projects (e.g., snyk-ls, Snyk CLI) that use this utility. Existing environments with SMOKE_TEST_TOKEN set will now silently fail to authenticate, as the code falls back to generating a random UUID (which will result in 401/403 errors from the Snyk API) instead of using the provided legacy token. token := os.Getenv("SNYK_TOKEN") Opaque Test Config 🟡 [minor] Changing the hardcoded organization UUID while simultaneously removing the documentation in CONTRIBUTING.md that specified the target environment (app.dev.snyk.io) makes the test suite's requirements opaque. This makes it difficult for contributors to diagnose authorization failures or set up their own tokens with correct permissions for the new organization. return "81c4528c-665a-43da-a0a7-581277288bf3"

📚 Repository Context Analyzed This review considered 4 relevant code sections from 4 files (average relevance: 0.74) http/http.go (lines 1-206) config/mocks/config.go (lines 1-106) SUPPORT.md (lines 1-5) CONTRIBUTING.md (lines 1-203)

🤖 Repository instructions applied (from AGENTS.md)

[minsiyang]

We might want to migrate this as some point. This repo is achieved, we should use https://github.com/uber-go/mock

[minsiyang]

🚀