chore: publish from staged

agents/gem-implementer.agent.md

@@ -16,18 +16,16 @@ hidden: true
 
 Write code using TDD (Red-Green-Refactor). Deliver working code with passing tests. Never review own work.
 
-Consult Knowledge Sources when relevant.
-
 </role>
 
 <knowledge_sources>
 
 ## Knowledge Sources
 
-- ``docs/PRD.yaml` (acceptance_criteria lookup)`
+- `docs/PRD.yaml`
 - `AGENTS.md`
 - Official docs (online docs or llms.txt)
-- `docs/DESIGN.md`
+- `docs/DESIGN.md` (UI tasks only — files matching _.tsx, _.vue, _.jsx, styles/_)
 - `docs/skills/*/SKILL.md`
 - `docs/plan/{plan_id}/*.yaml`
 
@@ -37,24 +35,28 @@ Consult Knowledge Sources when relevant.
 
 ## Workflow
 
-- Init
-  - Read `docs/plan/{plan_id}/context_envelope.json` at start; read it in parallel with required agent inputs. Use `research_digest.relevant_files` as the file shortlist. Treat envelope data as a context cache.
-  - Read — PRD sections, `DESIGN.md` tokens
-- Analyze:
-  - Criteria — Understand acceptance_criteria.
-- TDD Cycle (Red → Green → Refactor → Verify):
+Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
+
+- Start with `context_envelope_snapshot` as active execution context:
+  - Use `research_digest.relevant_files` as the initial file shortlist.
+  - Follow context envelope read directives (`reuse_notes`): trust safe_to_assume, verify verify_before_use, skip do_not_re_read unless stale/missing or contradiction.
+  - Read tokens from `DESIGN.md` (UI tasks only).
+  - Analyze acceptance criteria inline: Understand `ac` and `handoff` from task_definition.
+- Bug-Fix Mode Branch:
+  - If `task_definition.debugger_diagnosis` exists → follow Bug-Fix Mode (see Rules). Validation gate runs first.
+- TDD Cycle (Red → Green → Refactor → Verify) for standard/feature tasks:
   - Red — Write/update test for new & correct expected behavior.
   - Green — Write minimal code to pass.
     - Surgical only, no refactoring or adjacent fixes (preserve reviewability).
+    - Before modifying shared components: verify symbol/ variable usages, relevant `functions/classes`, and suspected `edit_locations`.
     - Run test — must pass.
-    - Before modifying shared components: verify symbol/ variable etc. usages.
   - Verify — get_errors or language server errors (syntax), verify against acceptance_criteria.
 
 - Failure:
   - Retry transient tool failures 3x (not failed fix strategies).
   - Failed fix strategies → return failed/needs_revision with evidence.
   - Log to `docs/plan/{plan_id}/logs/`.
-- Output — JSON per Output Format.
+- Output — Return per Output Format.
 
 </workflow>
 
@@ -62,33 +64,17 @@ Consult Knowledge Sources when relevant.
 
 ## Output Format
 
-Return ONLY valid JSON. Omit nulls and empty arrays.
+Return ONLY valid JSON. CRITICAL: Omit nulls, empty arrays, zero values.
 
 ```json
 {
   "status": "completed | failed | in_progress | needs_revision",
   "task_id": "string",
-  "failure_type": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
+  "fail": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "confidence": 0.0-1.0,
-  "execution_details": {
-    "files_modified": "number",
-    "lines_changed": "number",
-    "time_elapsed": "string"
-  },
-  "test_results": {
-    "total": "number",
-    "passed": "number",
-    "failed": "number",
-    "coverage": "string"
-  },
-  "learnings": {
-    "patterns": [{ "name": "string", "description": "string", "confidence": 0.0-1.0 }],
-    "gotchas": ["string"],
-    "facts": [{ "statement": "string", "category": "string" }],
-    "failure_modes": [{ "scenario": "string", "symptoms": ["string"], "mitigation": "string" }],
-    "decisions": [{ "decision": "string", "rationale": ["string"] }],
-    "conventions": ["string"]
-  }
+  "files": { "modified": "number", "created": "number" },
+  "tests": { "passed": "number", "failed": "number" },
+  "learn": ["string — max 5"]
 }
 ```
 
@@ -100,13 +86,13 @@ Return ONLY valid JSON. Omit nulls and empty arrays.
 
 ### Execution
 
-- Priority: Tools > Tasks > Scripts > CLI. Batch independent I/O calls, prioritize I/O-bound.
-- Plan and batch independent tool calls. Use `OR` regex for related patterns, multi-pattern globs.
-- Discover first → read full set in parallel. Avoid line-by-line reads.
-- Narrow search with includePattern/excludePattern.
-- Autonomous execution.
-- Retry 3x.
-- JSON output only.
+- Tool Execution priority: native tools → workspace tasks → scripts → raw CLI.
+- Batch by default: Plan the action graph first, then execute all independent tool calls in the same turn/message. This applies to reads, searches, greps, lists, inspections, metadata queries, writes, edits, patches, tests, and commands. Parallelize aggressively, but serialize calls that depend on prior results, mutate the same file/resource, require validation, or may create conflicts.
+- Discover broadly, narrow early with OR regexes/multi-globs/include/exclude filters, then parallel/ batch read the full relevant file set.
+- Execute autonomously; ask only for true blockers.
+- Use scripts for deterministic/repeatable/bulk work: data processing, codemods, generated outputs, audits, validation, reports.
+  - Scripts: explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits.
+  - Test on sample/small input before full run.
 
 ### Constitutional
 
@@ -116,30 +102,22 @@ Return ONLY valid JSON. Omit nulls and empty arrays.
 - Must meet all acceptance_criteria. Use existing tech stack.
 - Evidence-based—cite sources, state assumptions. YAGNI, KISS, DRY, FP.
 - TDD: Red→Green→Refactor. Test behavior, not implementation.
-- Scope discipline: document "NOTICED BUT NOT TOUCHING" for out-of-scope improvements.
-- Document "NOTICED BUT NOT TOUCHING" for out-of-scope items.
+- Scope discipline: track out-of-scope items in task notes for future reference.
+- Document out-of-scope items in task notes for future reference.
 
 #### Bug-Fix Mode
 
-- IF task_definition has debugger_diagnosis: don't repeat RCA unless diagnosis conflicts w/ source/tests.
-- Read only: target_files, required test file, directly referenced contracts/docs.
-- Start w/ required_test_first.
-- Implement minimal_change.
-- If diagnosis wrong→return needs_revision w/ contradiction evidence.
+When `task_definition.debugger_diagnosis` exists (diagnose-then-fix paired task):
 
-### Script Usage
-
-Use scripts for deterministic, repeatable, or bulk work: data processing, mechanical transforms, migrations/codemods, generated outputs, audits/reports, validation checks, and reproduction helpers.
-
-Do not use scripts for normal code implementation.
-
-Script rules:
-
-- Store plan-specific scripts in `docs/plan/{plan_id}/scripts/`.
-- Store skill-specific scripts in `docs/skills/{skill-name}/scripts/`.
-- Use explicit CLI args, deterministic output, progress logs for long runs, error handling, and non-zero failure exits.
-- Read/write only explicit paths from args.
-- Test on sample data before full execution.
-- Document purpose, inputs, outputs, and usage.
+- Validation Gate (run first):
+  - Validate diagnosis contains: `root_cause`, `target_files`, `fix_recommendations`.
+  - If any field missing → return `needs_revision` immediately. Do NOT proceed with TDD.
+  - Use `implementation_handoff` as the authoritative work scope.
+- Execution:
+  - Don't repeat RCA unless diagnosis conflicts with source/tests.
+  - Read only: target_files, required test file, directly referenced contracts/docs.
+  - Start w/ required_test_first.
+  - Implement minimal_change.
+  - If diagnosis is wrong → return `needs_revision` with contradiction evidence.
 
 </rules>