feat(async-context-compression): release v1.4.0 with structure-aware grouping and session locking

- Introduced Atomic Message Grouping to prevent tool-calling corruption (Issue #56)
- Implemented Tail Boundary Alignment for deterministic context truncation
- Added per-chat asynchronous session locking to prevent duplicate background tasks
- Enhanced summarization traceability with message IDs and names
- Synchronized version and changelog across all documentation files
- Optimized release-prep skill to remove redundant H1 titles

Closes #56

.gemini/skills/release-prep/SKILL.md

@@ -73,11 +73,21 @@ Create two versioned release notes files:
 #### Required Sections
 
 Each file must include:
-1. **Title**: `# v{version} Release Notes` (EN) / `# v{version} 版本发布说明` (CN)
-2. **Overview**: One paragraph summarizing this release
-3. **New Features** / **新功能**: Bulleted list of features
-4. **Bug Fixes** / **问题修复**: Bulleted list of fixes
-5. **Migration Notes** / **迁移说明**: Breaking changes or Valve key renames (omit section if none)
+0. **Marketplace Badge**: A prominent button linking to the plugin on openwebui.com using shields.io (e.g., `[![](https://img.shields.io/badge/OpenWebUI%20Community-Get%20Plugin-blue?style=for-the-badge)](URL)`).
+1. **Overview Header**: Use `## Overview` as the first header.
+2. **Summary Paragraph**: A paragraph summarizing the release. **NEVER** include the version number as a title.
+3. **README Link**: Direct link to the plugin's README file on GitHub.
+4. **New Features** / **新功能**: Bulleted list of features
+5. **Bug Fixes** / **问题修复**: Bulleted list of fixes
+6. **Related Issues** / **相关 Issue**: Link to GitHub Issues. **ONLY** include if a specific issue is resolved. **NEVER use placeholders.**
+7. **Related PRs** / **相关 PR**: Link to the Pull Request. **ONLY** include if the PR is already created and the ID is known. **NEVER use placeholders.**
+8. **Migration Notes**: Breaking changes or Valve key renames (omit section if none)
+
+---
+
+## Language Standard
+
+- **Release Notes Files**: Use **English ONLY** for the final `.md` files to maintain professional consistency on GitHub. Avoid bilingual content in the release description.
 6. **Companion Plugins** / **配套插件** (optional): If a companion plugin was updated
 
 If a release notes file already exists for this version, update it rather than creating a new one.
@@ -98,8 +108,10 @@ Generate the commit message following `commit-message.instructions.md` rules:
 - **Language**: English ONLY
 - **Format**: `type(scope): subject` + blank line + body bullets
 - **Scope**: use plugin folder name (e.g., `github-copilot-sdk`)
-- **Body**: 1-3 bullets summarizing key changes
-- Explicitly mention "READMEs and docs synced" if version was bumped
+- **Body**: 
+    - 1-3 bullets summarizing key changes
+    - Explicitly mention "READMEs and docs synced" if version was bumped
+    - **MUST** end with `Closes #XX` or `Fixes #XX` if an issue is being resolved.
 
 Present the full commit message to the user for review before executing.