feat: pass OpenAI agent settings to Lightsail API

[BeforeLights]

What changed

• pass OPENAI_API_KEY and the server-controlled OpenAI agent settings only to the Lightsail API container
• keep OpenAI disabled by default and keep the example environment file free of key material
• document the protected /opt/databreeze/.env setup and add deployment assertions

Why

The deployed Lightsail Compose profile previously did not pass the OpenAI credential or agent flag into the API, so adding the key to the protected server environment could not activate the server-side agent. The GitHub workflow still never uploads /opt/databreeze/.env or the key.

Validation

• docker compose --env-file infrastructure/lightsail/.env.example -f infrastructure/lightsail/compose.pilot.yml config --quiet
• targeted Lightsail OpenAI configuration assertions
• Prettier check
• git diff --check

The repository-pinned Node test command was blocked locally because this desktop's dependency shim reports pnpm 11.19.0 while the repository requires 11.18.0; the equivalent assertions and Compose validation passed.

[coderabbitai]

Warning

Review limit reached

@BeforeLights, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2ce487b3-ed31-463c-a9bf-7ddd959a552b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a4ff2d and d9e828d.

📒 Files selected for processing (4)

• infrastructure/lightsail/.env.example
• infrastructure/lightsail/README.md
• infrastructure/lightsail/compose.pilot.yml
• tools/repo-cli/test/lightsail-deployment.test.mjs

---

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