docs: update all documentation for accuracy and rename

- Rename all "Kolya BR Proxy" references to "BR Enterprise Proxy"
- Fix token hashing: docs incorrectly claimed PBKDF2 (actual: SHA256)
- Fix timeout values in performance docs (read_timeout=3600, keep_alive=3700)
- Fix cache write multiplier: add 2.0x for 1h TTL (default)
- Add RBAC and Teams sections to security docs
- Update testing guide with all test files
- Fix deployment log examples (module name)

Author: Chao Huang

docs/api-reference.md

@@ -1,6 +1,6 @@
 # API Reference
 
-Kolya BR Proxy exposes four API groups:
+BR Enterprise Proxy exposes four API groups:
 
 | Group | Prefix | Auth | Purpose |
 |-------|--------|------|---------|

docs/api-reference.zh.md

@@ -1,6 +1,6 @@
 # API 参考
 
-Kolya BR Proxy 提供四组 API：
+BR Enterprise Proxy 提供四组 API：
 
 | 分组 | 前缀 | 认证方式 | 用途 |
 |------|------|----------|------|

docs/architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-Comprehensive architecture documentation for Kolya BR Proxy -- an AI Gateway that provides both OpenAI-compatible and Anthropic Messages API access to AWS Bedrock models (Claude, Nova, DeepSeek, Mistral, Llama, etc.) and Google Gemini models via the native generateContent API.
+Comprehensive architecture documentation for BR Enterprise Proxy -- an AI Gateway that provides both OpenAI-compatible and Anthropic Messages API access to AWS Bedrock models (Claude, Nova, DeepSeek, Mistral, Llama, etc.) and Google Gemini models via the native generateContent API.
 
 ---
 

docs/architecture.zh.md

@@ -1,6 +1,6 @@
 # 架构文档
 
-Kolya BR Proxy 综合架构文档 -- 一个提供 OpenAI 兼容 API 和 Anthropic Messages API 访问 AWS Bedrock 模型（Claude、Nova、DeepSeek、Mistral、Llama 等）以及通过原生 generateContent API 访问 Google Gemini 模型的 AI 网关。
+BR Enterprise Proxy 综合架构文档 -- 一个提供 OpenAI 兼容 API 和 Anthropic Messages API 访问 AWS Bedrock 模型（Claude、Nova、DeepSeek、Mistral、Llama 等）以及通过原生 generateContent API 访问 Google Gemini 模型的 AI 网关。
 
 ---
 

docs/deployment.md

@@ -1,4 +1,4 @@
-# Kolya BR Proxy — Deployment SOP
+# BR Enterprise Proxy — Deployment SOP
 
 This document covers the full deployment and teardown lifecycle on AWS EKS.
 
@@ -374,8 +374,8 @@ When no token context is available the field shows `[-]`.
 Example output:
 
 ```
-2026-04-11 08:23:01,234 - kolya_br_proxy.router - INFO - [my-team-key] streaming request to us-west-2
-2026-04-11 08:23:05,678 - kolya_br_proxy.router - WARNING - [-] health check from unknown caller
+2026-04-11 08:23:01,234 - app.router - INFO - [my-team-key] streaming request to us-west-2
+2026-04-11 08:23:05,678 - app.router - WARNING - [-] health check from unknown caller
 ```
 
 ---

docs/deployment.zh.md

@@ -1,4 +1,4 @@
-# Kolya BR Proxy — 部署 SOP
+# BR Enterprise Proxy — 部署 SOP
 
 本文档涵盖 AWS EKS 上的完整部署和销毁流程。
 
@@ -374,8 +374,8 @@ Terraform workspace（`prod` vs 其他）决定资源规格：
 输出示例：
 
 ```
-2026-04-11 08:23:01,234 - kolya_br_proxy.router - INFO - [my-team-key] streaming request to us-west-2
-2026-04-11 08:23:05,678 - kolya_br_proxy.router - WARNING - [-] health check from unknown caller
+2026-04-11 08:23:01,234 - app.router - INFO - [my-team-key] streaming request to us-west-2
+2026-04-11 08:23:05,678 - app.router - WARNING - [-] health check from unknown caller
 ```
 
 ---

docs/kolya_ask.md

@@ -103,7 +103,7 @@ When conversation history approaches the context limit, Claude Code uses Haiku t
 
 ```
 INFO: Waiting for application startup.
-10:18:22 - Starting Kolya BR Proxy...
+10:18:22 - Starting BR Enterprise Proxy...
          - Database engine initialized, tables created/verified
          - Rate limiter: Redis distributed mode, global 8.33 req/s (500 RPM),
            burst=10, local fallback 2.78 req/s (÷3 pods)
@@ -134,7 +134,7 @@ INFO: Waiting for application startup.
              Update model pricing from AWS (02:00 UTC)
              Update Gemini model pricing from Google (02:30 UTC)
          - Pricing update scheduler started
-         - Kolya BR Proxy started successfully
+         - BR Enterprise Proxy started successfully
 
 INFO: Application startup complete.
 INFO: Uvicorn running on http://0.0.0.0:8000

docs/kolya_ask.zh.md

@@ -103,7 +103,7 @@ Claude Code 会定期用 `smallFastModel` 把对话内容写入 `MEMORY.md`，
 
 ```
 INFO: 等待应用启动
-10:18:22 - 启动 Kolya BR Proxy...
+10:18:22 - 启动 BR Enterprise Proxy...
          - 数据库引擎初始化、表创建/验证完成
          - 限流器：Redis 分布式模式，全局 8.33 req/s（500 RPM），burst=10
            本地 fallback 2.78 req/s（÷3 pods）
@@ -132,7 +132,7 @@ INFO: 等待应用启动
              从 AWS 更新模型定价（02:00 UTC）
              从 Google 更新 Gemini 模型定价（02:30 UTC）
          - 定价更新调度器已启动
-         - Kolya BR Proxy 启动成功
+         - BR Enterprise Proxy 启动成功
 
 INFO: 应用启动完成
 INFO: Uvicorn 运行在 http://0.0.0.0:8000

docs/oauth-setup.md

@@ -1,6 +1,6 @@
 # OAuth Setup Guide
 
-Kolya BR Proxy uses OAuth exclusively for authentication (no local username/password). Two OAuth providers are supported:
+BR Enterprise Proxy uses OAuth exclusively for authentication (no local username/password). Two OAuth providers are supported:
 
 - **AWS Cognito** (default/recommended) -- AWS-managed user pool authentication
 - **Microsoft Entra ID** (Azure AD) -- personal and enterprise Microsoft accounts
@@ -21,7 +21,7 @@ Cognito is the default provider selected during deployment via `deploy-all.sh`.
 1. Under your User Pool, go to **App integration** > **App client** > **Create app client**.
 2. Select **Confidential client** (server-side).
 3. Set:
-   - **App client name**: `Kolya BR Proxy`
+   - **App client name**: `BR Enterprise Proxy`
    - **Generate client secret**: Yes
    - **Allowed callback URLs**: `http://localhost:3000/auth/cognito/callback`
      - For production, add `https://<your-domain>/auth/cognito/callback`
@@ -131,7 +131,7 @@ Frontend                     Backend                      Cognito
 
 1. Go to [Azure Portal > App registrations](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps) and click **New registration**.
 2. Fill in:
-   - **Name**: `Kolya BR Proxy`
+   - **Name**: `BR Enterprise Proxy`
    - **Supported account types**: "Accounts in any organizational directory and personal Microsoft accounts" (multi-tenant)
    - **Redirect URI**: Platform `Web`, URI `http://localhost:3000/auth/microsoft/callback`
      - For production, add `https://<your-domain>/auth/microsoft/callback`
@@ -143,7 +143,7 @@ Frontend                     Backend                      Cognito
 ### Step 2: Create Client Secret
 
 1. Go to **Certificates & secrets** > **New client secret**.
-2. Set description (e.g. `Kolya BR Proxy Secret`) and expiry (up to 24 months).
+2. Set description (e.g. `BR Enterprise Proxy Secret`) and expiry (up to 24 months).
 3. Click **Add** and immediately copy the **Value** (shown only once).
 
 ### Step 3: Configure API Permissions

docs/oauth-setup.zh.md

@@ -1,6 +1,6 @@
 # OAuth 配置指南
 
-Kolya BR Proxy 仅使用 OAuth 进行认证（不支持本地用户名/密码）。支持两种 OAuth 提供商：
+BR Enterprise Proxy 仅使用 OAuth 进行认证（不支持本地用户名/密码）。支持两种 OAuth 提供商：
 
 - **AWS Cognito**（默认/推荐）-- AWS 托管的用户池认证
 - **Microsoft Entra ID**（Azure AD）-- 个人和企业 Microsoft 账户
@@ -21,7 +21,7 @@ Cognito 是通过 `deploy-all.sh` 部署时默认选择的认证提供商。两
 1. 在用户池下，进入 **应用集成** > **应用客户端** > **创建应用客户端**。
 2. 选择 **机密客户端**（服务端）。
 3. 设置：
-   - **应用客户端名称**：`Kolya BR Proxy`
+   - **应用客户端名称**：`BR Enterprise Proxy`
    - **生成客户端密钥**：是
    - **允许的回调 URL**：`http://localhost:3000/auth/cognito/callback`
      - 生产环境添加 `https://<your-domain>/auth/cognito/callback`
@@ -131,7 +131,7 @@ aws cognito-idp admin-set-user-password \
 
 1. 访问 [Azure 门户 > 应用注册](https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps)，点击 **新注册**。
 2. 填写以下信息：
-   - **名称**：`Kolya BR Proxy`
+   - **名称**：`BR Enterprise Proxy`
    - **支持的帐户类型**：「任何组织目录中的帐户和个人 Microsoft 帐户」（多租户）
    - **重定向 URI**：平台选 `Web`，URI 为 `http://localhost:3000/auth/microsoft/callback`
      - 生产环境另外添加 `https://<your-domain>/auth/microsoft/callback`
@@ -143,7 +143,7 @@ aws cognito-idp admin-set-user-password \
 ### 步骤二：创建客户端密钥
 
 1. 进入 **证书和密码** > **新客户端密码**。
-2. 设置说明（如 `Kolya BR Proxy Secret`）和有效期（最长 24 个月）。
+2. 设置说明（如 `BR Enterprise Proxy Secret`）和有效期（最长 24 个月）。
 3. 点击 **添加**，并立即复制 **值**（仅显示一次）。
 
 ### 步骤三：配置 API 权限