chore: sync upstream feat/v0.6.0-beta into main (preserve i18n)

.agents/skills/first-principles-thinking/SKILL.md

@@ -251,8 +251,8 @@ During `/trellis:brainstorm`, when the task is classified as "Complex":
 2. **Execute**: Run Phases 0-3, saving output to `fp-analysis.md` in task directory
 3. **Feed into PRD**:
    - Ground Truths → PRD Requirements and Constraints
-   - Assumption Table → PRD Technical Notes / Trade-offs
-   - Reasoning Chain → PRD Technical Design or `info.md`
+   - Assumption Table → design.md Trade-offs
+   - Reasoning Chain → `design.md`
 4. **Continue**: Phases 4-5 inform implementation decisions
 
 ### Context Injection

.agents/skills/trellis-before-dev/SKILL.md

@@ -7,28 +7,34 @@ Read the relevant development guidelines before starting your task.
 
 Execute these steps:
 
-1. **Discover packages and their spec layers**:
+1. **Read current task artifacts**:
+   - `prd.md` for requirements and acceptance criteria
+   - `design.md` if present for technical design
+   - `implement.md` if present for execution order and validation plan
+
+2. **Discover packages and their spec layers**:
    ```bash
    python3 ./.trellis/scripts/get_context.py --mode packages
    ```
 
-2. **Identify which specs apply** to your task based on:
+3. **Identify which specs apply** to your task based on:
    - Which package you're modifying (e.g., `cli/`, `docs-site/`)
    - What type of work (backend, frontend, unit-test, docs, etc.)
+   - Any spec/research paths referenced by the task artifacts
 
-3. **Read the spec index** for each relevant module:
+4. **Read the spec index** for each relevant module:
    ```bash
    cat .trellis/spec/<package>/<layer>/index.md
    ```
    Follow the **"Pre-Development Checklist"** section in the index.
 
-4. **Read the specific guideline files** listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`). Read those files to understand the coding standards and patterns.
+5. **Read the specific guideline files** listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., `error-handling.md`, `conventions.md`, `mock-strategies.md`). Read those files to understand the coding standards and patterns.
 
-5. **Always read shared guides**:
+6. **Always read shared guides**:
    ```bash
    cat .trellis/spec/guides/index.md
    ```
 
-6. Understand the coding standards and patterns you need to follow, then proceed with your development plan.
+7. Understand the coding standards and patterns you need to follow, then proceed with your development plan.
 
 This step is **mandatory** before writing any code.