feat: Add API key integration for VSCode Void, Antigravity IDE, and AnythingLLM

[ghost]

Opened by @roomote-v0 on behalf of ALAN PERRY JR

Summary

This PR adds comprehensive API key integration setup for three development tools:

• VSCode Void
• Antigravity IDE
• AnythingLLM

Changes Made

✅ Created .env.example with all required API key templates
✅ Added .gitignore to protect sensitive data and credentials
✅ Created config/api-integrations.json with API endpoints and settings
✅ Added comprehensive API Integration Guide in docs/API_INTEGRATION_GUIDE.md
✅ Added Security Policy in docs/SECURITY.md
✅ Updated README with quick start guide and integration instructions

Key Features

• Environment Configuration: Template for all required API keys
• Security: Proper gitignore rules to prevent credential leaks
• Documentation: Complete setup guides for all three integrations
• Configuration: JSON-based API endpoint and feature management
• Best Practices: Security guidelines and troubleshooting tips

How to Use

1. Copy .env.example to .env
2. Add your API keys from each platform
3. Follow the detailed guides in docs/API_INTEGRATION_GUIDE.md

---

View task on Roo Code Cloud

[ghost]

Rooviewer   Follow task

Review complete. Flagged a few doc/config issues that could cause setup confusion or non-reproducible installs.

• Stop ignoring JS lockfiles in .gitignore (or document why), to keep installs reproducible
• Fix README install/run steps so they match actual repo entrypoints (no package.json / main.py yet)
• Clarify placeholder semantics for AnythingLLM endpoints (:slug substitution)
• Fix docs/API_INTEGRATION_GUIDE.md fenced block language (bash vs JSON/JSONC)

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[ghost]

Ignoring lockfiles makes installs non-reproducible across machines and CI, since the resolved dependency tree can drift over time. Lockfiles are typically committed, so consider removing them from .gitignore.

Suggested change

	package-lock.json
	yarn.lock
	pnpm-lock.yaml
	# Lockfiles (commit these for reproducible installs)
	# package-lock.json
	# yarn.lock
	# pnpm-lock.yaml

_{Fix it with Roo Code or mention @roomote and request a fix.}

[ghost]

npm install / npm start and python main.py are presented as runnable steps, but there is no package.json or main.py in this branch, so following the README currently dead-ends. Consider rephrasing these as future/placeholder steps or linking to the actual entrypoint once the app scaffold exists.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[ghost]

The AnythingLLM endpoints use a :slug placeholder, but the config file does not describe how substitution is performed (and this placeholder format is not universal). If another part of the code expects {slug} or performs simple string concatenation, this will break requests. Consider documenting placeholder semantics in this JSON or switching to a clearer token format.

_{Fix it with Roo Code or mention @roomote and request a fix.}

[ghost]

In the "Connection Timeout" section, the fenced block is labeled bash but contains JSON plus // comments, which is not valid JSON and can mislead copy/paste. Consider changing the fence to jsonc (or removing comments and using json) so the example is accurate.

_{Fix it with Roo Code or mention @roomote and request a fix.}