triflux 10.26.0 → 10.28.0

package/README.ko.md

@@ -8,19 +8,19 @@
   </picture>
 </p>
 
-<h3 align="center">Claude Code, Codex, Gemini를 위한 CLI-first 멀티 모델 오케스트레이션</h3>
+<h3 align="center">Claude Code, Codex, Antigravity를 위한 CLI-first 멀티 모델 오케스트레이션</h3>
 
 <p align="center">
-  작업 라우팅, 에이전트 조율, 로컬/원격 팀 실행, Codex/Gemini/Claude 실행 경로를<br>
-  감사 가능한 guard 뒤에 묶는 하나의 front door입니다.
+  작업 라우팅, 에이전트 조율, 로컬/원격 팀 실행, Codex/Antigravity/Claude 실행 경로를<br>
+  감사 가능한 경로로 묶는 단일 진입점입니다.
 </p>
 
 <p align="center">
   <a href="https://www.npmjs.com/package/triflux"><img src="https://img.shields.io/npm/v/triflux?style=flat-square&color=FFAF00&label=npm" alt="npm version"></a>
   <a href="https://www.npmjs.com/package/triflux"><img src="https://img.shields.io/npm/dm/triflux?style=flat-square&color=F5C242" alt="npm downloads"></a>
   <a href="https://github.com/tellang/triflux/stargazers"><img src="https://img.shields.io/github/stars/tellang/triflux?style=flat-square&color=FFAF00" alt="GitHub stars"></a>
-  <img src="https://img.shields.io/badge/skill_files-33-F5C242?style=flat-square" alt="33 skill files">
-  <sub>deprecated 호환 alias 11개는 전면 표면이 아닙니다</sub>
+  <img src="https://img.shields.io/badge/skill_files-34-F5C242?style=flat-square" alt="34 skill files">
+  <sub>deprecated 호환 alias 11개는 전면 API가 아닙니다</sub>
   <img src="https://img.shields.io/badge/node-%3E%3D18-374151?style=flat-square" alt="Node >= 18">
   <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-374151?style=flat-square" alt="License: MIT"></a>
 </p>
@@ -42,9 +42,9 @@
 
 ## triflux란?
 
-triflux는 **Claude Code plugin + npm CLI**입니다. Claude, Codex, Gemini를
-오가며 AI 코딩 작업을 라우팅하되, 임의 셸 명령이나 오래된 skill alias가 제어면이
-되지 않도록 현재 표면을 정리합니다.
+triflux는 **Claude Code plugin + npm CLI**입니다. Claude, Codex, Antigravity를
+오가며 AI 코딩 작업을 라우팅합니다. 임의 셸 명령이나 오래된 skill alias가
+제어 표면이 되지 않도록 현재 진입점을 좁혔습니다.
 
 현재 설계는 예전 README보다 단순합니다.
 
@@ -105,7 +105,7 @@ tfx codex-team "auth 리팩터링 + 테스트 추가"
 ```
 
 > deep, consensus, team, swarm 경로는 관련 CLI와 터미널 multiplexer가 필요합니다.
-> 먼저 `tfx doctor`를 실행하면 Codex/Gemini/Claude, psmux/tmux, Hub, MCP,
+> 먼저 `tfx doctor`를 실행하면 Codex/Antigravity/Claude, psmux/tmux, Hub, MCP,
 > profile, stale skill 문제를 한 번에 확인할 수 있습니다.
 
 ---
@@ -120,26 +120,31 @@ tfx codex-team "auth 리팩터링 + 테스트 추가"
 | --- | --- |
 | `tfx setup` | scripts, HUD, hooks, MCP, profile 동기화. `--dry-run` 지원. |
 | `tfx doctor` | 설치 상태 진단/복구. `--fix`, `--reset`, `--diagnose`, `--json` 지원. |
+| `tfx auto` | `tfx-auto` 라우팅 결정을 미리 확인. `--cli`, `--mode`, `--parallel`, `--json` 지원. |
 | `tfx mcp` | MCP registry 대상을 `list`, `sync`, `add`, `remove`. |
 | `tfx hub` | 로컬 MCP 메시지 버스 시작/중지/보장/상태 확인. |
-| `tfx list` | 설치된 package/user skill 목록. |
+| `tfx list` | 설치된 package skill과 user skill 목록. |
 | `tfx handoff` | 현재 컨텍스트를 로컬/원격 이어받기 프롬프트로 직렬화. |
 | `tfx schema` | CLI와 Hub delegator schema 출력. |
+| `tfx hooks` | hook orchestrator를 scan/diff/apply/restore/status로 관리. |
+| `tfx tray` | tray/HUD 상태 프로세스 실행. `--attach`는 foreground 디버깅용. |
 | `tfx multi` | tmux/psmux + Hub 기반 로컬 multi-agent team 실행. |
 | `tfx swarm` | PRD 기반 worktree 격리 swarm의 plan/preflight/run/list. |
 | `tfx synapse` | swarm registry와 lease 상태 확인. |
-| `tfx codex-team` | Codex lead team mode 편의 wrapper. |
-| `tfx notion-read` | MCP client를 통해 Notion 페이지를 Markdown으로 변환. |
+| `tfx review` | Codex 기반 git diff review 실행. |
+| `tfx codex-team` | Codex lead team mode용 편의 wrapper. |
+| `tfx notion-read` | MCP client로 Notion 페이지를 Markdown으로 변환. |
 | `tfx why` | 특정 경로의 마지막 커밋 intent trailer 조회. |
 | `tfx update` | 최신 stable/dev 패키지로 업데이트. |
+| `tfx monitor` | 터미널 TUI monitor 실행. |
 | `tfx version` | 버전 정보 출력. |
-| `tfx-profile` | Codex/Gemini profile 관리용 편의 binary. |
+| `tfx-profile` | Codex profile 관리용 편의 binary. |
 
 정확한 인자 계약은 `tfx schema <command>`로 확인합니다.
 
 ### Claude Code skill
 
-패키지에는 **33개 skill 파일**이 들어 있습니다. 크게 나누면 다음과 같습니다.
+패키지에는 **34개 skill 파일**이 들어 있습니다. 크게 나누면 다음과 같습니다.
 
 - **표준 진입점**: `tfx-auto`, `tfx-remote`, `tfx-doctor`, `tfx-setup`,
   `tfx-profile`, `tfx-hub`, `tfx-hooks`, `tfx-ship`, `tfx-wt`.
@@ -150,7 +155,7 @@ tfx codex-team "auth 리팩터링 + 테스트 추가"
 
 ### 표준 플래그 맵
 
-대부분의 옛 skill 이름은 이제 명시적인 `tfx-auto` 플래그로 표현할 수 있습니다.
+대부분의 옛 skill 이름은 `tfx-auto` 플래그로 표현할 수 있습니다.
 
 | 의도 | 표준 형태 |
 | --- | --- |
@@ -161,11 +166,11 @@ tfx codex-team "auth 리팩터링 + 테스트 추가"
 | debate 또는 panel 보고 | `/tfx-auto "작업" --mode consensus --shape debate|panel` |
 | 로컬 병렬 작업 | `/tfx-auto "작업" --parallel N --mode deep` 또는 shell `tfx multi ...` |
 | PRD/worktree swarm | `/tfx-auto "작업" --parallel swarm --mode consensus --isolation worktree` 또는 shell `tfx swarm ...` |
-| CLI lane 강제 | `/tfx-auto "작업" --cli codex|gemini|claude` |
+| CLI lane 강제 | `/tfx-auto "작업" --cli codex|antigravity|claude` |
 
 ### 제어 표면의 경계
 
-triflux를 디버그하거나 확장할 때는 아래 표면을 나눠서 봐야 합니다.
+triflux를 디버그하거나 확장할 때는 아래 경계를 분리해서 봐야 합니다.
 
 | 표면 | 기준 위치 | npm/plugin 포함 여부 |
 | --- | --- | --- |
@@ -208,7 +213,7 @@ triflux를 디버그하거나 확장할 때는 아래 표면을 나눠서 봐야
 /tfx-auto "마이그레이션 전략 리뷰" --mode consensus --shape panel
 ```
 
-참여 lane은 설정된 Claude/Codex/Gemini입니다. 어떤 lane이 없으면 결과에 partial/degraded 상태가 드러나야 합니다.
+참여 lane은 설정된 Claude/Codex/Antigravity입니다. 어떤 lane이 없으면 결과에 partial/degraded 상태가 드러나야 합니다.
 
 ### 로컬 팀 또는 PRD swarm
 
@@ -256,8 +261,8 @@ tfx handoff --target remote --decision "README는 canonical 중심, alias는 doc
 graph TD
     User([User / Claude Code / shell]) --> Skills[Claude skills]
     User --> CLI[tfx CLI]
-    Skills --> Auto[/tfx-auto]
-    Skills --> Remote[/tfx-remote]
+    Skills --> Auto["/tfx-auto"]
+    Skills --> Remote["/tfx-remote"]
     CLI --> Hub[triflux Hub]
     CLI --> Team[tfx multi / swarm]
     Auto --> Route[tfx-route.sh + guards]
@@ -276,7 +281,7 @@ graph TD
 1. Claude Code prompt 또는 명시적 skill 호출.
 2. keyword/routing hook이 context를 추가하거나 skill을 고릅니다.
 3. `tfx-auto`가 intent를 mode, retry, parallelism, risk tier, 대상 CLI lane으로 정규화합니다.
-4. `tfx-route.sh`, Hub worker, 또는 `tfx` CLI가 실제 Codex/Gemini/Claude 기반 작업을 실행합니다.
+4. `tfx-route.sh`, Hub worker, 또는 `tfx` CLI가 실제 Codex/Antigravity/Claude 기반 작업을 실행합니다.
 5. Hub가 team message, lease, retry, handoff, status surface를 기록합니다.
 
 ### Hub
@@ -303,7 +308,7 @@ triflux는 위험한 실행을 관리된 경로 뒤에 둡니다.
 
 ### Profile과 모델 라우팅
 
-Codex/Gemini profile은 `tfx-profile` 또는 `tfx setup`으로 관리합니다. 이미 profile이
+Codex profile은 `tfx-profile`로 관리하고, Antigravity 및 legacy Gemini 호환 상태는 `tfx setup`/`tfx doctor`로 점검합니다. 이미 profile이
 소유한 model/effort 값을 launcher script에 중복 하드코딩하지 마세요.
 
 ---
@@ -332,7 +337,7 @@ tfx mcp remove context7
 ```
 
 registry가 관리 대상 MCP 설정의 source of truth입니다. Drift 디버깅이 아니라면
-Codex/Gemini/Claude MCP 파일을 직접 수정하지 마세요.
+Codex/Antigravity/Claude MCP 파일을 직접 수정하지 마세요.
 
 ### State snapshot
 
@@ -350,7 +355,7 @@ npm run snapshot:all
 패키지 내용에 영향이 있는 저장소 변경은 ship 전에 release gate를 통과시킵니다.
 
 ```bash
-npm run gen:skill-docs
+npm run lint:skills
 npm run gen:skill-manifest
 npm run release:check-sync
 npm run release:check-mirror
@@ -382,7 +387,7 @@ agent/launcher가 따라야 하는 더 엄격한 Windows/psmux 규칙은 `AGENTS
 | Hub token auth | 설정된 경우 Hub API에 로컬 bearer token 적용. |
 | Localhost binding | Hub 기본 bind는 `127.0.0.1`. |
 | MCP registry guard | 지원하지 않거나 stale한 MCP record를 관리형 HTTP entry로 교체. |
-| Headless guard | 비관리 Codex/Gemini headless 실행 경로 차단. |
+| Headless guard | 비관리 Codex/Antigravity headless 실행 경로와 deprecated Gemini route 차단. |
 | Safety guard | psmux/SSH/WT 셸 민감 흐름 sanitizing. |
 | Consensus reporting | deep/consensus workflow는 degraded/disputed 결과를 명시해야 함. |
 

package/README.md

@@ -8,18 +8,18 @@
   </picture>
 </p>
 
-<h3 align="center">CLI-first multi-model orchestration for Claude Code, Codex, and Gemini</h3>
+<h3 align="center">CLI-first multi-model orchestration for Claude Code, Codex, and Antigravity</h3>
 
 <p align="center">
   One front door for routing work, coordinating agents, running local/remote teams,<br>
-  and keeping Codex/Gemini/Claude execution behind auditable guards.
+  and keeping Codex/Antigravity/Claude execution behind auditable guards.
 </p>
 
 <p align="center">
   <a href="https://www.npmjs.com/package/triflux"><img src="https://img.shields.io/npm/v/triflux?style=flat-square&color=FFAF00&label=npm" alt="npm version"></a>
   <a href="https://www.npmjs.com/package/triflux"><img src="https://img.shields.io/npm/dm/triflux?style=flat-square&color=F5C242" alt="npm downloads"></a>
   <a href="https://github.com/tellang/triflux/stargazers"><img src="https://img.shields.io/github/stars/tellang/triflux?style=flat-square&color=FFAF00" alt="GitHub stars"></a>
-  <img src="https://img.shields.io/badge/skill_files-33-F5C242?style=flat-square" alt="33 skill files">
+  <img src="https://img.shields.io/badge/skill_files-34-F5C242?style=flat-square" alt="34 skill files">
   <sub>11 compatibility aliases are deprecated</sub>
   <img src="https://img.shields.io/badge/node-%3E%3D18-374151?style=flat-square" alt="Node >= 18">
   <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-374151?style=flat-square" alt="License: MIT"></a>
@@ -43,7 +43,7 @@
 ## What is triflux?
 
 triflux is a **Claude Code plugin + npm CLI** for routing AI coding work across
-Claude, Codex, and Gemini without letting ad-hoc shell commands or stale skill
+Claude, Codex, and Antigravity without letting ad-hoc shell commands or stale skill
 aliases become the control plane.
 
 The current design is intentionally simpler than the old README implied:
@@ -111,7 +111,7 @@ tfx codex-team "refactor auth + add tests"
 ```
 
 > Deep, consensus, team, and swarm paths need the relevant CLIs and a terminal
-> multiplexer. Run `tfx doctor` first; it reports missing Codex/Gemini/Claude,
+> multiplexer. Run `tfx doctor` first; it reports missing Codex/Antigravity/Claude,
 > psmux/tmux, Hub, MCP, profile, and stale-skill issues.
 
 ---
@@ -126,26 +126,31 @@ The `tfx` CLI currently exposes these primary commands:
 | --- | --- |
 | `tfx setup` | Sync scripts, HUD, hooks, MCP, and profiles. Supports `--dry-run`. |
 | `tfx doctor` | Diagnose and repair installation state. Supports `--fix`, `--reset`, `--diagnose`, `--json`. |
+| `tfx auto` | Preview the `tfx-auto` routing decision. Supports `--cli`, `--mode`, `--parallel`, `--json`. |
 | `tfx mcp` | Manage MCP registry targets with `list`, `sync`, `add`, and `remove`. |
 | `tfx hub` | Start, stop, ensure, or inspect the local MCP message bus. |
 | `tfx list` | Show installed package and user skills. |
 | `tfx handoff` | Serialize the current context for local or remote continuation. |
 | `tfx schema` | Print CLI and Hub delegator schemas. |
+| `tfx hooks` | Scan, diff, apply, restore, or inspect hook orchestrator state. |
+| `tfx tray` | Start the tray/HUD status process; use `--attach` for foreground debugging. |
 | `tfx multi` | Launch local multi-agent team mode through tmux/psmux + Hub. |
 | `tfx swarm` | Plan, preflight, run, or list PRD-based worktree-isolated swarm work. |
 | `tfx synapse` | Inspect swarm registry and leases. |
+| `tfx review` | Run Codex-backed git diff review. |
 | `tfx codex-team` | Codex-led team mode convenience wrapper. |
 | `tfx notion-read` | Convert Notion pages to Markdown through configured MCP clients. |
 | `tfx why` | Read intent trailers from the last commit touching a path. |
 | `tfx update` | Update to the latest stable or dev package. |
+| `tfx monitor` | Open the terminal TUI monitor. |
 | `tfx version` | Print version information. |
-| `tfx-profile` | Convenience binary for interactive Codex/Gemini profile management. |
+| `tfx-profile` | Convenience binary for interactive Codex profile management. |
 
 Run `tfx schema <command>` for the exact argument contract.
 
 ### Claude Code skills
 
-The package ships **33 skill files**. The important split is:
+The package ships **34 skill files**. The important split is:
 
 - **Canonical entrypoints**: `tfx-auto`, `tfx-remote`, `tfx-doctor`,
   `tfx-setup`, `tfx-profile`, `tfx-hub`, `tfx-hooks`, `tfx-ship`, `tfx-wt`.
@@ -169,7 +174,7 @@ Most old skill names now map to explicit `tfx-auto` flags:
 | debate or panel report | `/tfx-auto "task" --mode consensus --shape debate|panel` |
 | local parallel work | `/tfx-auto "task" --parallel N --mode deep` or shell `tfx multi ...` |
 | PRD/worktree swarm | `/tfx-auto "task" --parallel swarm --mode consensus --isolation worktree` or shell `tfx swarm ...` |
-| force a CLI lane | `/tfx-auto "task" --cli codex|gemini|claude` |
+| force a CLI lane | `/tfx-auto "task" --cli codex|antigravity|claude` |
 
 ### Control-plane boundaries
 
@@ -217,7 +222,7 @@ explicit. Use `--mode quick|deep|consensus` when you already know the mode.
 /tfx-auto "review the migration strategy" --mode consensus --shape panel
 ```
 
-Consensus participants are the configured Claude/Codex/Gemini lanes. If a lane is
+Consensus participants are the configured Claude/Codex/Antigravity lanes. If a lane is
 unavailable, the result should report partial/degraded status instead of hiding it.
 
 ### Local team or PRD swarm
@@ -267,8 +272,8 @@ state without replaying the entire conversation.
 graph TD
     User([User / Claude Code / shell]) --> Skills[Claude skills]
     User --> CLI[tfx CLI]
-    Skills --> Auto[/tfx-auto]
-    Skills --> Remote[/tfx-remote]
+    Skills --> Auto["/tfx-auto"]
+    Skills --> Remote["/tfx-remote"]
     CLI --> Hub[triflux Hub]
     CLI --> Team[tfx multi / swarm]
     Auto --> Route[tfx-route.sh + guards]
@@ -288,7 +293,7 @@ The common routing path is:
 2. Keyword/routing hooks may add context or choose a skill.
 3. `tfx-auto` normalizes intent into mode, retry, parallelism, risk tier, and
    target CLI lane.
-4. `tfx-route.sh`, Hub workers, or the `tfx` CLI execute the actual Codex/Gemini/
+4. `tfx-route.sh`, Hub workers, or the `tfx` CLI execute the actual Codex/Antigravity/
    Claude-backed work.
 5. Hub records team messages, leases, retries, handoffs, and status surfaces.
 
@@ -313,13 +318,13 @@ team, or MCP workflows allow localhost access if your environment requires it.
 triflux keeps risky execution behind managed routes:
 
 - CLI calls should flow through `tfx-route.sh`, Hub workers, or the `tfx` CLI.
-- Direct `codex exec` / `gemini -y` paths are guarded in the installed workflow.
+- Direct `codex exec`, unmanaged `agy`, and deprecated `gemini` routes are guarded in the installed workflow.
 - psmux/Windows Terminal flows must use the managed API and documented rules, not
   ad-hoc `wt.exe` or `psmux send-keys` snippets.
 
 ### Profiles and model routing
 
-Use `tfx-profile` or `tfx setup` to manage Codex/Gemini profiles. Do not hardcode
+Use `tfx-profile` for Codex profiles and `tfx setup`/`tfx doctor` for Antigravity plus legacy Gemini compatibility state. Do not hardcode
 model and effort flags in launcher scripts when a profile already owns them.
 
 ---
@@ -348,12 +353,11 @@ tfx mcp remove context7
 ```
 
 The registry is the source of truth for managed MCP targets. Avoid hand-editing
-Codex/Gemini/Claude MCP files unless you are intentionally debugging drift.
+Codex/Antigravity/Claude MCP files unless you are intentionally debugging drift.
 
 ### State snapshots
 
-Hub startup can take best-effort daily snapshots of selected `~/.codex/` and
-`~/.gemini/` state into ignored `references/*-snapshots/` folders. Manual helpers:
+Hub startup can take best-effort daily snapshots of selected `~/.codex/` and Antigravity/Gemini `~/.gemini/` state into ignored `references/*-snapshots/` folders. Manual helpers:
 
 ```bash
 npm run snapshot:codex
@@ -367,7 +371,7 @@ For repository changes that affect package contents, run the release gates befor
 shipping:
 
 ```bash
-npm run gen:skill-docs
+npm run lint:skills
 npm run gen:skill-manifest
 npm run release:check-sync
 npm run release:check-mirror
@@ -399,7 +403,7 @@ rules used by agents and launch scripts.
 | Hub token auth | Local bearer token for Hub APIs where configured. |
 | Localhost binding | Hub defaults to `127.0.0.1`. |
 | MCP registry guard | Replaces unsupported or stale MCP records with managed HTTP entries. |
-| Headless guard | Blocks unmanaged Codex/Gemini headless execution paths. |
+| Headless guard | Blocks unmanaged Codex/Antigravity headless execution paths and deprecated Gemini routes. |
 | Safety guard | Sanitizes shell-sensitive psmux/SSH/WT flows. |
 | Consensus reporting | Deep/consensus workflows should report degraded or disputed findings explicitly. |