cc-viewer 1.7.23 → 1.8.1

package/server/system-prompt-templates/systemPromptVariables.it.md

@@ -27,8 +27,6 @@ Questo file documenta solo le variabili in `systemPromptModel.md` che devono ess
 | `${os.hostname}` | Hostname corrente. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Parallelismo disponibile. | `10` |
 | `${os.totalMemory}` | Memoria totale del sistema, in byte. | `34359738368` |
-| `${os.freeMemory}` | Memoria libera, in byte. | `8589934592` |
-| `${os.uptime}` | Tempo di attività del sistema, in secondi. | `123456` |
 
 ## Runtime di Node.js
 
@@ -43,8 +41,6 @@ Questo file documenta solo le variabili in `systemPromptModel.md` che devono ess
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Stringa di ora locale corrente. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Ora ISO corrente. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Data locale corrente. | `2026-07-09` |
 | `${time.timezone}` | Fuso orario del sistema corrente. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ Questo file documenta solo le variabili in `systemPromptModel.md` che devono ess
 |---|---|---|
 | `${terminal.term}` | TERM corrente. | `xterm-256color` |
 | `${terminal.colorTerm}` | COLORTERM corrente. | `truecolor` |
-| `${terminal.columns}` | Numero di colonne del terminale corrente. | `120` |
-| `${terminal.rows}` | Numero di righe del terminale corrente. | `40` |
 
 ## File system
 
@@ -91,7 +85,6 @@ Questo file documenta solo le variabili in `systemPromptModel.md` che devono ess
 | `${git.branch}` | Branch Git corrente o hash HEAD breve. | `main` |
 | `${git.mainBranch}` | Branch principale predefinito, normalmente utilizzato come destinazione di PR o merge. | `main` |
 | `${git.userName}` | Attuale Git `user.name`. | `Sky` |
-| `${git.status}` | Output di `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Riepilogo dei commit recenti. | `abc1234 Fix prompt builder` |
 
 ## Memoria

package/server/system-prompt-templates/systemPromptVariables.ja.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | 現在のホスト名です。 | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | 利用可能な並列性です。 | `10` |
 | `${os.totalMemory}` | システム総メモリ（バイト単位）です。 | `34359738368` |
-| `${os.freeMemory}` | 空きメモリ（バイト単位）です。 | `8589934592` |
-| `${os.uptime}` | システムアップタイム（秒単位）です。 | `123456` |
 
 ## Node.js ランタイム
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | 現在のローカル時刻文字列です。 | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | 現在のISO時刻です。 | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | 現在のローカル日付です。 | `2026-07-09` |
 | `${time.timezone}` | 現在のシステムタイムゾーンです。 | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | 現在のTERMです。 | `xterm-256color` |
 | `${terminal.colorTerm}` | 現在のCOLORTERMです。 | `truecolor` |
-| `${terminal.columns}` | 現在のターミナル列数です。 | `120` |
-| `${terminal.rows}` | 現在のターミナル行数です。 | `40` |
 
 ## ファイルシステム
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | 現在のgitブランチまたは短いHEADハッシュです。 | `main` |
 | `${git.mainBranch}` | デフォルトのメインブランチで、通常PRまたはマージターゲットとして使用されます。 | `main` |
 | `${git.userName}` | 現在のgit `user.name` です。 | `Sky` |
-| `${git.status}` | `git status --short` の出力です。 | `M src/index.ts` |
 | `${git.recentCommits}` | 最近のコミットの概要です。 | `abc1234 Fix prompt builder` |
 
 ## メモリ

package/server/system-prompt-templates/systemPromptVariables.ko.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | 현재 호스트 이름입니다. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | 사용 가능한 병렬성입니다. | `10` |
 | `${os.totalMemory}` | 시스템 총 메모리(바이트 단위)입니다. | `34359738368` |
-| `${os.freeMemory}` | 사용 가능한 메모리(바이트 단위)입니다. | `8589934592` |
-| `${os.uptime}` | 시스템 가동 시간(초 단위)입니다. | `123456` |
 
 ## Node.js 런타임
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | 현재 로컬 시간 문자열입니다. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | 현재 ISO 시간입니다. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | 현재 로컬 날짜입니다. | `2026-07-09` |
 | `${time.timezone}` | 현재 시스템 시간대입니다. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | 현재 TERM입니다. | `xterm-256color` |
 | `${terminal.colorTerm}` | 현재 COLORTERM입니다. | `truecolor` |
-| `${terminal.columns}` | 현재 터미널 열 개수입니다. | `120` |
-| `${terminal.rows}` | 현재 터미널 행 개수입니다. | `40` |
 
 ## 파일 시스템
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | 현재 git 분기 또는 짧은 HEAD 해시입니다. | `main` |
 | `${git.mainBranch}` | 기본 주 분기로 일반적으로 PR 또는 병합 대상으로 사용됩니다. | `main` |
 | `${git.userName}` | 현재 git `user.name`입니다. | `Sky` |
-| `${git.status}` | `git status --short`의 출력입니다. | `M src/index.ts` |
 | `${git.recentCommits}` | 최근 커밋의 요약입니다. | `abc1234 Fix prompt builder` |
 
 ## 메모리

package/server/system-prompt-templates/systemPromptVariables.md

@@ -27,8 +27,6 @@ This file documents only the variables in `systemPromptModel.md` that must be re
 | `${os.hostname}` | Current hostname. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Available parallelism. | `10` |
 | `${os.totalMemory}` | Total system memory, in bytes. | `34359738368` |
-| `${os.freeMemory}` | Free memory, in bytes. | `8589934592` |
-| `${os.uptime}` | System uptime, in seconds. | `123456` |
 
 ## Node.js runtime
 
@@ -43,8 +41,6 @@ This file documents only the variables in `systemPromptModel.md` that must be re
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Current local time string. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Current ISO time. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Current local date. | `2026-07-09` |
 | `${time.timezone}` | Current system timezone. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ This file documents only the variables in `systemPromptModel.md` that must be re
 |---|---|---|
 | `${terminal.term}` | Current TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Current COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Current terminal column count. | `120` |
-| `${terminal.rows}` | Current terminal row count. | `40` |
 
 ## Filesystem
 
@@ -91,7 +85,6 @@ This file documents only the variables in `systemPromptModel.md` that must be re
 | `${git.branch}` | Current git branch or short HEAD hash. | `main` |
 | `${git.mainBranch}` | Default main branch, typically used as the PR or merge target. | `main` |
 | `${git.userName}` | Current git `user.name`. | `Sky` |
-| `${git.status}` | Output of `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Summary of recent commits. | `abc1234 Fix prompt builder` |
 
 ## Memory

package/server/system-prompt-templates/systemPromptVariables.no.md

@@ -27,8 +27,6 @@ Denne filen dokumenterer bare variablene i `systemPromptModel.md` som må løses
 | `${os.hostname}` | Gjeldende vertsnavn. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Tilgjengelig parallellisme. | `10` |
 | `${os.totalMemory}` | Total systemhukommelse i bytes. | `34359738368` |
-| `${os.freeMemory}` | Ledig hukommelse i bytes. | `8589934592` |
-| `${os.uptime}` | System oppetid i sekunder. | `123456` |
 
 ## Node.js-kjøretid
 
@@ -43,8 +41,6 @@ Denne filen dokumenterer bare variablene i `systemPromptModel.md` som må løses
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Gjeldende lokal tidsstreng. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Gjeldende ISO tid. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Gjeldende lokaldato. | `2026-07-09` |
 | `${time.timezone}` | Gjeldende systemtidssone. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ Denne filen dokumenterer bare variablene i `systemPromptModel.md` som må løses
 |---|---|---|
 | `${terminal.term}` | Gjeldende TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Gjeldende COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Gjeldende terminal kolonne tall. | `120` |
-| `${terminal.rows}` | Gjeldende terminal rad tall. | `40` |
 
 ## Filsystem
 
@@ -91,7 +85,6 @@ Denne filen dokumenterer bare variablene i `systemPromptModel.md` som må løses
 | `${git.branch}` | Gjeldende git gren eller kort HEAD hash. | `main` |
 | `${git.mainBranch}` | Standard hoved gren, typisk brukt som PR eller sammensmeltings mål. | `main` |
 | `${git.userName}` | Gjeldende git `user.name`. | `Sky` |
-| `${git.status}` | Utdata fra `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Oppsummering av nylige commits. | `abc1234 Fix prompt builder` |
 
 ## Minne

package/server/system-prompt-templates/systemPromptVariables.pl.md

@@ -27,8 +27,6 @@ Ten plik dokumentuje tylko zmienne w `systemPromptModel.md`, które muszą być
 | `${os.hostname}` | Bieżąca nazwa hosta. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Dostępny paralelizm. | `10` |
 | `${os.totalMemory}` | Całkowita pamięć systemu w bajtach. | `34359738368` |
-| `${os.freeMemory}` | Wolna pamięć w bajtach. | `8589934592` |
-| `${os.uptime}` | Czas pracy systemu w sekundach. | `123456` |
 
 ## Środowisko wykonawcze Node.js
 
@@ -43,8 +41,6 @@ Ten plik dokumentuje tylko zmienne w `systemPromptModel.md`, które muszą być
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Bieżący lokalny ciąg znaków czasu. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Bieżący czas ISO. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Bieżąca data lokalna. | `2026-07-09` |
 | `${time.timezone}` | Bieżąca strefa czasowa systemu. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ Ten plik dokumentuje tylko zmienne w `systemPromptModel.md`, które muszą być
 |---|---|---|
 | `${terminal.term}` | Bieżący TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Bieżący COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Bieżąca liczba kolumn terminala. | `120` |
-| `${terminal.rows}` | Bieżąca liczba wierszy terminala. | `40` |
 
 ## System plików
 
@@ -91,7 +85,6 @@ Ten plik dokumentuje tylko zmienne w `systemPromptModel.md`, które muszą być
 | `${git.branch}` | Bieżąca gałąź git lub krótka skrót HEAD. | `main` |
 | `${git.mainBranch}` | Domyślna gałąź główna, zazwyczaj używana jako cel PR lub połączenia. | `main` |
 | `${git.userName}` | Bieżące git `user.name`. | `Sky` |
-| `${git.status}` | Wyjście `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Streszczenie niedawnych zatwierdzeń. | `abc1234 Fix prompt builder` |
 
 ## Pamięć

package/server/system-prompt-templates/systemPromptVariables.pt-BR.md

@@ -27,8 +27,6 @@ Este arquivo documenta apenas as variáveis em `systemPromptModel.md` que devem
 | `${os.hostname}` | Nome de host atual. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Paralelismo disponível. | `10` |
 | `${os.totalMemory}` | Memória total do sistema, em bytes. | `34359738368` |
-| `${os.freeMemory}` | Memória livre, em bytes. | `8589934592` |
-| `${os.uptime}` | Tempo de atividade do sistema, em segundos. | `123456` |
 
 ## Runtime Node.js
 
@@ -43,8 +41,6 @@ Este arquivo documenta apenas as variáveis em `systemPromptModel.md` que devem
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | String de hora local atual. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Hora ISO atual. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Data local atual. | `2026-07-09` |
 | `${time.timezone}` | Fuso horário do sistema atual. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ Este arquivo documenta apenas as variáveis em `systemPromptModel.md` que devem
 |---|---|---|
 | `${terminal.term}` | TERM atual. | `xterm-256color` |
 | `${terminal.colorTerm}` | COLORTERM atual. | `truecolor` |
-| `${terminal.columns}` | Contagem de colunas do terminal atual. | `120` |
-| `${terminal.rows}` | Contagem de linhas do terminal atual. | `40` |
 
 ## Sistema de arquivos
 
@@ -91,7 +85,6 @@ Este arquivo documenta apenas as variáveis em `systemPromptModel.md` que devem
 | `${git.branch}` | Branch git atual ou hash HEAD curto. | `main` |
 | `${git.mainBranch}` | Branch principal padrão, normalmente usado como alvo de PR ou mesclagem. | `main` |
 | `${git.userName}` | `user.name` do git atual. | `Sky` |
-| `${git.status}` | Saída de `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Resumo de commits recentes. | `abc1234 Fix prompt builder` |
 
 ## Memória

package/server/system-prompt-templates/systemPromptVariables.ru.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | Текущее имя хоста. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Доступный параллелизм. | `10` |
 | `${os.totalMemory}` | Общая память системы в байтах. | `34359738368` |
-| `${os.freeMemory}` | Свободная память в байтах. | `8589934592` |
-| `${os.uptime}` | Время работы системы в секундах. | `123456` |
 
 ## Среда выполнения Node.js
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Строка текущего местного времени. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Текущее время в ISO. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Текущая местная дата. | `2026-07-09` |
 | `${time.timezone}` | Текущий системный часовой пояс. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | Текущий TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Текущий COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Текущее количество столбцов терминала. | `120` |
-| `${terminal.rows}` | Текущее количество строк терминала. | `40` |
 
 ## Файловая система
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | Текущая ветка git или сокращённый хеш HEAD. | `main` |
 | `${git.mainBranch}` | Основная ветка по умолчанию, обычно используется как цель PR или слияния. | `main` |
 | `${git.userName}` | Текущее имя git `user.name`. | `Sky` |
-| `${git.status}` | Вывод `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Сводка недавних коммитов. | `abc1234 Fix prompt builder` |
 
 ## Память

package/server/system-prompt-templates/systemPromptVariables.th.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | ชื่อโฮสต์ปัจจุบัน | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | ความสามารถในการประมวลผลแบบขนาน | `10` |
 | `${os.totalMemory}` | หน่วยความจำของระบบทั้งหมด เป็นไบต์ | `34359738368` |
-| `${os.freeMemory}` | หน่วยความจำว่าง เป็นไบต์ | `8589934592` |
-| `${os.uptime}` | เวลาทำงานของระบบ เป็นวินาที | `123456` |
 
 ## Runtime Node.js
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | สตริงเวลาท้องถิ่นปัจจุบัน | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | เวลา ISO ปัจจุบัน | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | วันที่ท้องถิ่นปัจจุบัน | `2026-07-09` |
 | `${time.timezone}` | โซนเวลาของระบบปัจจุบัน | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | TERM ปัจจุบัน | `xterm-256color` |
 | `${terminal.colorTerm}` | COLORTERM ปัจจุบัน | `truecolor` |
-| `${terminal.columns}` | จำนวนคอลัมน์เทอร์มินัลปัจจุบัน | `120` |
-| `${terminal.rows}` | จำนวนแถวเทอร์มินัลปัจจุบัน | `40` |
 
 ## ระบบไฟล์
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | บรานช์ git ปัจจุบันหรือแฮช HEAD สั้น | `main` |
 | `${git.mainBranch}` | บรานช์หลักเริ่มต้น มักใช้เป็นเป้าหมาย PR หรือการผสาน | `main` |
 | `${git.userName}` | `user.name` ของ git ปัจจุบัน | `Sky` |
-| `${git.status}` | ผลลัพธ์ของ `git status --short` | `M src/index.ts` |
 | `${git.recentCommits}` | สรุปของคอมมิตล่าสุด | `abc1234 Fix prompt builder` |
 
 ## หน่วยความจำ

package/server/system-prompt-templates/systemPromptVariables.tr.md

@@ -27,8 +27,6 @@ Bu dosya, `systemPromptModel.md` içindeki çalışma zamanında çözülmesi ge
 | `${os.hostname}` | Geçerli ana bilgisayar adı. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Kullanılabilir paralelizm. | `10` |
 | `${os.totalMemory}` | Toplam sistem belleği, bayt cinsinden. | `34359738368` |
-| `${os.freeMemory}` | Boş bellek, bayt cinsinden. | `8589934592` |
-| `${os.uptime}` | Sistem çalışma süresi, saniye cinsinden. | `123456` |
 
 ## Node.js çalışma zamanı
 
@@ -43,8 +41,6 @@ Bu dosya, `systemPromptModel.md` içindeki çalışma zamanında çözülmesi ge
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Geçerli yerel saat dizesi. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Geçerli ISO saati. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Geçerli yerel tarih. | `2026-07-09` |
 | `${time.timezone}` | Geçerli sistem saat dilimi. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@ Bu dosya, `systemPromptModel.md` içindeki çalışma zamanında çözülmesi ge
 |---|---|---|
 | `${terminal.term}` | Geçerli TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Geçerli COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Geçerli terminal sütun sayısı. | `120` |
-| `${terminal.rows}` | Geçerli terminal satır sayısı. | `40` |
 
 ## Dosya sistemi
 
@@ -91,7 +85,6 @@ Bu dosya, `systemPromptModel.md` içindeki çalışma zamanında çözülmesi ge
 | `${git.branch}` | Geçerli git dalı veya kısa HEAD hash. | `main` |
 | `${git.mainBranch}` | Varsayılan ana dal, tipik olarak PR veya birleştirme hedefi olarak kullanılır. | `main` |
 | `${git.userName}` | Geçerli git `user.name`. | `Sky` |
-| `${git.status}` | `git status --short` çıkışı. | `M src/index.ts` |
 | `${git.recentCommits}` | Son commits özeti. | `abc1234 Fix prompt builder` |
 
 ## Bellek

package/server/system-prompt-templates/systemPromptVariables.uk.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | Поточне ім'я хосту. | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | Доступний паралелізм. | `10` |
 | `${os.totalMemory}` | Загальна пам'ять системи у байтах. | `34359738368` |
-| `${os.freeMemory}` | Вільна пам'ять у байтах. | `8589934592` |
-| `${os.uptime}` | Час роботи системи у секундах. | `123456` |
 
 ## Середовище виконання Node.js
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | Рядок поточного місцевого часу. | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | Поточний час у ISO. | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | Поточна місцева дата. | `2026-07-09` |
 | `${time.timezone}` | Поточний системний часовий пояс. | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | Поточний TERM. | `xterm-256color` |
 | `${terminal.colorTerm}` | Поточний COLORTERM. | `truecolor` |
-| `${terminal.columns}` | Поточна кількість стовпців терміналу. | `120` |
-| `${terminal.rows}` | Поточна кількість рядків терміналу. | `40` |
 
 ## Файлова система
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | Поточна гілка git або скорочений хеш HEAD. | `main` |
 | `${git.mainBranch}` | Основна гілка за замовчуванням, зазвичай використовується як ціль PR або злиття. | `main` |
 | `${git.userName}` | Поточне ім'я git `user.name`. | `Sky` |
-| `${git.status}` | Результат `git status --short`. | `M src/index.ts` |
 | `${git.recentCommits}` | Резюме недавніх комітів. | `abc1234 Fix prompt builder` |
 
 ## Пам'ять

package/server/system-prompt-templates/systemPromptVariables.zh-TW.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | 目前主機名稱。 | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | 可用並行度。 | `10` |
 | `${os.totalMemory}` | 系統總記憶體，以位元組為單位。 | `34359738368` |
-| `${os.freeMemory}` | 可用記憶體，以位元組為單位。 | `8589934592` |
-| `${os.uptime}` | 系統運行時間，以秒為單位。 | `123456` |
 
 ## Node.js 執行環境
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | 目前本地時間字串。 | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | 目前 ISO 時間。 | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | 目前本地日期。 | `2026-07-09` |
 | `${time.timezone}` | 目前系統時區。 | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | 目前 TERM。 | `xterm-256color` |
 | `${terminal.colorTerm}` | 目前 COLORTERM。 | `truecolor` |
-| `${terminal.columns}` | 目前終端欄數。 | `120` |
-| `${terminal.rows}` | 目前終端列數。 | `40` |
 
 ## 檔案系統
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | 目前 git 分支或短 HEAD 雜湊。 | `main` |
 | `${git.mainBranch}` | 預設主分支，通常用作 PR 或合併目標。 | `main` |
 | `${git.userName}` | 目前 git `user.name`。 | `Sky` |
-| `${git.status}` | `git status --short` 的輸出。 | `M src/index.ts` |
 | `${git.recentCommits}` | 最近提交的摘要。 | `abc1234 Fix prompt builder` |
 
 ## 記憶

package/server/system-prompt-templates/systemPromptVariables.zh.md

@@ -27,8 +27,6 @@
 | `${os.hostname}` | 当前主机名。 | `MacBook-Pro.local` |
 | `${os.availableParallelism}` | 可用并行度。 | `10` |
 | `${os.totalMemory}` | 系统总内存，以字节为单位。 | `34359738368` |
-| `${os.freeMemory}` | 可用内存，以字节为单位。 | `8589934592` |
-| `${os.uptime}` | 系统运行时间，以秒为单位。 | `123456` |
 
 ## Node.js 运行时
 
@@ -43,8 +41,6 @@
 
 | Variable | Description | Example |
 |---|---|---|
-| `${time.current}` | 当前本地时间字符串。 | `Thu Jul 09 2026 18:22:09 GMT+0800 (China Standard Time)` |
-| `${time.iso}` | 当前 ISO 时间。 | `2026-07-09T10:22:09.000Z` |
 | `${time.date}` | 当前本地日期。 | `2026-07-09` |
 | `${time.timezone}` | 当前系统时区。 | `Asia/Shanghai` |
 
@@ -64,8 +60,6 @@
 |---|---|---|
 | `${terminal.term}` | 当前 TERM。 | `xterm-256color` |
 | `${terminal.colorTerm}` | 当前 COLORTERM。 | `truecolor` |
-| `${terminal.columns}` | 当前终端列数。 | `120` |
-| `${terminal.rows}` | 当前终端行数。 | `40` |
 
 ## 文件系统
 
@@ -91,7 +85,6 @@
 | `${git.branch}` | 当前 git 分支或短 HEAD 哈希。 | `main` |
 | `${git.mainBranch}` | 默认主分支，通常用作 PR 或合并目标。 | `main` |
 | `${git.userName}` | 当前 git `user.name`。 | `Sky` |
-| `${git.status}` | `git status --short` 的输出。 | `M src/index.ts` |
 | `${git.recentCommits}` | 最近提交的摘要。 | `abc1234 Fix prompt builder` |
 
 ## 记忆

package/ultraAgents/README.md

@@ -48,6 +48,8 @@ in `src/utils/ultraplanTemplates.js`). Preset `content` should therefore be writ
 > `src/utils/ultraplanTemplates.js`'s `ULTRAPLAN_VARIANTS.codeExpert` / `researchExpert`,
 > and is pinned byte-for-byte by `test/ultra-agents-api.test.js` — to change the body, edit that
 > source file and regenerate the JSON in this directory; do not hand-write a second copy here.
+> Other presets (e.g. `test-analysis-expert`) are authored standalone in this directory and have
+> no template source.
 
 ## Validation and Limits
 
@@ -66,6 +68,7 @@ Each file undergoes defensive validation at load time. Invalid files are skipped
 | --- | --- | --- | --- |
 | `code-expert.json` | Code Expert / 代码专家 | Inline localized (all 18 languages) | `ULTRAPLAN_VARIANTS.codeExpert` |
 | `research-expert.json` | Research Expert / 调研专家 | Inline localized (all 18 languages) | `ULTRAPLAN_VARIANTS.researchExpert` |
+| `test-analysis-expert.json` | Test Analysis Expert / 测分专家 | Inline localized (all 18 languages) | standalone (authored here; UI-only Midscene.js YAML test-case generation, generation-only) |
 
 To add a new preset: drop a new `*.json` file in this directory (file name should match `id`),
 and restart/refresh to see it in the modal.

package/ultraAgents/test-analysis-expert.json

@@ -0,0 +1,45 @@
+{
+  "id": "test-analysis-expert",
+  "version": 1,
+  "title": {
+    "zh": "测分专家",
+    "en": "Test Analysis Expert",
+    "zh-TW": "測試分析專家",
+    "ko": "테스트 분석 전문가",
+    "ja": "テスト分析エキスパート",
+    "de": "Testanalyse-Experte",
+    "es": "Experto en análisis de pruebas",
+    "fr": "Expert en analyse de tests",
+    "it": "Esperto di analisi dei test",
+    "da": "Testanalyseekspert",
+    "pl": "Ekspert analizy testów",
+    "ru": "Эксперт по анализу тестирования",
+    "ar": "خبير تحليل الاختبارات",
+    "no": "Testanalyseekspert",
+    "pt-BR": "Especialista em análise de testes",
+    "th": "ผู้เชี่ยวชาญการวิเคราะห์การทดสอบ",
+    "tr": "Test analiz uzmanı",
+    "uk": "Експерт з аналізу тестування"
+  },
+  "description": {
+    "zh": "测试分析专家：多智能体素材分析 + Midscene YAML 用例生成，产出 UI 测试分析报告与自动化用例，只生成不执行。",
+    "en": "Test analysis expert: multi-agent materials analysis and Midscene.js YAML flow generation — produces a UI test-analysis report and automation cases; generation only, no execution.",
+    "zh-TW": "測試分析專家：多智能體素材分析 + Midscene YAML 用例產生，產出 UI 測試分析報告與自動化用例，只產生不執行。",
+    "ko": "테스트 분석 전문가: 멀티 에이전트 자료 분석 + Midscene YAML 케이스 생성 — UI 테스트 분석 보고서와 자동화 케이스를 산출하며, 실행 없이 생성만 합니다.",
+    "ja": "テスト分析エキスパート：マルチエージェント素材分析 + Midscene YAML フロー生成 — UI テスト分析レポートと自動化ケースを生成、実行は行いません。",
+    "de": "Testanalyse-Experte: Multi-Agenten-Materialanalyse und Midscene-YAML-Flow-Generierung – erstellt einen UI-Testanalysebericht und Automatisierungsfälle; nur Generierung, keine Ausführung.",
+    "es": "Experto en análisis de pruebas: análisis de materiales multiagente y generación de flujos YAML de Midscene.js — produce un informe de análisis de pruebas UI y casos de automatización; solo generación, sin ejecución.",
+    "fr": "Expert en analyse de tests : analyse des matériaux multi-agents et génération de flux YAML Midscene.js — produit un rapport d'analyse de tests UI et des cas d'automatisation ; génération uniquement, sans exécution.",
+    "it": "Esperto di analisi dei test: analisi dei materiali multi-agente e generazione di flussi YAML Midscene.js — produce un report di analisi dei test UI e casi di automazione; solo generazione, nessuna esecuzione.",
+    "da": "Testanalyseekspert: multi-agent-materialeanalyse og Midscene.js YAML-flow-generering — producerer en UI-testanalyserapport og automatiseringscases; kun generering, ingen eksekvering.",
+    "pl": "Ekspert analizy testów: wieloagentowa analiza materiałów i generowanie przepływów YAML Midscene.js — tworzy raport analizy testów UI i przypadki automatyzacji; tylko generowanie, bez wykonywania.",
+    "ru": "Эксперт по анализу тестирования: мультиагентный анализ материалов и генерация YAML-потоков Midscene.js — формирует отчёт по анализу UI-тестирования и автоматизированные кейсы; только генерация, без выполнения.",
+    "ar": "خبير تحليل الاختبارات: تحليل المواد متعدد الوكلاء وتوليد تدفقات YAML لـ Midscene.js — يُنتج تقرير تحليل اختبارات واجهة المستخدم وحالات أتمتة؛ توليد فقط دون تنفيذ.",
+    "no": "Testanalyseekspert: multi-agent materialeanalyse og Midscene.js YAML-flytgenerering — produserer en UI-testanalyserapport og automatiseringscaser; kun generering, ingen kjøring.",
+    "pt-BR": "Especialista em análise de testes: análise de materiais multiagente e geração de fluxos YAML do Midscene.js — produz um relatório de análise de testes de UI e casos de automação; apenas geração, sem execução.",
+    "th": "ผู้เชี่ยวชาญการวิเคราะห์การทดสอบ: วิเคราะห์เอกสารแบบหลายเอเจนต์และสร้างโฟลว์ YAML ของ Midscene.js — สร้างรายงานการวิเคราะห์การทดสอบ UI และกรณีทดสอบอัตโนมัติ สร้างอย่างเดียวไม่รัน",
+    "tr": "Test analiz uzmanı: çok aracılı malzeme analizi ve Midscene.js YAML akışı üretimi — UI test analiz raporu ve otomasyon senaryoları üretir; yalnızca üretim, çalıştırma yok.",
+    "uk": "Експерт з аналізу тестування: мультиагентний аналіз матеріалів і генерація YAML-потоків Midscene.js — створює звіт аналізу UI-тестування та кейси автоматизації; лише генерація, без виконання."
+  },
+  "content": "<system-reminder>\n[SCOPED INSTRUCTION] The following instructions apply only to the next 1–3 interactions. Once the task is complete, these instructions should gradually decrease in priority and no longer affect subsequent interactions. You should be adept at utilizing tools such as `AskUserQuestion`, `EnterPlanMode`, and `Agent`, rather than relying solely on plain text processing. Before execution, you must ensure that the `EnterPlanMode`, `ExitPlanMode`, `TaskCreate`, `TaskUpdate`, `TaskStop`, `TaskGet`, `TaskOutput` and `TaskList` tools are loaded.\n\nPre-requisite: Use `AskUserQuestion` to clarify the target UI scope (modules, pages, key flows), the case-text language, and the output directory whenever the request is ambiguous. Skip only if the intent is unambiguous.\n\nYou are a UI test-analysis expert. Your only deliverables are (a) a markdown test-analysis report (including validation notes) and (b) Midscene.js YAML automation flows (github.com/web-infra-dev/midscene). Hard rules:\n- UI layer only: do not produce API-level or unit-level test points or code.\n- Generation only: NEVER execute the YAML flows, a midscene runner, Playwright, or any browser automation; validation is by reading and cross-checking.\n- Case text inside YAML files follows the case-text language clarified at intake (default: the language of the source materials).\n\nLeverage a multi-agent exploration mechanism to formulate an exceptionally detailed test analysis.\n\nInstructions:\n1. Materials intake — the analysis requires these materials; confirm each given path actually exists and never fabricate contents:\n- REQUIRED: (a) system-analysis docs; (b) requirements docs; (c) the code repository of the system under test; (d) environment context (target URLs, accounts, viewport, midscene model configuration).\n- OPTIONAL: existing test assets (style reference + dedup), prototypes/design drafts or page snapshots, defect/risk history.\n- If any REQUIRED material is missing, use `AskUserQuestion` before continuing (offer: user supplies the path / proceed with assumptions recorded in the report / narrow the scope). Missing optional materials are noted in the report and do not block.\n\n2. Use the `Agent` tool to spawn parallel agents that analyze the materials from different angles:\n- Requirements deconstruction: testable behaviors, roles, preconditions, acceptance criteria; flag ambiguities and conflicts; assign each requirement item a stable requirement ID.\n- System-analysis mapping: pages, flows and state models (state x event x action x result); identify stateful lifecycles.\n- Code grounding: map requirement behaviors to concrete pages/routes/components in the repository; extract the exact visible UI copy/labels as assertion material; flag requirement-vs-code mismatches (when UI copy in code conflicts with the specification, the specification wins and the case is marked as a suspected bug); also flag behaviors found in code but absent from the specification (spec-silent), to be handled per the anti-oracle guardrail.\n- Environment completeness: verify the environment context fully specifies a midscene target (url, viewport, model configuration); list gaps; determine the login strategy per flow group: (a) `cookie` (path to a JSON cookie file) in the environment segment when provided, or (b) a first `task` acting as the login setup flow, or (c) login treated as an out-of-scope precondition recorded in the handoff notes.\n- (Only when test assets exist) Asset inventory: style conventions and a dedup list.\nYou may add other roles or deploy additional agents beyond the ones listed above; the maximum number of concurrently dispatched agents is 5.\n\n3. Synthesize the findings from all agents into a test-analysis report (markdown). The report must include:\n- A traceability matrix: requirement ID to test point(s).\n- The test-point list with fixed fields: ID | requirement ID(s) | page/flow | behavior under test | input/precondition (including entry state: login role, seed data) | expected result (grounded in the requirements) | design technique | priority | YAML file (backfilled in step 4).\n- The design technique for each test point, chosen by these decision rules (not definitions):\n  pure input domains to equivalence partitioning + boundary values (template: min-1/min/min+1/max-1/max/max+1);\n  multi-condition business rules to decision tables;\n  lifecycle state machines (orders, sessions, wizards) to state-transition testing;\n  more than 3 parameters that cannot be exhaustively combined to pairwise;\n  tight time or broad scope to risk table, top-N first;\n  default (display/copy/navigation points matching no technique): scenario-based, at least one happy-path case per requirement item, exception paths on demand.\n- Risk ranking (impact x probability) and a list of known non-goals.\nRe-read the report once against the intake materials, then submit it as the plan via `ExitPlanMode`. Once `ExitPlanMode` returns a result:\n- If approved: proceed to generate the YAML flows in this session.\n- If rejected: revise the report based on the feedback provided and call `ExitPlanMode` again.\n- If an error occurs (including receiving a \"Not in Plan Mode\" message): do **not** follow the suggestions provided in the error message; instead, prompt the user for further instructions.\n\n4. Generate the YAML flows (only after approval):\n- One YAML file per page/flow group; at least one `task` per test point; embed the test-point ID in the task name (e.g. `name: TP-012 login-empty-password`). A test point whose technique yields multiple attempts (BVA's six boundary values, decision-table rows, pairwise combinations) may either run several attempt -> assert -> reset cycles inside ONE task - each cycle re-establishing its own entry state via reload/navigation so no step depends on a previous attempt's end state - or split into suffixed tasks (`TP-012-1` ... `TP-012-n`); the convention used must be stated in the report.\n- File skeleton: an environment segment (`page:` is the recommended key, with `url`, `viewportWidth`/`viewportHeight` - default 1440x800 - plus `userAgent`/`cookie` (path to a JSON cookie file)/`output` only when the environment context requires them; `web:` remains supported as a compatibility entry but is discouraged for new files; `browser:` (multi-tab flows) and the optional `agent:` section (testId, reportFileName) are documented keys, acceptable when the environment context requires them; NEVER the deprecated `target:`; never mix `page`/`browser`/`web`/`target`) followed by `tasks:`. Structural rule: every task's steps live under that task's `flow:` key, and a task may only carry `name`/`continueOnError`/`flow`:\n  tasks:\n    - name: TP-012 login-empty-password\n      flow:\n        - aiTap: 'the blue Login button at the top right'\n- Flow granularity: each `-` step is ONE user-visible action in the case-text language; use instant actions (`aiTap`, `aiHover`, `aiInput`+`value`, `aiKeyboardPress`+`keyName`, `aiScroll`) for single-element operations and `ai`/`aiAct` only for multi-step or conditional actions; prompts describe elements visually (appearance + position, e.g. \"the blue Login button at the top right\"), never by DOM/selectors/xpath; YAML string hygiene: wrap every prompt/value/errorMessage string in single quotes - any string containing `: ` (colon+space), `#`, or leading/trailing spaces MUST be quoted or YAML parsing fails; `aiQuery` prompts must state the result format and carry a `name`; every flow ends with at least one `aiAssert` whose prompt states requirement-grounded visible text or state (optionally `errorMessage` carrying the test-point ID); prefer `aiWaitFor` (waits for a condition, default 30000ms, raise `timeout` when needed) for asynchronous UI and use `sleep` only for fixed-duration animation/throttle waits; `aiBoolean` may check a visible state mid-flow; `javascript` only for UI-state preconditions not reachable via `ai*` actions (e.g. seeding login state or localStorage), never for assertions.\n- Every flow is self-contained: it starts from a reachable entry page and never depends on the end state of a previous task or file; record the navigation chain in the test point's precondition.\n- Secrets and accounts are referenced as `${VAR}` placeholders documented in the handoff notes - never hardcode credentials.\n- Create one task per YAML file with `TaskCreate` (subject = relative path) and move it through in_progress to completed with `TaskUpdate` as generation and review fixes land; backfill the report's YAML-file column.\n- **Anti-oracle-compliance guardrail (most important):** expected results come from the requirements/system-analysis docs - NEVER derive an expectation from the implementation's current behavior. Because nothing is ever executed, 'implementation behavior' can only mean what the code-grounding agent read in the repository (UI copy, conditional rendering, validation rules) - there is no other source. When implementation conflicts with the specification, write the flow asserting the SPECIFIED behavior, mark it as a suspected-bug case, and place it in `suspected-bugs/` (isolated from the passing suite); never write a case that enshrines a buggy implementation. When the specification is SILENT about the expected result (no conflict, but no spec either), never derive the expectation from code: omit that particular `aiAssert` (the flow still ends with its spec-grounded assertion) and record the spec gap in the report's gap list.\n- Restating the hard rule: do NOT execute anything - no `midscene` CLI, no runner, no browser automation.\n\n5. Static validation - use the `Agent` tool to spawn 2-3 review agents that examine the deliverables by reading only (never execute):\n- Schema/structure: valid YAML; only documented midscene keys (`page`/`web`/`browser`, `agent`, `tasks`, `name`, `continueOnError`, `flow`, `ai`/`aiAct`, `aiTap`, `aiHover`, `aiInput`+`value`, `aiKeyboardPress`+`keyName`, `aiScroll`, `aiAssert`, `aiQuery`+`name`, `aiBoolean`, `aiWaitFor`, `sleep`, `javascript`, `recordToReport`); every flow step is a `-` array item; no mixed environment segments.\n- Assert locatability: every `aiAssert` targets visible copy/state derivable from the requirements or repository UI text; no selector/xpath assertions; prompts are visual and single-purpose.\n- Anti-oracle compliance: every `aiAssert`'s expected value is traceable to the requirements/system-analysis docs, not to the implementation's current behavior; suspected-bug flows are correctly isolated.\n- Flow self-containment & step reachability: every flow starts from a reachable entry page (the environment `url` or a navigation chain recorded in the test point's precondition); every step's target element is established by an earlier step in the same task - no cross-task/file dependency; every assertion on async content (per the code-grounding findings: fetch/SSE/lazy rendering) is preceded by `aiWaitFor` (explicit timeout) or `sleep`; every `${VAR}` referenced in a flow is documented in run-notes.md; every flow's login strategy (cookie path / first login task / out-of-scope precondition) matches the environment-completeness findings.\n- Traceability & dedup: every test point has at least one flow; every flow links back to a test-point ID (suffixed IDs like `TP-012-1` allowed); no duplicates of existing test assets.\nDistill findings into P0/P1/P2 items; fix P0 (and concrete low-risk P1) and re-review, at most 2 rounds; report anything left unfixed.\n\n6. Deliverables and closing report - write files under `test-analysis/` (confirm the location at intake):\n  test-analysis/\n    analysis-report.md      # test-point matrix, techniques, traceability\n    flows/<module>/<page-or-flow>.yaml\n    suspected-bugs/*.yaml   # isolated spec-vs-implementation cases\n    validation-notes.md     # static-review record + risk statement\n    run-notes.md            # offline execution handoff (see below)\nThe closing message must include: requirement x test-point x flow coverage summary; the gap list with reasons; a risk statement (known non-goals, suspected-bug list, visual-assertion uncertainty); and the offline-execution handoff (also written to run-notes.md): how to run (`midscene ./x.yaml`), the required `.env` variables (MIDSCENE_MODEL_NAME / MIDSCENE_MODEL_API_KEY / MIDSCENE_MODEL_BASE_URL / MIDSCENE_MODEL_FAMILY) and the `${VAR}` account placeholders, explicitly stating the flows were never executed.\n</system-reminder>"
+}