Add context7.json with URL and public key

[gimlichael]

This pull request adds a new configuration file, context7.json, which contains a URL and a public key for the bootstrapper service. This change prepares the project for integration with the external Context7 service.

Configuration update:

• Added context7.json file with url and public_key fields for Context7 bootstrapper integration.

Summary by CodeRabbit

• Chores
  • Added new configuration settings to support platform operations.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

A new configuration file context7.json has been introduced containing URL and public key parameters. This appears to be a simple data addition with no logic modifications or functional changes to existing code.

Changes

Cohort / File(s)	Summary
Configuration Addition context7.json	New JSON file added with two top-level fields: url (pointing to a context7 endpoint) and public_key (cryptographic key identifier).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A config file hops into view,
With URL and key, shiny and new,
Four simple lines, pristine and bright,
Context seven brings bootstrapper's light! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gimlichael-patch-1

---

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.}

[Copilot]

Pull request overview

Adds a new repository-level configuration file to support upcoming integration between the bootstrapper service and the external Context7 service.

Changes:

• Added context7.json containing the Context7 endpoint URL.
• Added a public_key value intended for Context7 bootstrapper integration.

[Copilot]

The public_key value appears to be a credential-like identifier (e.g., pk_…) committed directly into the repo. If Context7 treats this as an API/publishable key that can be abused (quota, attribution, etc.), it should be provided via a secret/env var or injected at deploy time (and this file should be a template/sample). If it is truly intended to be public, please add a brief note/justification (and consider scoping/rotating it) so we don't accidentally leak a sensitive key here.

Suggested change

	"public_key": "pk_ZYmd0ipMJCtW5NudkKPxA"
	"public_key": "YOUR_CONTEXT7_PUBLIC_KEY_HERE"