feat: add History page for browsing Hermes sessions (v0.5.5) (#370)

Features:
- Add dedicated History page for browsing Hermes session history
- Independent session state (does not interfere with active chat)
- Auto-select first CLI session on page load
- Filter out api_server and cron sources

Components:
- New HistoryView.vue with isolated state management
- New HistoryMessageList.vue with session prop support
- Filters empty content and tool messages without toolName

Backend:
- Add GET /api/hermes/sessions/hermes endpoint (excludes api_server)
- Add GET /api/hermes/sessions/hermes/:id endpoint (404s for api_server)
- Add fetchHermesSessions() and fetchHermesSession() API functions

Cleanup:
- Remove localStorage session caching
- Simplify profile switching cache management
- Clean up废弃 cache cleanup calls

i18n:
- Add "History" translation to all 8 locales
- Add v0.5.5 changelog entries in all languages
- 🎉 Happy Labor Day!

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/client/src/i18n/locales/ja.ts

@@ -67,6 +67,8 @@ export default {
   // サイドバー
   sidebar: {
     chat: 'チャット',
+    search: '検索',
+    history: '履歴',
     jobs: 'ジョブ',
     models: 'モデル',
     profiles: 'プロファイル',
@@ -563,7 +565,15 @@ export default {
 
   // 更新履歴
   changelog: {
-    new_0_5_4_1: 'Happy Labor Day! No work this Labor Day, please bear with us if there are any issues 🎉',
+
+    new_0_5_5_1: '🎉 労働者の日！今日はお休みです、何卒ご理解ください',
+    new_0_5_5_2: 'Hermesセッション履歴ページを追加',
+    new_0_5_5_3: '履歴ページはアクティブチャットに干渉せずにセッション管理',
+    new_0_5_5_4: '履歴ページは最初のCLIセッションを自動選択',
+    new_0_5_5_5: 'HistoryMessageListコンポーネントを追加',
+    new_0_5_5_6: '空のメッセージとtoolNameなしのtoolメッセージをフィルタリング',
+    new_0_5_5_7: 'localStorageセッションキャッシュを削除、バックエンドから直接取得',
+    new_0_5_5_8: 'プロフィール切り替えを最適化',
     new_0_5_4_2: 'Fix concurrent chat sessions event cross-talk with WebSocket event routing refactoring',
     new_0_5_4_3: 'Fix cron job edit payloads with partial PATCH to support long prompt name-only edits',
     new_0_5_4_4: 'Fix web terminal Hermes CLI availability after Docker deployment',