@eevee-ta/cli 0.1.0-beta.1 → 1.2.0

package/assets/skills/eevee-integration/references/java-springboot.md

@@ -0,0 +1,182 @@
+# Java Spring Boot Integration
+
+Use this reference for Java 11+ Spring Boot Maven or Gradle repositories.
+
+## Inspect first
+
+Determine:
+
+- Maven or Gradle multi-module layout.
+- JDK version and Maven version.
+- Spring MessageSource basename, normally in `application*.yml`.
+- Existing resource path, such as:
+  ```yaml
+  spring:
+    messages:
+      basename: static/i18n/messages
+  ```
+- Existing resource naming:
+  ```text
+  messages_zh_CN.properties
+  messages_en_US.properties
+  messages_ja_JP.properties
+  messages_ko_KR.properties
+  ```
+- Existing wrapper scripts, Git hooks, and build validation commands.
+
+## `intl.json` shape
+
+A typical all-version, no-tag Java configuration is:
+
+```json
+{
+  "url": "https://eevee.example.com/mcp",
+  "token": "<basic-read-token-if-approved>",
+  "includes": ["**/src/main/java/**/*.java"],
+  "excludeAscii": true,
+  "excludeTrack": true,
+  "format": "properties",
+  "groupByTag": false,
+  "clean": false,
+  "localeAliases": {
+    "zh-CN": "messages_zh_CN",
+    "en-US": "messages_en_US",
+    "ja-JP": "messages_ja_JP",
+    "ko-KR": "messages_ko_KR"
+  },
+  "outPaths": [
+    {
+      "path": "/src/main/resources/static/i18n/",
+      "buildPath": "/target/classes/static/i18n/",
+      "projectIds": [
+        {
+          "projectId": 3,
+          "branchIds": []
+        }
+      ]
+    }
+  ]
+}
+```
+
+Adjust only after confirming IDs and output expectations with the user. A leading `/` in `path` or `buildPath` is repository-relative, not an absolute filesystem path.
+
+## Wrapper script
+
+Prefer `scripts/eevee-i18n.sh` with actions such as:
+
+```bash
+scripts/eevee-i18n.sh export --dry-run
+scripts/eevee-i18n.sh export
+scripts/eevee-i18n.sh export --target build
+scripts/eevee-i18n.sh scan --no-fail
+scripts/eevee-i18n.sh scan-changed
+scripts/eevee-i18n.sh check
+```
+
+`check` normally performs:
+
+1. `git diff --check`
+2. EEVEE export dry-run
+3. Full EEVEE scan with `--no-fail` for legacy visibility
+4. Blocking scan of staged Java files
+5. Maven `validate`
+
+Use `EEVEE_CLI`, `MVN_CMD`, and `MAVEN_LOCAL_REPO` overrides for developer environments.
+
+## Commit hook
+
+Use `.githooks/pre-commit` and configure:
+
+```bash
+git config core.hooksPath .githooks
+```
+
+Hook behavior:
+
+```bash
+#!/usr/bin/env bash
+set -euo pipefail
+ROOT="$(git rev-parse --show-toplevel)"
+"$ROOT/scripts/eevee-i18n.sh" scan-changed
+```
+
+`scan-changed` must collect only:
+
+```bash
+git diff --name-only --cached --diff-filter=ACMR | grep -E '\.java$'
+```
+
+Skip cleanly when there are no staged Java files. This prevents thousands of legacy findings from blocking every commit while still checking files changed by the current work.
+
+## Java suppression comments
+
+The scanner understands real Java comments, including block comments:
+
+```java
+// eevee-i18n-disable-next-line：组件内部按 key 翻译
+private String title = "操作";
+```
+
+```java
+private String title = "操作"; // eevee-i18n-disable：内部枚举显示名
+```
+
+```java
+// eevee-i18n-disable-file：本文件只维护后端返回类型标识
+```
+
+Do not put the directive inside a string; it must be an actual comment.
+
+## Validation
+
+Run in this order:
+
+1. `scripts/eevee-i18n.sh export --dry-run`
+2. Real export only after the user confirms EEVEE is the source of truth
+3. Properties consistency:
+   - same key set in every locale
+   - no duplicate keys
+   - expected key count
+   - placeholder parity where applicable
+4. `scripts/eevee-i18n.sh scan --no-fail`
+5. Positive and negative commit-hook tests:
+   - no staged Java file exits 0
+   - a staged temporary Java file with hardcoded user-visible Chinese exits non-zero
+6. Maven validation, usually:
+   ```bash
+   mvn -s settings.xml -Dmaven.repo.local="$HOME/.m2/repository" validate
+   ```
+
+On a clean repository, some Maven `banCircularDependencies` configurations resolve reactor siblings from the local repository. If validate fails with missing sibling artifacts, bootstrap once with the project's known-compatible Maven version:
+
+```bash
+mvn -s settings.xml \
+  -Dmaven.repo.local="$HOME/.m2/repository" \
+  -DskipTests install
+```
+
+Then rerun validate. Keep machine-specific credentials and repository paths out of committed settings.
+
+## Documentation to leave in the repository
+
+Record:
+
+- EEVEE project and version policy
+- whether tags are used
+- output paths and format
+- full command list
+- commit-hook scope
+- known legacy-debt count and policy
+- all non-obvious directory exclusions and suppression examples
+
+
+## Term upload requirements (source metadata)
+
+When backfilling terms extracted from Java sources or resource bundles, upload
+`source_info` (`repo`/`branch`/`path`/`line`, all four together or omitted) and
+`params` for message placeholders, plus `description` recording the class/usage
+location. `term create --translations` sets initial translations; refreshing an
+existing term's translation must go through `translation set-content` per locale
+(`term update` ignores `--translations`). Keep upload scripts idempotent by
+diffing against `eevee term list` before writing.

package/assets/skills/eevee-integration/references/umijs.md

@@ -0,0 +1,210 @@
+# UmiJS / Umi Max Integration
+
+Use this reference for Umi, Umi Max, React, TypeScript, and similar front-end repositories.
+
+## Inspect first
+
+Determine:
+
+- Monorepo app directory, such as `apps/gaia/src`, versus single-app `src`.
+- Existing locale loader and output directory:
+  - `src/locales`
+  - `public/intl`
+  - `apps/<app>/public/intl`
+- Runtime file format:
+  - JSON files loaded by `intl.js`
+  - ESM `js` / `ts` modules
+  - existing `INTL` / `COMM_INTL` maps
+- Existing i18n functions, especially `formatMessage` from `tant-intl`.
+- Existing npm scripts, lint-staged config, ESLint setup, and Git hooks.
+- Existing term maps such as `intl.ts` / `intl.tsx`.
+- Whether old ESLint plugin configuration exists and must be replaced rather than duplicated.
+
+## `intl.json` shape
+
+Single-app grouped JSON example:
+
+```json
+{
+  "includes": ["src/**/*.{ts,tsx,js,jsx}"],
+  "excludes": ["**/*.d.ts"],
+  "excludeAscii": true,
+  "excludeTrack": true,
+  "token": "<basic-read-token-if-approved>",
+  "format": "json",
+  "groupByTag": true,
+  "clean": true,
+  "localeAliases": {
+    "zh-CN": "zh",
+    "en-US": "en"
+  },
+  "outPaths": [
+    {
+      "path": "/public/intl/",
+      "buildPath": "/public/intl/",
+      "projectIds": [
+        {
+          "projectId": 12,
+          "branchIds": [21],
+          "tags": ["web"]
+        }
+      ]
+    }
+  ]
+}
+```
+
+Monorepos should use app-specific paths and include globs. Confirm project, version, tags, grouping, aliases, and both output directories with the user before writing this file.
+
+For ESM output, use `format: "js"` or `"ts"`:
+
+```js
+export default {
+  登录: 'Sign in',
+};
+```
+
+## npm scripts
+
+Prefer wrappers that call the local CLI:
+
+```json
+{
+  "scripts": {
+    "eevee": "eevee",
+    "eevee:export": "eevee i18n export",
+    "eevee:i18n": "eevee i18n scan",
+    "eevee:check": "eevee doctor"
+  }
+}
+```
+
+A shell wrapper can add `--no-update-check`, verify CLI version, and route `scan-changed` / `check`.
+
+## Scanner behavior and false-positive handling
+
+The CLI scans:
+
+- JavaScript / TypeScript strings
+- template literals
+- JSX text
+- Vue text where applicable
+
+It ignores by default:
+
+- pure ASCII when `excludeAscii: true`
+- import/export source strings
+- object property keys
+- tracking calls
+- tests, mocks, fixtures, generated Umi directories, and build outputs
+- standard i18n expressions inside template interpolation
+- member expressions such as `INTL.操作`
+
+Nonstandard patterns are not automatically exempt. Use explicit comments:
+
+```ts
+// eevee-i18n-disable-next-line：动态拼接词条字典 key
+const title = REPO_INTL[`${isEdit ? '编辑' : '新建'}表`];
+```
+
+```ts
+title: '操作', // eevee-i18n-disable：表格组件内部按 key 翻译
+```
+
+For a whole term-key map:
+
+```ts
+// eevee-i18n-disable-file：本文件只维护词条 key
+```
+
+Column arrays such as `COLUMN_DEFAULT_ALL` often need line-level comments when the table component translates keys internally. Add the comment to every affected title rather than suppressing an entire page file.
+
+## Commit gate
+
+Use a Git hook or lint-staged task that scans only staged frontend source files. A dedicated `scan-changed` script is easier to test than embedding complex shell in Git configuration.
+
+Collect staged files with:
+
+```bash
+git diff --name-only --cached --diff-filter=ACMR |
+  grep -E '\.(js|jsx|ts|tsx|vue)$'
+```
+
+Pass each file to:
+
+```bash
+eevee i18n scan . --include <file>
+```
+
+Skip when no matching file is staged.
+
+For legacy repositories, full scanning can remain informational with `--no-fail`; only staged files should block commits.
+
+## Validation
+
+Run:
+
+1. `npm run eevee -- version`, requiring CLI `>= 1.1.0`
+2. Export dry-run and confirm expected project/version/tag/key counts
+3. Real export only after confirming source of truth and cleanup behavior
+4. Locale consistency:
+   - same key set
+   - expected count
+   - no duplicate keys
+   - runtime loader still references generated filenames
+5. `eevee i18n scan --no-fail`
+6. Blocking scan of staged source files
+7. Existing project checks:
+   ```bash
+   npm run tsc
+   npm run build
+   ```
+8. If ESLint integration changed, run the project's JS lint command and remove obsolete plugin configuration/dependencies.
+
+## Documentation to leave in the repository
+
+Record:
+
+- project IDs and version IDs
+- tag semantics and grouping
+- output paths and format
+- locale aliases
+- npm or shell commands
+- commit gate scope
+- known false-positive categories and suppression examples
+- legacy-debt policy and files or directories intentionally excluded
+
+## Term upload requirements (source metadata)
+
+When a repository uploads or backfills terms to EEVEE (for example a
+`eevee:upload` wrapper around `eevee term create`), each term entry should carry
+source metadata, not only translations:
+
+| Field | Required | Shape / rule |
+|---|---|---|
+| `name` | yes | Term key. In zh-reference projects the key is usually the Chinese source text. |
+| `translations` | yes | Map covering **every** project locale; use `""` only when explicitly intended. |
+| `description` | recommended | Where the term appears, e.g. `顶栏导航：项目`. |
+| `params` | recommended | Placeholder parameter array `[{"name":"count","value":"42","desc":"数量"}]`. Upload it whenever the source text contains `{placeholder}` tokens so translators see the parameter contract. |
+| `source_info` | recommended | Repository origin `{"repo","branch","path","line"}`. All four fields must be filled together or omitted entirely (server rejects partial objects). Capture them from the file location / git revision at extraction time. |
+
+Update semantics that scripts must respect:
+
+- `term create --translations` is the only batch way to set initial translations.
+- `term update` does **not** accept `--translations` (the server ignores it);
+  refresh existing translations per locale with
+  `eevee translation set-content --id <pid> --term-id <tid> --locale <locale> --content <text>`.
+- Keep uploads idempotent: diff against `eevee term list`/`terms/page` first and
+  only write created terms plus drifted locales.
+
+A minimal idempotent upload wrapper therefore looks like:
+
+```bash
+eevee term list <project-id> --version-id <version-id> --json   # remote baseline
+eevee term create <project-id> <version-id> --name <key> \
+  --description "<location>" \
+  --params '[{"name":"count","value":"42","desc":"数量"}]' \
+  --source-info '{"repo":"org/web","branch":"main","path":"src/page.tsx","line":12}' \
+  --translations '{"zh-CN":"共 {count} 条","en-US":"{count} items"}'
+eevee translation set-content --id <project-id> --term-id <tid> --locale en-US --content "{count} items"
+```

package/assets/skills/eevee-mcp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: eevee-mcp
-description: Operate eevee through the @eevee/cli business commands—projects, versions, terms, translations, tags, permissions, logs—and retain access to raw MCP tools/resources/prompts.
+description: Operate eevee through the @eevee-ta/cli business commands—projects, versions, terms, translations, tags, permissions, logs—and retain access to raw MCP tools/resources/prompts.
 ---
 
 # eevee business-aware MCP skill
@@ -14,6 +14,9 @@ Use this skill when a user asks Codex/Claude or another terminal Agent to inspec
 3. Destructive delete/clear operations require explicit `--yes`; ask the user first if they did not request deletion.
 4. Report actual response data verbatim. If `isError=true`, stop and show the error instead of inventing fields.
 5. Keep the user's personal token private; never print it or put it in code/docs/tests.
+6. Before creating a term or setting/updating translations, search existing terms in the same project/version and inspect their translations. Use those translations as terminology, tone, placeholder, capitalization, and style references before machine-translating the new content.
+7. Every term should normally provide content for every locale configured by the project. Leave a locale as `""` only when the user explicitly says that locale must remain an empty string.
+8. When creating or maintaining terms, enrich metadata best effort — description, `params` for placeholders, `source_info` when a repo location is known, and doc-link attachments. If the context is missing, ask once instead of silently omitting it; never force the user to provide everything.
 
 ## First-run setup
 
@@ -56,17 +59,93 @@ eevee project list
 eevee project create --name Demo --locales zh-CN,en-US --description '示例项目'
 eevee project detail 12
 eevee version list 12
-eevee version create --id 12 --name 'Release 1' --status 2
+eevee version create --id 12 --name 'Release 1' --deadline-date 2026-12-31
 eevee term create --id 12 --version-id 34 --name login.button \
   --translations '{"zh-CN":"登录","en-US":"Sign in"}'
 eevee translation set-content --id 12 --term-id 56 --locale zh-CN --content 登录
-eevee translation assign-translators --id 12 --locales zh-CN,en-US --translator-ids 2,3
+eevee translation assign-translators --id 12 --locale en-US --user-id 3 --term-ids 56,57
 eevee permission list 12
 eevee log list --id 12 --page 1 --page-size 20
 ```
 
+Version status starts at 待开始 on create; change it afterwards with
+`eevee version set-status`. Translation status ceiling depends on role:
+translator → 已翻译(3), reviewer/admin → 已审核(4), plain member → 已机翻(2).
+
 Add `--json` for machine-readable `{ok,data}` output, or `--raw` to inspect the complete MCP result.
 
+## Local source i18n scan
+
+When the user asks to inspect a repository for hardcoded Chinese UI terms or Spring Boot i18n compatibility, run the packaged local scanner instead of shelling out to ESLint:
+
+```bash
+eevee i18n scan <project-dir> --json
+```
+
+The command preserves the legacy `intl.json` ESLint-plugin options and also scans Java source, Java text blocks, Thymeleaf/JSP/Freemarker/Velocity templates, JS/TS strings, templates, JSX, and Vue files. It ignores tests, mocks, fixtures, generated Umi directories, and i18n expressions inside template interpolation. A non-zero exit code means issues were found.
+
+## Configured term export
+
+When the user asks to download or refresh locale files from eevee, inspect `intl.json` and run:
+
+```bash
+eevee i18n export                 # path / development directory
+eevee i18n export --target build  # buildPath / online directory
+```
+
+`branchIds` is a required list of version IDs; `[]` means all versions. `tags: []` means all terms; `tags: [null]` means terms without tags. Output supports JSON, ESM JS/TS, and Java properties, optional tag grouping, locale filename aliases, and configurable cleanup. Projects, versions, and tags are processed in configuration order; later entries overwrite duplicate keys when bundles are merged.
+
+## Enrich term metadata (best effort)
+
+Term quality depends on context, not only translations. When creating or
+maintaining terms, upload as much of the following as the user's context
+provides. Nothing below is mandatory — pass it whenever it is available:
+
+| Field | When to include | How to collect |
+|---|---|---|
+| version | Always resolve explicitly | Single-version project: use that version. Multi-version project: ask the user which version owns the term before creating it. |
+| description | Whenever the usage location is known | e.g. `顶栏导航：项目`, `设置页 → 保存按钮`. |
+| params | Source text contains `{placeholder}` tokens | `--params '[{"name":"count","value":"42","desc":"数量"}]'` extracted from the call site; translators rely on this contract. |
+| source_info | The term comes from a repository/file the user can point to | `--source-info '{"repo":"org/web","branch":"main","path":"src/page.tsx","line":12}'` from the file location and git revision. All four fields together, or omit entirely. |
+| attachments | The user mentions screenshots, design specs, or docs | Design/doc URLs: `eevee term add-doc-link --id <pid> --term-id <tid> --link <url>`. Local screenshot files cannot be uploaded through MCP (multipart is unsupported) — tell the user to attach those in the web UI. |
+
+The same enrichment applies to existing terms — backfill metadata with:
+
+```bash
+eevee term update --id <pid> --term-id <tid>   --description '设置页 → 保存按钮'   --params '[{"name":"count","value":"42","desc":"数量"}]'   --source-info '{"repo":"org/web","branch":"main","path":"src/page.tsx","line":12}'
+```
+
+Translations themselves are refreshed per locale with `translation set-content`.
+
+## Required translation workflow
+
+Apply this workflow to `term create` and `translation set-content`:
+(`term update` only edits name/description/params/source_info — translations are
+changed with `translation set-content`, one locale at a time.)
+
+1. Read project detail or use another authoritative source to determine all project locales and the reference locale.
+2. Search/list existing terms in the same project, preferably the same version and similar namespace or terminology, for example:
+
+   ```bash
+   eevee term list <project-id> --version-id <version-id> --json
+   eevee term detail <project-id> --term-id <similar-term-id> --json
+   ```
+
+3. Extract existing translations and use them as references for terminology, tone, placeholder handling, capitalization, punctuation, and product-specific wording. Do not blindly translate in isolation.
+4. Machine-translate the missing or changed content while keeping the source meaning and reference conventions consistent.
+5. Upload a complete translation map with `term create --translations`; when using `translation set-content`, fill every missing locale unless it is intentionally empty.
+6. Before upload, verify that every key matches a project locale exactly and that no configured locale is omitted. Use `""` only when the user explicitly requires an empty value for that locale.
+
+Example:
+
+```bash
+eevee term create <project-id> <version-id> --name login.button \
+  --description '登录页 → 提交按钮' \
+  --params '[{"name":"retry","value":"3","desc":"重试次数"}]' \
+  --source-info '{"repo":"org/web","branch":"main","path":"src/pages/login.tsx","line":42}' \
+  --translations '{"zh-CN":"登录","en-US":"Sign in","ja-JP":"ログイン"}'
+```
+
 ## Fallback: raw server tools
 
 The current eevee MCP server exposes three REST-backed tools. Use these only for an operation not yet represented by the business catalog, or while diagnosing it:
@@ -94,6 +173,11 @@ Always inspect current capability with `eevee tools list`; future servers may ex
 
 ## Other standard MCP surfaces
 
+The current eevee server implements only `initialize`, `ping`, `tools/*`, and
+`notifications/initialized`. The commands below fail with `Method not found`
+against it; use them only when `eevee tools list` confirms the connected server
+actually exposes resources/prompts.
+
 ```bash
 eevee resources list
 eevee resources templates

package/assets/skills/eevee-mcp/reference.md

@@ -1,4 +1,4 @@
-# @eevee/cli reference for Agents
+# @eevee-ta/cli reference for Agents
 
 ## Command model
 
@@ -39,15 +39,42 @@ eevee project delete 86 --yes --json
 eevee version list 86
 eevee version create --id 86 --name v1
 eevee term list 86
-eevee term set-tags --id 86 --version-id 9 --term-id 22 --tag-ids 3,4
+eevee term set-tags --id 86 --term-id 22 --tag-ids 3,4
+eevee version set-status --id 86 --version-id 9 --status 2
 
 # Translations
+eevee term list 86 --json
+eevee term detail 86 --term-id 22 --json
 eevee translation set-content --id 86 --term-id 22 --locale en-US --content Hello
 eevee translation set-status --id 86 --term-id 22 --locale en-US --status 3
 ```
 
 Use the returned IDs from live responses rather than examples above.
 
+### Translation completeness workflow
+
+Before `term create` or `translation set-content` — `term update` does not accept `--translations`; change existing translations one locale at a time with `translation set-content`:
+
+1. Determine all locales configured on the project.
+2. Search existing terms in the same project/version and read their details to collect comparable translations.
+3. Use those translations as terminology and style references when machine-translating the new content.
+4. Provide content for every configured locale in principle. An empty string is allowed only when the user explicitly requests that locale to remain empty.
+5. Re-check locale keys before upload; do not invent locales that the project has not configured.
+
+## Term metadata enrichment (best effort)
+
+When creating or maintaining terms, fill every field the context can provide —
+none are mandatory, but pass them whenever possible:
+
+- Confirm the owning version first (single version: use it; multi-version: ask the user).
+- `--description` for the usage location, e.g. `设置页 → 保存按钮`.
+- `--params '[{"name":"count","value":"42","desc":"数量"}]'` whenever the text has `{placeholder}` tokens.
+- `--source-info '{"repo":"...","branch":"...","path":"...","line":12}'` when the term comes from a repository (all four fields together or omitted).
+- Design/doc links with `eevee term add-doc-link --id <pid> --term-id <tid> --link <url>`;
+  local screenshot files must be attached in the web UI (MCP cannot upload multipart files).
+- Backfill existing terms with `term update --description/--params/--source-info`;
+  refresh translations per locale with `translation set-content`.
+
 ## Built-in MCP tool fallbacks
 
 | Server tool | Purpose | Invocation |
@@ -60,6 +87,8 @@ Check `eevee tools list` first; it is authoritative if the server adds tools lat
 
 ## Full MCP surface
 
+Capability note: the current eevee server implements only `initialize`, `ping`, `tools/*`, and `notifications/initialized`. The resources/prompts/completion/logging requests below return `Method not found` against it; verify with `eevee tools list` before using them on a different server.
+
 ```bash
 eevee ping
 eevee tools list [--raw|--json]