chore: update trellis workflow and editor settings

.trellis/workflow.md

@@ -147,15 +147,15 @@ python3 ./.trellis/scripts/get_context.py --mode phase --step <X.Y>  # detailed
 ## Phase Index
 
 ```
-Phase 1: Plan    → classify, get task-creation consent, then write planning artifacts
+Phase 1: Plan    → classify, get task-creation consent when a task is needed, then write planning artifacts
 Phase 2: Execute → implement only after task status is in_progress
 Phase 3: Finish  → verify, update spec, commit, and wrap up
 ```
 
 ### Request Triage
 
-- Simple conversation or small task: ask only whether this turn should create a Trellis task. If the user says no, skip Trellis for this session.
-- Complex task: ask whether you may create a Trellis task and enter planning. If the user says no, do not do broad inline implementation; explain, clarify scope, or suggest a smaller split.
+- Direct work, no task: answer-only requests; read-only diagnosis; and narrow, explicitly requested Git operations such as status, log, diff, branch inspection, staging, committing, merging, rebasing, or pushing. Execute them directly without asking about a Trellis task. Normal Git safety and authorization rules still apply.
+- Implementation, refactoring, behavior changes, or work that needs planning: ask whether you may create a Trellis task and enter planning. If the user says no, do not do broad inline implementation; explain, clarify scope, or suggest a smaller split.
 - User approval to create a task is not approval to start implementation. Planning still happens first.
 
 ### Planning Artifacts
@@ -177,9 +177,9 @@ Create new children with `task.py create "<title>" --slug <name> --parent <paren
 <!-- Per-turn breadcrumb: shown when there is no active task (before Phase 1) -->
 
 [workflow-state:no_task]
-No active task. First classify the current turn and ask for task-creation consent before creating any Trellis task.
-Simple conversation / small task: ask only whether this turn should create a Trellis task. If the user says no, skip Trellis for this session.
-Complex task: ask the user if you can create a Trellis task and enter the planning phase. If the user says no, explain, clarify scope, or suggest a smaller split.
+No active task. First classify the current turn.
+Do not ask about a Trellis task for answer-only requests, read-only diagnosis, or narrow, explicitly requested Git operations. Execute those directly; preserve normal Git safety and authorization rules.
+For implementation, refactoring, behavior changes, or work that needs planning, ask the user if you can create a Trellis task and enter the planning phase. If the user says no, explain, clarify scope, or suggest a smaller split.
 [/workflow-state:no_task]
 
 <!-- Per-turn breadcrumb: shown when the active task record cannot be read. -->
@@ -318,7 +318,7 @@ python3 ./.trellis/scripts/get_context.py --mode phase --step <step>
 
 ## Phase 1: Plan
 
-Goal: classify the request, get task-creation consent when a task is needed, and produce the planning artifacts required before implementation.
+Goal: classify the request, bypass Trellis for direct work, get task-creation consent for work that needs planning, and produce the planning artifacts required before implementation.
 
 #### 1.0 Create task `[required · once]`
 
@@ -662,7 +662,7 @@ This section is for developers who want to modify the Trellis workflow itself. A
 ### Changing what a step means
 
 Edit the corresponding step's walkthrough body in the Phase 1 / 2 / 3 sections above. Critical invariants:
-- No active task must triage first and ask for task-creation consent before creating a Trellis task.
+- No active task must triage first; direct work bypasses Trellis, while work that needs planning asks for task-creation consent before creating a Trellis task.
 - Planning must distinguish lightweight PRD-only tasks from complex tasks that require `prd.md`, `design.md`, and `implement.md` before start.
 - Every required execution path must keep the Phase 3.4 commit reminder reachable before `/trellis:finish-work`.
 

.vscode/settings.json

@@ -25,5 +25,8 @@
     "[jsonc]": {
         "editor.defaultFormatter": "oxc.oxc-vscode",
         "editor.formatOnSave": true
-    }
+    },
+    "commentTranslate.targetLanguage": "zh-CN",
+    "commentTranslate.source": "Bing",
+    "commentTranslate.browse.mode": "inplace"
 }