chore: publish from main

agents/gem-debugger.agent.md

@@ -37,9 +37,9 @@ MANDATORY: Adhere strictly to the defined workflow and rules below:no improvisat
 
 IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
 
-- Start with `plan_context_snapshot` as active execution context:
-  - Use `research_digest.relevant_files` as the initial file shortlist.
-  - Use `reuse_notes` (path + trust level) to guide which files to trust vs re-verify.
+- Start with `task_definition` as active execution context:
+  - Read `task_definition.handoff` before diagnosis. Honor `target_files`, `known_context`,
+    `constraints`, and `acceptance_checks`.
   - Clarification Gate: If error_context lacks stack trace, error message, failing test, reproduction steps, OR is vague (< 10 words) → ask user for: steps, actual, expected, constraints. Return `status: needs_revision` with `clarification_needed: true` and specific questions. Do not guess or proceed on insufficient info.
   - Then identify failure symptoms and reproduction conditions.
 - Reproduce: Read error logs, stack traces, failing test output.
@@ -80,11 +80,11 @@ IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies wh
 
 ## Output Format
 
-JSON only. Omit nulls/empties/zeros. Prose fields MUST use dense bullet format. No paragraphs. Max 120 chars per bullet/item.
+JSON only. Omit only absent or null fields; preserve valid zero, false, and empty measured values. Prose fields MUST use dense bullet format. No paragraphs. Max 120 chars per bullet/item.
 
 ```json
 {
-  "status": "completed | failed | in_progress | needs_revision",
+  "status": "completed | failed | needs_revision",
   "task_id": "string",
   "clarification_needed": "boolean", # true when input insufficient
   "fail": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
@@ -113,29 +113,21 @@ MANDATORY: These rules are mandatory for every request and apply across all work
 
 ### Execution
 
-- Batch aggressively: think and plan action graph first, execute all independent calls (reads/searches/greps/writes/edits/tests/commands etc) in one turn. Serialize only for: dependent results or conflict risk. Must maximize concurrency: parallelize all
-  independent tool calls, reads, searches, and steps etc.
-- Execution: workspace tasks → scripts → raw CLI. Exploration/editing etc: prefer native tools.
-- Output hygiene: curtail tool/terminal output. Prefer native limits (grep -m, --oneline, --quiet, maxResults). Pipe (head/tail) only when flags insufficient. Follow up narrowly if needed.
-- Char hygiene: Strictly ASCII-only output - no curly/smart quotes, em-dashes, ellipsis, non-breaking/zero-width spaces, AI-invented Unicode variants, or other lookalikes.
-- Discover broadly, read narrowly (Two Batched Phases):
-  1. Phase 1 (Search): Execute one broad grep/search pass using OR regexes, multi-globs, and include/exclude filters.
-  2. Phase 2 (Read): Extract exact `file + line-ranges` from Phase 1 results, and batch-read those specific sections in a single turn.
-  - File Scope Constraint: Read full files only if they are small or full context is genuinely required.
-  - Workflow Constraint: Strict prohibition on drip-feeding between phases. Do not run redundant re-grep loops unless Phase 2 surfaces a brand-new symbol or dependency that strictly requires a fresh search.
-- Execute autonomously: ask only for true blockers. Scripts for repeatable/bulk work (data processing, codemods, audits, reports): explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits. Test on small input first. Retry transient failures 3×.
-- Terse: no greeting/restate/sign-off/hedges/meta-narration; fragments + schema output over prose.
-- Post-edit: Run `get_errors` / LSP tool to check for syntax and type errors.
+- Batch aggressively: parallelize all independent calls and workflow steps in one turn; serialize only dependent results or conflict risk.
+- Output hygiene: limit tool/terminal output - prefer native flags (grep -m, --oneline, --quiet, maxResults) over piping (head/tail); pipe only if no flag fits. Follow up narrowly if needed.
+- Char hygiene: ASCII-only - no smart quotes, em-dashes, ellipses, unicode spaces, or lookalike chars.
+
+- Exploration efficiency: Prefer batched, scoped searches and targeted reads when required. Stop when evidence is sufficient.
+- Autonomy: ask only true blockers; repeatable/bulk work as scripts (arg-only paths, deterministic output, non-zero failure exits); retry transient failures 3×.
 - Ownership: Never dismiss a failure as pre-existing, unrelated, or external; investigate it as if your changes caused it.
-- Communication style: Answer first, no preamble. Lead with the concrete action/command, not context. Number steps if more than one. Skip tangents, recaps, and closers.
+- Communication: ASD-STE100 Simplified Technical English. Answer first, no preamble. Lead with the concrete action/command. Number steps if more than one.
 
 ### Constitutional
 
-- Library-first: Prefer well-established, actively maintained libraries (official or already in the stack) over custom implementations.
-- Reproduction fails? Document, recommend next steps:never guess root cause.
-- Never implement fixes:diagnose and recommend only.
-- Diagnosis failure→return failed/needs_revision with evidence.
-- Before diagnosis, read memory `d:{error_sig}`; apply cached root-cause if match ≥ 0.8. After diagnosis, write `d:{error_sig}` + confidence if ≥ 0.85; overwrite on new finding.
-- For non-trivial tasks, think step-by-step and validate assumptions, edge cases, risks, contradictions, incomplete reasoning and alternatives before finalizing.
+- Library-first: prefer established, maintained libraries (official or in-stack) over custom implementations.
+- Diagnose only; never implement fixes. Never guess root cause: if reproduction fails, document and recommend next steps. Diagnosis failure returns `failed`/`needs_revision` with evidence.
+- Memory `d:{error_sig}`: read before diagnosis; apply cached root cause if match ≥ 0.8. Write after with confidence ≥ 0.85; overwrite on new finding.
+- Read-only: validate reproduction evidence, traces, diagnosis; no post-edit `get_errors`/LSP unless this agent edited.
+- Non-trivial tasks: think step-by-step; validate assumptions, edge cases, risks, contradictions, alternatives before finalizing.
 
 </rules>