feat(mcp): pull API keys from environment at setup time

[JonZeolla]

Contributor Comments

Now if you set certain env vars at repo generation time (currently just ZENABLE_API_KEY but we plan to support more), it will auto-populate your .envrc file.

This is purposefully undocumented for now, as we test it. We will add docs when this feature goes GA

Pull Request Checklist

Thank you for submitting a contribution!

Please address the following items:

• If you are adding a dependency, please explain how it was chosen.
• If manual testing is needed in order to validate the changes, provide a testing plan and the expected results.
• Validate that documentation is accurate and aligned to any project updates or additions.=

[ai-coding-guardrails]

I've got 2 comments for you to consider

The PR title and description are not accurate. Here are my suggestions:

Title: feat(mcp): pull API keys from environment at setup time + update pre-commit config

Description: # Contributor Comments

Main Feature

Now if you set certain env vars at repo generation time (currently just ZENABLE_API_KEY but we plan to support more), it will auto-populate your .envrc file.

This is purposefully undocumented for now, as we test it. We will add docs when this feature goes GA

Additional Changes

• Updated pre-commit configuration by removing verbose flag from ruff linter and updating revision hashes

Pull Request Checklist

Thank you for submitting a contribution!

Please address the following items:

• If you are adding a dependency, please explain how it was chosen.
• If manual testing is needed in order to validate the changes, provide a testing plan and the expected results.
• Validate that documentation is accurate and aligned to any project updates or additions.

Reviewed with 🤟 by Zenable