chore(convolens): db logical names + env defaults (PR 4/5)

[JustAGhosT]

Summary

PR 4 of 5 in the convolens rename. Decouples the Cosmos logical database name from the Azure resource-naming prefix so the brand rename can land without renaming any Azure resources.

Changes (4 files, +15/-10)

• `apps/api/.env.example` — header → ConvoLens; `DB_NAME`, `AZURE_COSMOS_DATABASE`, `AZURE_SQL_DATABASE` example values → `convolens`
• `apps/web/.env.example` — header → ConvoLens
• `apps/api/src/config/azure/index.ts` — `AZURE_COSMOS_DATABASE` fallback → `'convolens'`
• `infra/bicep/main.bicep` — header → ConvoLens; new param `databaseName` defaulting to `'convolens'`, wired into Cosmos module (was `databaseName: projectName`)

Azure resource names — intentionally unchanged

`rg-whatssummarize-`, `kvwhatssummarizedev`, `cosmos-whatssummarize-dev`, `oai-whatssummarize-dev`, etc. all stay. Separate Azure rename decision is queued. `infra/scripts/` PROJECT_NAME also unchanged for the same reason — those drive resource lookups, not naming logic.

Production deploy note

The Bicep change deploys a new `convolens` Cosmos database on the existing `cosmos-whatssummarize-dev` account. Any prod env currently pointing app config at `DB_NAME=whatssummarize` needs an explicit override at deploy time until the data migrates over.

Test plan

• `az bicep build --file infra/bicep/main.bicep` succeeds (syntax)
• `az deployment group what-if` (against existing `rg-whatssummarize-dev`) shows only the new `databaseName` param and Cosmos DB diff — no resource-group / app-service / KV renames
• `pnpm --filter @convolens/api typecheck` passes
• `.env.example` keys match what `apps/api/src/config/*` reads

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@JustAGhosT has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 1 second before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c58d2348-b9a5-45f8-bbc0-a9535604b8c7

📥 Commits

Reviewing files that changed from the base of the PR and between f2f15dd and 2888a66.

📒 Files selected for processing (4)

• apps/api/.env.example
• apps/api/src/config/azure/index.ts
• apps/web/.env.example
• infra/bicep/main.bicep

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/convolens-env-config

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}