docs: add bilingual Codex guides and improve GitHub documentation

Author: denven

README.md

@@ -167,24 +167,24 @@ Process identity, PID/parent relationships, and creation-time validation belong
 
 ## 4. Runtime Overview
 
-```mermaid
-flowchart LR
-    U[Lark User] --> B[lark-channel-bridge]
-    B --> S[Lark scope / Session binding]
-    S --> C[Codex CLI]
-
-    W[Windows Terminal / codex3] --> C2[Codex CLI]
-    C2 --> R[Codex rollout JSONL]
-
-    A[Attach-CodexObserver.ps1] --> R
-    A --> O[Watch-CodexSession.ps1]
-    A --> RA[Watch-CodexRelease.ps1]
-
-    O --> M[.codex-monitor/status]
-    RA --> Q[release request/result]
-
-    B --> M
-    B --> Q
+```mermaid
+flowchart LR
+    U["Lark User"] --> B["lark-channel-bridge"]
+    B --> S["Lark scope / Session binding"]
+    S --> C["Codex CLI"]
+
+    W["Windows Terminal / codex3"] --> C2["Codex CLI"]
+    C2 --> R["Codex rollout JSONL"]
+
+    A["Attach-CodexObserver.ps1"] --> R
+    A --> O["Watch-CodexSession.ps1"]
+    A --> RA["Watch-CodexRelease.ps1"]
+
+    O --> M[".codex-monitor/status"]
+    RA --> Q["release request/result"]
+
+    B --> M
+    B --> Q
 ```
 
 See [local-docs/02-lark-bridge-codex-architecture.md](./local-docs/02-lark-bridge-codex-architecture.md) for details.

README.zh-CN.md

@@ -181,24 +181,24 @@ Release-CodexSession.ps1
 
 ## 4. 运行机制概览
 
-```mermaid
-flowchart LR
-    U[Lark User] --> B[lark-channel-bridge]
-    B --> S[Lark scope / Session binding]
-    S --> C[Codex CLI]
-
-    W[Windows Terminal / codex3] --> C2[Codex CLI]
-    C2 --> R[Codex rollout JSONL]
-
-    A[Attach-CodexObserver.ps1] --> R
-    A --> O[Watch-CodexSession.ps1]
-    A --> RA[Watch-CodexRelease.ps1]
-
-    O --> M[.codex-monitor/status]
-    RA --> Q[release request/result]
-
-    B --> M
-    B --> Q
+```mermaid
+flowchart LR
+    U["Lark User"] --> B["lark-channel-bridge"]
+    B --> S["Lark scope / Session binding"]
+    S --> C["Codex CLI"]
+
+    W["Windows Terminal / codex3"] --> C2["Codex CLI"]
+    C2 --> R["Codex rollout JSONL"]
+
+    A["Attach-CodexObserver.ps1"] --> R
+    A --> O["Watch-CodexSession.ps1"]
+    A --> RA["Watch-CodexRelease.ps1"]
+
+    O --> M[".codex-monitor/status"]
+    RA --> Q["release request/result"]
+
+    B --> M
+    B --> Q
 ```
 
 更详细的原理见：

local-docs/01-codex-third-party-api-key.md

@@ -30,13 +30,13 @@ thread index
 other local Codex state
 ```
 
-```mermaid
-flowchart LR
-    PS[PowerShell] --> C3[codex3 wrapper]
-    C3 --> CH[CODEX_HOME=.codex-cli-thirdparty]
-    CH --> CFG[config.toml]
-    CFG --> P[Third-party Provider]
-    P --> API[Responses-compatible API]
+```mermaid
+flowchart LR
+    PS["PowerShell"] --> C3["codex3 wrapper"]
+    C3 --> CH["CODEX_HOME=.codex-cli-thirdparty"]
+    CH --> CFG["config.toml"]
+    CFG --> P["Third-party Provider"]
+    P --> API["Responses-compatible API"]
 ```
 
 ---

local-docs/01-codex-third-party-api-key.zh-CN.md

@@ -30,13 +30,13 @@ Third-party Codex
 
 逻辑如下：
 
-```mermaid
-flowchart LR
-    PS[PowerShell] --> C3[codex3 wrapper]
-    C3 --> CH[CODEX_HOME=.codex-cli-thirdparty]
-    CH --> CFG[config.toml]
-    CFG --> P[Third-party Provider]
-    P --> API[Responses-compatible API]
+```mermaid
+flowchart LR
+    PS["PowerShell"] --> C3["codex3 wrapper"]
+    C3 --> CH["CODEX_HOME=.codex-cli-thirdparty"]
+    CH --> CFG["config.toml"]
+    CFG --> P["Third-party Provider"]
+    P --> API["Responses-compatible API"]
 ```
 
 ---

local-docs/02-lark-bridge-codex-architecture.md

@@ -55,21 +55,21 @@ It observes already-running Windows Codex sessions and provides safe writer rele
 
 ## 2. Normal Lark → Codex Flow
 
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant L as Lark
-    participant B as lark-channel-bridge
-    participant S as Session Store
-    participant C as Codex CLI
-
-    U->>L: normal message
-    L->>B: message event
-    B->>S: resolve scope cwd/sessionId
-    B->>C: start/resume Codex
-    C-->>B: stream/result
-    B-->>L: card/markdown
-    L-->>U: response
+```mermaid
+sequenceDiagram
+    participant U as "User"
+    participant L as "Lark"
+    participant B as "lark-channel-bridge"
+    participant S as "Session Store"
+    participant C as "Codex CLI"
+
+    U->>L: normal message
+    L->>B: message event
+    B->>S: resolve scope cwd/sessionId
+    B->>C: start/resume Codex
+    C-->>B: stream/result
+    B-->>L: card/markdown
+    L-->>U: response
 ```
 
 ---
@@ -163,17 +163,17 @@ Release only the Codex writer.
 
 ## 6. Attach Lifecycle
 
-```mermaid
-flowchart TD
-    A[codex3 starts] --> B[Record LaunchId/CWD/owner PID]
-    B --> C[Find Codex process]
-    C --> D[Wait for matching session/rollout]
-    D --> E[Claim Session]
-    E --> F[Start Observer]
-    E --> G[Start Release Agent]
-    F --> H[status-SessionId.json]
-    G --> I[Wait for release requests]
-    E --> J[launch mapping]
+```mermaid
+flowchart TD
+    A["codex3 starts"] --> B["Record LaunchId/CWD/owner PID"]
+    B --> C["Find Codex process"]
+    C --> D["Wait for matching session/rollout"]
+    D --> E["Claim Session"]
+    E --> F["Start Observer"]
+    E --> G["Start Release Agent"]
+    F --> H["status-SessionId.json"]
+    G --> I["Wait for release requests"]
+    E --> J["launch mapping"]
 ```
 
 A newly opened Codex TUI may exist before a persistent rollout/session has been created. Such a process is best considered a **Pending Launch**, not yet a fully discovered session.
@@ -221,23 +221,23 @@ Watch-CodexRelease.ps1
 
 The bridge does not directly kill the Windows Codex process. Instead it submits a local request:
 
-```mermaid
-sequenceDiagram
-    participant L as Lark Bridge
-    participant R as Request-CodexRelease.ps1
-    participant Q as Request JSON
-    participant A as Watch-CodexRelease.ps1
-    participant X as Release-CodexSession.ps1
-    participant C as Codex Writer
-
-    L->>R: release Session
-    R->>Q: write request
-    A->>Q: consume request
-    A->>X: validate target
-    X->>C: terminate writer
-    X-->>A: RELEASED / ERROR
-    A-->>R: result JSON
-    R-->>L: OK|RELEASED|...
+```mermaid
+sequenceDiagram
+    participant L as "Lark Bridge"
+    participant R as "Request-CodexRelease.ps1"
+    participant Q as "Request JSON"
+    participant A as "Watch-CodexRelease.ps1"
+    participant X as "Release-CodexSession.ps1"
+    participant C as "Codex Writer"
+
+    L->>R: release Session
+    R->>Q: write request
+    A->>Q: consume request
+    A->>X: validate target
+    X->>C: terminate writer
+    X-->>A: RELEASED / ERROR
+    A-->>R: result JSON
+    R-->>L: OK|RELEASED|...
 ```
 
 The PowerShell layer performs the authoritative safety validation.
@@ -280,19 +280,19 @@ attachedAt
 /local-handoff <Thread-name-or-Session-ID-prefix>
 ```
 
-```mermaid
-flowchart TD
-    A[/local-handoff] --> B[Resolve unique Session]
-    B --> C{Bound to another Lark scope?}
-    C -- Yes --> X[Reject: handback from original scope]
-    C -- No --> D{Windows session busy?}
-    D -- Yes --> Y[Reject: wait for current turn]
-    D -- No --> E[Request-CodexRelease]
-    E --> F{PowerShell release successful?}
-    F -- No --> Z[Do not alter Lark binding]
-    F -- Yes --> G[Set scope cwd]
-    G --> H[Set scope sessionId]
-    H --> I[Next normal Lark message resumes the same Session]
+```mermaid
+flowchart TD
+    A["/local-handoff"] --> B["Resolve unique Session"]
+    B --> C{"Bound to another Lark scope?"}
+    C -- Yes --> X["Reject: handback from original scope"]
+    C -- No --> D{"Windows session busy?"}
+    D -- Yes --> Y["Reject: wait for current turn"]
+    D -- No --> E["Request-CodexRelease"]
+    E --> F{"PowerShell release successful?"}
+    F -- No --> Z["Do not alter Lark binding"]
+    F -- Yes --> G["Set scope cwd"]
+    G --> H["Set scope sessionId"]
+    H --> I["Next normal Lark message resumes the same Session"]
 ```
 
 The order must be: