Please address the comments from this code review:

## Overall Comments
- The JSDoc for `resolveI18nInObject` says it only resolves `$`-prefixed i18n strings, but the implementation currently resolves all string values; consider aligning the logic with the documented `$` prefix behavior to avoid unintentionally rewriting non-i18n fields (e.g., IDs or keys).
- In `maaService.startTasks`, `piEnvs` is only forwarded when `hasAgent` is true; if the intent is that the backend always receives a value when `piEnvs` is computed, even for future non-agent use, you may want to decouple the `piEnvs` parameter from `hasAgent`.

## Individual Comments

### Comment 1
<location path="src/utils/piEnv.ts" line_range="18-41" />
<code_context>
+ * 递归解析对象中所有 `$` 开头的 i18n 字符串字段。
+ * 返回的新对象中 label、description 等字段已替换为最终展示文本。
+ */
+function resolveI18nInObject(
+  obj: Record<string, unknown>,
+  translations?: Record<string, string>,
+): Record<string, unknown> {
+  const resolved: Record<string, unknown> = {};
+  for (const [key, value] of Object.entries(obj)) {
+    if (typeof value === 'string') {
+      resolved[key] = resolveI18nText(value, translations);
+    } else if (Array.isArray(value)) {
+      resolved[key] = value.map((item) =>
+        typeof item === 'object' && item !== null
+          ? resolveI18nInObject(item as Record<string, unknown>, translations)
+          : typeof item === 'string'
+            ? resolveI18nText(item, translations)
+            : item,
+      );
+    } else if (typeof value === 'object' && value !== null) {
+      resolved[key] = resolveI18nInObject(value as Record<string, unknown>, translations);
+    } else {
+      resolved[key] = value;
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Consider limiting i18n resolution to fields that are actually i18n keys to avoid unintended transformations.

Right now every string (including nested ones) is passed to resolveI18nText. If resolveI18nText can modify non-key strings, this risks changing values like IDs or URLs, and also does extra work. If you have a convention such as "$"-prefixed keys, consider checking that before calling resolveI18nText so only true i18n keys are processed.

```suggestion
function resolveI18nInObject(
  obj: Record<string, unknown>,
  translations?: Record<string, string>,
): Record<string, unknown> {
  const resolved: Record<string, unknown> = {};
  for (const [key, value] of Object.entries(obj)) {
    if (typeof value === 'string') {
      // 仅对以 `$` 开头的字符串视为 i18n key 进行解析，避免误处理普通字符串（如 ID、URL 等）
      resolved[key] = value.startsWith('$') ? resolveI18nText(value, translations) : value;
    } else if (Array.isArray(value)) {
      resolved[key] = value.map((item) =>
        typeof item === 'object' && item !== null
          ? resolveI18nInObject(item as Record<string, unknown>, translations)
          : typeof item === 'string'
            ? item.startsWith('$')
              ? resolveI18nText(item, translations)
              : item
            : item,
      );
    } else if (typeof value === 'object' && value !== null) {
      resolved[key] = resolveI18nInObject(value as Record<string, unknown>, translations);
    } else {
      resolved[key] = value;
    }
  }
  return resolved;
}
```
</issue_to_address>

Please address the comments from this code review:

## Overall Comments
- In `resolvePiI18nText`, using `translations?.[key] || key` will treat an empty translated string as missing; consider explicitly checking `key in translations` (or `translations?.[key] !== undefined`) so valid empty translations are preserved.
- In `maaService.startTasks`, `piEnvs` is passed through from callers and then conditionally nulled when `hasAgent` is false; to avoid future call sites accidentally omitting PI_* metadata, consider centralizing the `buildPiEnvVars` call inside `startTasks` (based on store state) instead of requiring each UI component to construct and forward it.