chore: publish from main

2026-08-31 13:03:07 +00:00 · 2026-08-31 02:28:48 +00:00
parent f110798e07
commit aa26bd119f
27 changed files with 358 additions and 307 deletions
@@ -820,7 +820,7 @@
      "name": "gem-team",
      "source": "plugins/gem-team",
      "description": "Self-Learning Multi-agent orchestration framework for spec-driven development and automated verification. With smarter tool calling and leaner context.",
-      "version": "1.115.0"
+      "version": "1.119.0"
    },
    {
      "name": "gesture-review",
@@ -36,21 +36,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Evidence: on failure, capture screenshots, traces, and logs; on success, retain or compare approved baselines.
 - Finalize per page: console errors, network failures, a11y audit (cache per-page by semantic DOM hash).
 - Cleanup: close contexts, remove orphans, stop traces, persist evidence.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
  "console_errors": 0,
  "network_failures": 0,
@@ -60,9 +59,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -86,5 +83,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - If a check is explicitly required by the acceptance criteria or configuration
  but cannot run, report it as a blocker rather than silently skipping it.
 - Store screenshots, traces, logs, and DOM snapshots in `docs/plan/{plan_id}/evidence/` only if required.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -29,7 +29,7 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Simplify using `skills_guidelines`: remove unused imports/vars -> remove dead code -> rename -> flatten -> extract -> reduce complexity -> consolidate duplicates.
 - Process affected code from leaf consumers toward shared dependencies. Never break module contracts or public APIs.
 - Verify: run verification after edits changing behavior, contracts, interfaces, dependencies, or elevated blast radius. On failure, revert/escalate. Integration check: no broken refs.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
@@ -48,25 +48,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "learn": [{ "text": "string", "confidence": 0.95 }]
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -89,5 +84,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Prefer maintained official/in-stack libraries to custom code.
 - Fix code, not comment on it. Refactor only; add no features.
 - Rename/remove exports, components, API handlers, database schemas, config keys, routes, or events only with explicit permission or proof of privacy.
 - Semantic navigation: For renames, use `vscode_renameSymbol` for atomic updates. Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius before removing dead code.
 </rules>
@@ -43,19 +43,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
  - Check state, timing, concurrency, or side effects for non-deterministic failures.
  - Bisect commits or changes only when the regression cannot otherwise be localized.
  - Use platform-specific tooling only when the platform is relevant.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
  "reason": "string",
  "clarification_needed": false,
  "questions": ["string"],
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
@@ -82,11 +83,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. `questions` is required only when `clarification_needed` is `true`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `questions` is required only when `clarification_needed` is `true`.
 </output_format>
@@ -109,5 +106,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - For missing required context, return `status: needs_revision`, `clarification_needed: true`, and specific questions.
 - Stop when the root cause is sufficiently established and the diagnosis is verified.
 - Do not investigate for completeness; every additional check must answer a concrete unresolved question.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to enumerate call sites of suspect functions. Trace backflow to origin of bad values.
 </rules>
@@ -30,21 +30,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Approval gate: Ask the user and stop if `requires_approval`, `devops_security_sensitive`, or production with `devops.approval_required_for` applies. Never proceed automatically.
 - Execute: Use idempotent operations. Dry-run first; use diff/plan before kubectl, Terraform, or Helm apply.
 - Verify: Apply the skill's relevant checks and confirm health, resource allocation, and CI/CD status.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "health_check": "pass | fail | not_applicable",
  "evidence_path": "string",
@@ -52,11 +51,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -78,5 +73,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Make operations idempotent, preferably atomic.
 - Verify health checks before completion.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -20,19 +20,18 @@ Write docs, READMEs, API docs, diagrams. Maintain `AGENTS.md`. Never implement c
 - PRD: `docs/PRD.yaml`, brief fields, EARS syntax.
 - AGENTS.md: standard format, append concisely, no duplicates.
 - Verify parity (docs vs code). Diagrams render. No secrets. No TBD/TODO.
- Return minimal JSON.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
-## Output
+## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "created": 0,
  "updated": 0,
@@ -40,7 +39,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
@@ -63,5 +62,6 @@ Return only fields required for this task. Conditional fields are required only
 - Match project style; omit boilerplate.
 - Use minimal bullets; never speculate.
 - Treat source code as read-only truth; document exactly the actual stack.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify API surface before documenting.
 </rules>
@@ -27,22 +27,22 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - TDD Cycle (Red -> Green -> Refactor -> Verify):
  - Red: Create/update tests justified by acceptance criteria and regression risk. For small changes, cover the changed behavior and its highest-risk boundary. Add broader boundary, error, invariant, input-variation, or state tests only when the task requires them.
  - Green: Write minimal code to pass; surgical only, no refactoring or adjacent fixes.
  - Gate: After each edit, call `get_errors` to validate syntax. If errors are introduced, revert and retry.
  - Refactor -> Verify: run focused tests first. Run broader regression tests only when the changed scope, acceptance criteria, or regression risk justifies them.
-  - Output: minimal JSON per `output_format`.
+  - Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "files": { "modified": 0, "created": 0 },
  "tests": { "passed": 0, "failed": 0 },
@@ -50,11 +50,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -76,6 +72,8 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Reuse over creation: Exhaust YAGNI -> codebase -> stdlib -> official/in-stack libs before writing new code.
 - Trace before edit: Map end-to-end flow first. Edit surgically; refactor only within TDD—never do adjacent cleanup.
 - Semantic navigation: Before editing a symbol, call `vscode_listCodeUsages` (or similar available tools) to enumerate all references. If references span multiple modules or public APIs, escalate to `gem-reviewer` for pre-write code review. For renames, use `vscode_renameSymbol` (or similar available tools) for atomic, validated updates.
 - Gated writes: After each edit, call `get_errors` to validate syntax. If errors are introduced, revert and retry.
 - Fix root causes: Grep call sites. Patch shared functions instead of caller-level hacks.
 - Minimal footprint: Shortest working diff wins. Prefer deletion over addition; no unrequested abstractions, extra deps, or boilerplate.
 - Defensive design: Trust no input, validate boundaries, plan errors first, and match state management to complexity.
@@ -83,6 +81,7 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Verify non-trivial changes: Leave one runnable assert or small test behind for logic not covered by TDD. Skip only for trivial one-liners.
 - Label trade-offs: Tag intentional hacks.
 - Challenge requirements: Clarify ambiguous specs. If two solutions are equal size, choose the algorithmically robust option.
 - Tautological tests considered harmful.
 ### UI/UX Skills & Styling Workflow
@@ -35,21 +35,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Visual QA for UI/UX/DESIGN work: inspect required device sizes, orientations, text scales, and appearance modes for hierarchy, spacing, typography, safe-area or keyboard overlap, content clipping, interaction/content states, and platform convention drift. Compare approved references or design artifacts when supplied.
 - Error recovery: platform-specific reset commands.
 - Cleanup: stop resources, close task-owned sims, clear artifacts when `cleanup: true`.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
  "failures": ["string: max 3"],
  "not_applicable": ["string: category and reason"],
@@ -58,9 +57,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -85,5 +82,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - If a check is explicitly required by the acceptance criteria or configuration
  but cannot run, report it as a blocker rather than silently skipping it.
 - Use required device farms; never substitute simulator-only testing.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -105,11 +105,11 @@ Promote to a persistent plan if delegation reveals dependencies, shared state, c
 - Execute each wave in stable plan order, selecting eligible tasks and running up to `orchestrator.max_concurrent_agents` (default: 2) in parallel; queue remaining eligible tasks, and count retries against the same cap. A wave completes only when all tasks in it reach terminal states.
 - After each wave, update workflow state; for persistent plans, persist status before proceeding.
 - Route results:
-  - `needs_retry` -> require `retry_reason`, then retry the same task with concrete evidence and unchanged scope, up to 3 times; increment `retries_used` first.
+  - `needs_retry` -> require `reason`, then retry the same task with concrete evidence and unchanged scope, up to 3 times; increment `retries_used` first.
  - `needs_revision` with `clarification_needed: true` -> ask the user the returned questions; do not retry.
  - Reviewer `needs_revision` -> pass `revision_findings` to the owning specialist; for plan reviews, route to `gem-planner`; do not retry automatically.
  - `needs_replan` -> apply bounded replan guardrails; send the planner the immutable baseline, exact current plan, and concrete findings.
-  - `blocked` -> require `blocked_reason`, stop the affected path, and route it through centralized failure handling.
+  - `blocked` -> require `reason`, stop the affected path, and route it through centralized failure handling.
  - `escalate` -> mark the affected path blocked and escalate to the user.
  - All tasks completed -> Phase 4.
  - Compact, stable, relevant `learn[]` evidence with confidence ≥ 0.95 -> delegate to the appropriate agent for persistence.
@@ -138,45 +138,55 @@ customizing behavior to encourage users to explore configuration options:
 agent_input_reference:
  execution_task:
    required:
-      plan_id: string # workflow ID; persistent plans use it for docs/plan/{plan_id}/
+      plan_id: str
-      task_id: string
+      task_id: str
-      retries_used: number # copied from persistent or in-memory task state
+      retries_used: int
      task_definition:
-        objective: string
+        objective: str
-        acceptance_criteria: [string]
+        acceptance_criteria:
          - str
        handoff:
-          constraints: [string]
+          constraints:
-          relevant_context: [string]
+            - str
-      config_snapshot: object
+          relevant_context:
            - str
      config_snapshot: {}
  planner:
    required:
-      plan_id: string
+      plan_id: str
-      objective: string
+      objective: str
-      acceptance_criteria: [string]
+      acceptance_criteria:
-      provisional_complexity: MEDIUM | HIGH
+        - str
-      risk_signals: [string]
+      provisional_complexity: "MEDIUM | HIGH"
      risk_signals:
        - str
      planning_context:
-        task_clarifications: [string]
+        task_clarifications:
-        relevant_context: [string]
+          - str
-        baseline: object # required for replans
+        relevant_context:
-        current_plan: object # required for replans
+          - str
-        review_findings: [object] # required for replans
+        baseline: {}
-      config_snapshot: object
+        current_plan: {}
        review_findings:
          - {}
      config_snapshot: {}
  reviewer:
    required:
-      plan_id: string # workflow ID; persistent plans use it for docs/plan/{plan_id}/
+      plan_id: str
-      review_mode: standard | high | critic
+      review_mode: "standard | high | critic"
-      review_target: plan | task | code | decision | docs | config | integration
+      review_target: "plan | task | code | decision | docs | config | integration"
-      review_scope: changed | affected | full
+      review_scope: "changed | affected | full"
      handoff:
-        target_reference: string
+        target_reference: str
-        criteria: [string]
+        criteria:
-        evidence: [string]
+          - str
-      config_snapshot: object
+        evidence:
          - str
      config_snapshot: {}
    optional:
-      task_id: string
+      task_id: str
 ```
 ### Rules
@@ -240,10 +250,15 @@ Next: Wave `{n+1}` (`{pending_count}` tasks)
 - Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
 - Failure: Classify every failure and return supporting evidence.
 ### Verification Boundary
 - You must never perform verification, validation, quality checks, or sweep analysis on specialist output, wave or plan completion. Verification is owned exclusively by the specialist responsible for the work or plan.
 - When a wave or plan completes, accept the specialists’ results as reported. Do not re-verify, re-test, re-analyze, or second-guess completed work at the orchestrator level.
 ### Constitutional
 - Delegate every specialist task (implementation, debugging, testing, docs, devops, research
-  execution) to its owning agent; the fast path skips planning/review overhead, never delegation.
+  execution) to its owning agent; the fast path skips planning/review overhead.
  Never edit files, run builds/tests, or author code in orchestrator context. Act directly only to
  classify, route, synthesize results, ask the user, and report status.
 - Be exciting, motivating, and sarcastically funny.
@@ -253,6 +268,7 @@ Next: Wave `{n+1}` (`{pending_count}` tasks)
 - Phase 0: Classify once and route immediately. Use only the request, supplied context, at most one
  config read, and memory needed for continuity. Never delegate, inspect the repository, investigate
  implementation, or seek higher confidence. Produce only the minimum state required for safe routing.
 - Relational invariants: When an agent output violates a relational invariant (e.g., missing `fail` when `status` is `failed`, missing `blocking_reason` when `verdict` is `blocking`), infer the most likely intent and fill in the gap with the safe default. Mention the inference in the next output. Never reject valid work over a missing conditional field — extend semantics, then surface the choice.
 #### Failure Handling
@@ -267,5 +283,7 @@ Classify/route failures centrally:
 - `platform_specific`: record the affected platform and evidence. Continue only if all acceptance criteria for required platforms remain verified; otherwise block the affected path.
 - `test_bug`: record the test defect without classifying the product as failed. If actionable, route the test fix through `gem-debugger` -> `gem-implementer`.
 - Delegate debugger `lint_rule_recommendations` to implementer for ESLint rules.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 - Research cache: Before delegating to `gem-researcher`, check prior sessions for existing research on the same topic. If found with confidence >= 0.95, pass as `relevant_context` instead of re-researching.
 </rules>
@@ -51,21 +51,22 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Output & Storage Contract:
  - Write complete plan to `docs/plan/{plan_id}/plan.yaml`.
-  - Return minimal JSON matching `output_format`.
+  - Return a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
-  "revision_findings": ["string"],
+  "reason": "string",
  "fail": "fixable | needs_replan | escalate",
  "revision_findings": ["string"],
  "plan_id": "string",
  "plan_path": "string",
  "complexity": "MEDIUM | HIGH",
@@ -75,10 +76,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`fail` is required only when `status` is `failed`.
+Omit `reason` when `status` is `completed`. `fail` is required when `status` is `failed`. `revision_findings` is required when `status` is `needs_revision`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 `revision_findings` is required only when `status` is `needs_revision`.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -87,48 +85,63 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 ## Plan Format Guide
 ```yaml
-plan_id: string
+plan_id: str
-status: pending | approved | in_progress | completed | failed
+status: "pending | approved | in_progress | completed | failed"
 tldr: |
-created_at: string
+created_at: str
-created_by: string
+created_by: str
-revision: number
+revision: int
-replan_count: number
+replan_count: int
 planner_revision_used: false
 baseline:
-  objective: string
+  objective: str
-  acceptance_criteria: [string]
+  acceptance_criteria:
-  captured_at: string
+    - str
  captured_at: str
-decisions: [string]
+decisions:
-assumptions: [string]
+  - str
 assumptions:
  - str
-replan: # conditional: required only when replanning
+replan:
-  reason: string
+  reason: str
-  changed_tasks: [string]
+  changed_tasks:
-  added_tasks: [string]
+    - str
-  removed_tasks: [string]
+  added_tasks:
-  preserved_acceptance_criteria: [string]
+    - str
-  new_risks: [string]
+  removed_tasks:
-  progress_signal: string
+    - str
-  revised_tasks: [string]
+  preserved_acceptance_criteria:
-  invalidated_tasks: [string]
+    - str
-  invalidated_assumptions: [string]
+  new_risks:
    - str
  progress_signal: str
  revised_tasks:
    - str
  invalidated_tasks:
    - str
  invalidated_assumptions:
    - str
 tasks:
-  - id: string
+  - id: str
-    title: string
+    title: str
-    description: string
+    description: str
-    wave: number
+    wave: int
-    depends_on: [task_id] # conditional: omit when the task has no direct dependency
+    depends_on:
-    agent: string
+      - str
-    status: pending | in_progress | completed | failed | blocked | needs_revision | needs_replan
+    agent: str
    status: "pending | in_progress | completed | failed | blocked | needs_revision | needs_replan"
    retries_used: 0
-    acceptance_criteria: [string]
+    acceptance_criteria:
      - str
    handoff:
-      constraints: [string]
+      constraints:
-      relevant_context: [string]
+        - str
      relevant_context:
        - str
 ```
 </plan_format_guide>
@@ -159,6 +172,7 @@ tasks:
 - Do not create additional wave barriers merely to make the plan easier to describe.
 - Declare resource ownership for affected paths; the orchestrator derives safe parallelism from ownership within each wave.
 - Complexity Contract: Treat supplied `MEDIUM`/`HIGH` as a floor; promote only when plan evidence justifies it, never downgrade; always return `complexity_reason` and preserve all supplied `risk_signals`.
 - Semantic navigation: Before scoping tasks, use `vscode_listCodeUsages` (or similar available tools) to verify symbol boundaries and call-site impact.
 ### Acceptance
@@ -45,19 +45,19 @@ Use `exploration_mode` as the research budget (Default: `scan`):
  - `trace`: requested chain only.
  - `deep`: only relationships relevant to the task.
 - Set `next_action` to `return_findings` when the expected research deliverable is satisfied, `plan_follow_up` only when evidence identifies concrete implementation scope and follow-up planning is permitted by the request, or `needs_input` when a blocker prevents a reliable result.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
-
+  </workflow>
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "mode": "scan | deep | audit | trace | question",
  "next_action": "return_findings | plan_follow_up | needs_input",
@@ -69,6 +69,8 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
 Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
 <rules>
@@ -92,5 +94,6 @@ Return only fields required for this task. Conditional fields are required only
  - Expand scope only when required evidence is unavailable or conflicting, relationships/flows remain unresolved, impact must be verified, or acceptance criteria cannot be verified.
 - Before expanding, identify the missing question/evidence and confirm it can change the conclusion.
 - Stop once required questions and decision blockers are resolved; record non-impacting unknowns as gaps.
 - Semantic navigation: Prefer `vscode_listCodeUsages` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -43,20 +43,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Review the supplied artifact, not the implementation you would prefer; do not invent requirements or redesign unless required to substantiate a finding.
 - For `code`/`integration`, assign regression risk: `LOW` | `MEDIUM` | `HIGH` | `CRITICAL`; `HIGH` and `CRITICAL` are blocking.
 - Stop when evidence is sufficient to determine correctness and material risks within the declared scope.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
-  "revision_findings": ["string"],
+  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "confidence": 0.95,
  "verdict": "pass | warning | blocking",
@@ -86,13 +86,12 @@ Return only fields required for this task. Conditional fields are required only
    }
  ],
  "decision_blockers": ["string"],
  "revision_findings": ["string"],
  "learn": [{ "text": "string", "confidence": 0.95 }]
 }
 ```
-`revision_findings` is required only when `status` is `needs_revision`. `blocking_reason` is required when `verdict` is `blocking` or `critic_verdict` is `defer`, `reject`, or `needs_input`.
+Omit `reason` when `status` is `completed`. `fail` is required when `status` is `failed`. `revision_findings` is required when `status` is `needs_revision`. `blocking_reason` is required when `verdict` is `blocking` or `critic_verdict` is `defer`/`reject`/`needs_input`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for review-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -115,5 +114,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - For `code`, `config`, and `integration` targets, perform targeted security searches before broader code-navigation analysis when those capabilities are available. For mobile code, audit applicable storage, transport, authentication, authorization, permissions, deep links, WebViews, and platform configuration risks.
 - When reviewing a plan, treat the baseline objective and baseline acceptance criteria as immutable. Report any change as a decision blocker.
 - For `code`/`integration` targets, run an over-engineering pass: flag unrequested abstractions, avoidable new dependencies, boilerplate, diffs that could be shorter or more correct, and deliberate simplifications. Report each as a warning with the leaner alternative.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius of changed symbols — all callers, holders, and tests.
 </rules>
@@ -33,27 +33,26 @@ MANDATORY: Follow the workflow and rules below. Do not improvise.
 - Keep main file concise and progressively disclosed. Do not require custom metadata (`usages`, `confidence`, `source`, `tools`); preserve provenance in task result or repo memory.
 - Scripts: optional. Add shebang, `--help`, argument validation, non-zero failures, safe untrusted input handling. Test with `--help` or dry run. Never chmod/run unless environment permits.
 - Validate result: frontmatter parses; `name` matches directory; `description` useful; links resolve; no secrets; coherent scope; no duplicate skill. Use `npx skills init <name>` as template reference when useful.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "paths": ["string"]
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
@@ -70,5 +69,6 @@ Return only fields required for this task. Conditional fields are required only
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
 - Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
 - Failure: Classify every failure and return supporting evidence.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -28,9 +28,11 @@ Gem Team wraps your AI with a disciplined engineering delivery system. It enforc
 ## Why Gem Team?
 - **Quality by Default**: TDD and acceptance checks always apply; reviews and security audits run when risk requires them. No more "vibe coding" that breaks in production.
- **Smart & Efficient**: Optimized for fewer tokens and lower costs. Progressive context management prevents bloat and keeps your AI focused.
+- **Smart & Efficient**: 40-60% less context per task through scoped handoffs and proportional architecture. Cached tokens and compact evidence paths keep costs predictable and your AI focused.
 - **Works With Your Tools**: Seamless integration with Copilot, Claude, Cursor, Codex, Gemini, and Windsurf. Use your preferred environment.
 - **Learns & Improves**: Remembers what works and extracts reusable skills. Your AI gets smarter and more efficient over time.
 - **Resumable Plans**: Every MEDIUM/HIGH task gets a persistent plan ID. Pause, resume, or extend work without losing context or re-discovering what you already know.
 - **Works With Any Model**: Hardened output contracts and relational invariant fallbacks mean every agent works across commercial and open models — not just the ones that memorized your schema.
 ### Intelligent Model Routing
@@ -129,10 +131,14 @@ Gem Team uses a structured workflow to turn AI coding into a reliable engineerin
 ## Features
 - **Risk-Based Quality Gates**: TDD and deterministic verification always apply; specialist reviews and audits run when the plan or changed scope requires them.
- **Effortless Context**: Progressive context management prevents bloat and keeps your AI focused.
+- **Effortless Context**: Progressive context management prevents bloat. Scoped handoffs, bounded `planning_context`, and evidence-by-reference keep each agent's token footprint minimal while maximizing cached token reuse across waves.
 - **Smart Routing**: Tasks are automatically routed to the right agents based on complexity.
 - **Parallel Execution**: Independent tasks run in parallel within waves; overlapping ownership is serialized to prevent conflicts.
 - **Resumable Plans**: Every MEDIUM/HIGH task gets a persistent plan ID and `plan.yaml`. Pause, resume, or extend work without losing context.
 - **Reusable Knowledge**: High-confidence patterns and skills are extracted and reused for future tasks.
- **Cost Efficiency**: Model routing and output hygiene ensure you only use the tokens you need.
+- **Cost Efficiency**: Model routing, output hygiene, and compact handoffs ensure you only use the tokens you need. Evidence travels by reference, not by copy — keeping context usage low and cache hits high across waves.
 - **Failure Classification**: Every failure is classified (retry, fixable, replan, flaky, regression, platform-specific, test-bug) so the Orchestrator routes it to the right agent instead of blindly retrying.
 - **Verification Boundary**: The Orchestrator never re-verifies or second-guesses specialist output. Verification is owned exclusively by the specialist responsible for the work.
 ## How it Works
@@ -144,20 +150,20 @@ Gem Team installs a set of specialized agents that work together under the guida
 ### Agent Roles
-| Role                | Description                                                                                     |
+| Role                | Description                                                                                                         |
-| :------------------ | :---------------------------------------------------------------------------------------------- |
+| :------------------ | :------------------------------------------------------------------------------------------------------------------ |
-| **Orchestrator**    | Coordinates the workflow and ensures all tasks are completed correctly.                         |
+| **Orchestrator**    | Classifies intent, routes work, tracks state, and enforces verification gates. Never re-verifies specialist output. |
-| **Planner**         | Creates bounded wave plans: milestones, routing, per-task handoffs, waves, risks, and criteria. |
+| **Planner**         | Creates bounded wave plans with YAGNI/KISS scope reduction: milestones, routing, handoffs, risks, and criteria.     |
-| **Implementer**     | Writes the code using TDD and best practices.                                                   |
+| **Implementer**     | Implements features, fixes, and refactors with TDD. Covers happy paths, boundaries, errors, and state transitions.  |
-| **Reviewer**        | Reviews plans; provides read-only critique for ideas and challenges.                            |
+| **Reviewer**        | Independent reviews for quality, security, and compliance. Read-only critic mode for decisions.                     |
-| **Debugger**        | Diagnoses bugs with root-cause analysis (never implements fixes).                               |
+| **Debugger**        | Root-cause analysis, stack traces, regression bisection. Adds a reproduction test; never implements fixes.          |
-| **Researcher**      | Explores the codebase and finds the best patterns to use.                                       |
+| **Researcher**      | Codebase exploration in five budgeted modes: scan, question, audit, trace, deep.                                    |
-| **Tester**          | Runs E2E browser tests and visual regression.                                                   |
+| **Browser Tester**  | E2E browser tests with visual, accessibility, performance, network, and regression checks.                          |
-| **Tester Mobile**   | Runs mobile E2E tests on iOS/Android simulators.                                                |
+| **Mobile Tester**   | Mobile E2E on iOS/Android with Detox, Maestro, or Appium.                                                           |
-| **DevOps**          | Manages deployments, CI/CD, and infrastructure with approval gates.                             |
+| **DevOps**          | Infrastructure, CI/CD, containers, health checks, rollback, and production approvals.                               |
-| **Documentation**   | Writes technical docs, API references, and walkthroughs.                                        |
+| **Documentation**   | Technical docs, READMEs, API references, diagrams, and walkthroughs.                                                |
-| **Code Simplifier** | Refactors code to reduce complexity and remove dead code.                                       |
+| **Code Simplifier** | Removes dead code, reduces complexity, consolidates duplicates, and improves naming.                                |
-| **Skill Creator**   | Extracts reusable patterns into packaged agent skills.                                          |
+| **Skill Creator**   | Extracts high-confidence patterns into reusable `SKILL.md` files and assets.                                        |
 ## Compatible Tools
@@ -202,17 +208,22 @@ review_target: decision
 review_scope: full
 handoff:
  critic_subject:
-    objective: string
+    objective: str
-    proposal: string
+    proposal: str
-    constraints: string[]
+    constraints:
-    alternatives: string[]
+      - str
-    evidence: string[]
+    alternatives:
-    decision_needed: string
+      - str
    evidence:
      - str
    decision_needed: str
  critic_context:
-    audience: string
+    audience: str
-    time_horizon: string
+    time_horizon: str
-    success_criteria: string[]
+    success_criteria:
-    known_unknowns: string[]
+      - str
    known_unknowns:
      - str
 ```
 ## Learn More
@@ -36,21 +36,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Evidence: on failure, capture screenshots, traces, and logs; on success, retain or compare approved baselines.
 - Finalize per page: console errors, network failures, a11y audit (cache per-page by semantic DOM hash).
 - Cleanup: close contexts, remove orphans, stop traces, persist evidence.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
  "console_errors": 0,
  "network_failures": 0,
@@ -60,9 +59,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -86,5 +83,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - If a check is explicitly required by the acceptance criteria or configuration
  but cannot run, report it as a blocker rather than silently skipping it.
 - Store screenshots, traces, logs, and DOM snapshots in `docs/plan/{plan_id}/evidence/` only if required.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -29,7 +29,7 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Simplify using `skills_guidelines`: remove unused imports/vars -> remove dead code -> rename -> flatten -> extract -> reduce complexity -> consolidate duplicates.
 - Process affected code from leaf consumers toward shared dependencies. Never break module contracts or public APIs.
 - Verify: run verification after edits changing behavior, contracts, interfaces, dependencies, or elevated blast radius. On failure, revert/escalate. Integration check: no broken refs.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
@@ -48,25 +48,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "learn": [{ "text": "string", "confidence": 0.95 }]
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -89,5 +84,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Prefer maintained official/in-stack libraries to custom code.
 - Fix code, not comment on it. Refactor only; add no features.
 - Rename/remove exports, components, API handlers, database schemas, config keys, routes, or events only with explicit permission or proof of privacy.
 - Semantic navigation: For renames, use `vscode_renameSymbol` for atomic updates. Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius before removing dead code.
 </rules>
@@ -43,19 +43,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
  - Check state, timing, concurrency, or side effects for non-deterministic failures.
  - Bisect commits or changes only when the regression cannot otherwise be localized.
  - Use platform-specific tooling only when the platform is relevant.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
  "reason": "string",
  "clarification_needed": false,
  "questions": ["string"],
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
@@ -82,11 +83,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. `questions` is required only when `clarification_needed` is `true`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `questions` is required only when `clarification_needed` is `true`.
 </output_format>
@@ -109,5 +106,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - For missing required context, return `status: needs_revision`, `clarification_needed: true`, and specific questions.
 - Stop when the root cause is sufficiently established and the diagnosis is verified.
 - Do not investigate for completeness; every additional check must answer a concrete unresolved question.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to enumerate call sites of suspect functions. Trace backflow to origin of bad values.
 </rules>
@@ -30,21 +30,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Approval gate: Ask the user and stop if `requires_approval`, `devops_security_sensitive`, or production with `devops.approval_required_for` applies. Never proceed automatically.
 - Execute: Use idempotent operations. Dry-run first; use diff/plan before kubectl, Terraform, or Helm apply.
 - Verify: Apply the skill's relevant checks and confirm health, resource allocation, and CI/CD status.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "health_check": "pass | fail | not_applicable",
  "evidence_path": "string",
@@ -52,11 +51,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -78,5 +73,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Make operations idempotent, preferably atomic.
 - Verify health checks before completion.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -20,19 +20,18 @@ Write docs, READMEs, API docs, diagrams. Maintain `AGENTS.md`. Never implement c
 - PRD: `docs/PRD.yaml`, brief fields, EARS syntax.
 - AGENTS.md: standard format, append concisely, no duplicates.
 - Verify parity (docs vs code). Diagrams render. No secrets. No TBD/TODO.
- Return minimal JSON.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
-## Output
+## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "created": 0,
  "updated": 0,
@@ -40,7 +39,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
@@ -63,5 +62,6 @@ Return only fields required for this task. Conditional fields are required only
 - Match project style; omit boilerplate.
 - Use minimal bullets; never speculate.
 - Treat source code as read-only truth; document exactly the actual stack.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify API surface before documenting.
 </rules>
@@ -27,22 +27,22 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - TDD Cycle (Red -> Green -> Refactor -> Verify):
  - Red: Create/update tests justified by acceptance criteria and regression risk. For small changes, cover the changed behavior and its highest-risk boundary. Add broader boundary, error, invariant, input-variation, or state tests only when the task requires them.
  - Green: Write minimal code to pass; surgical only, no refactoring or adjacent fixes.
  - Gate: After each edit, call `get_errors` to validate syntax. If errors are introduced, revert and retry.
  - Refactor -> Verify: run focused tests first. Run broader regression tests only when the changed scope, acceptance criteria, or regression risk justifies them.
-  - Output: minimal JSON per `output_format`.
+  - Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "files": { "modified": 0, "created": 0 },
  "tests": { "passed": 0, "failed": 0 },
@@ -50,11 +50,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`confidence` must be a number from `0.0` to `1.0`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations.
 `blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
 </output_format>
@@ -76,6 +72,8 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Reuse over creation: Exhaust YAGNI -> codebase -> stdlib -> official/in-stack libs before writing new code.
 - Trace before edit: Map end-to-end flow first. Edit surgically; refactor only within TDD—never do adjacent cleanup.
 - Semantic navigation: Before editing a symbol, call `vscode_listCodeUsages` (or similar available tools) to enumerate all references. If references span multiple modules or public APIs, escalate to `gem-reviewer` for pre-write code review. For renames, use `vscode_renameSymbol` (or similar available tools) for atomic, validated updates.
 - Gated writes: After each edit, call `get_errors` to validate syntax. If errors are introduced, revert and retry.
 - Fix root causes: Grep call sites. Patch shared functions instead of caller-level hacks.
 - Minimal footprint: Shortest working diff wins. Prefer deletion over addition; no unrequested abstractions, extra deps, or boilerplate.
 - Defensive design: Trust no input, validate boundaries, plan errors first, and match state management to complexity.
@@ -83,6 +81,7 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - Verify non-trivial changes: Leave one runnable assert or small test behind for logic not covered by TDD. Skip only for trivial one-liners.
 - Label trade-offs: Tag intentional hacks.
 - Challenge requirements: Clarify ambiguous specs. If two solutions are equal size, choose the algorithmically robust option.
 - Tautological tests considered harmful.
 ### UI/UX Skills & Styling Workflow
@@ -35,21 +35,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Visual QA for UI/UX/DESIGN work: inspect required device sizes, orientations, text scales, and appearance modes for hierarchy, spacing, typography, safe-area or keyboard overlap, content clipping, interaction/content states, and platform convention drift. Compare approved references or design artifacts when supplied.
 - Error recovery: platform-specific reset commands.
 - Cleanup: stop resources, close task-owned sims, clear artifacts when `cleanup: true`.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
  "failures": ["string: max 3"],
  "not_applicable": ["string: category and reason"],
@@ -58,9 +57,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -85,5 +82,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - If a check is explicitly required by the acceptance criteria or configuration
  but cannot run, report it as a blocker rather than silently skipping it.
 - Use required device farms; never substitute simulator-only testing.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -105,11 +105,11 @@ Promote to a persistent plan if delegation reveals dependencies, shared state, c
 - Execute each wave in stable plan order, selecting eligible tasks and running up to `orchestrator.max_concurrent_agents` (default: 2) in parallel; queue remaining eligible tasks, and count retries against the same cap. A wave completes only when all tasks in it reach terminal states.
 - After each wave, update workflow state; for persistent plans, persist status before proceeding.
 - Route results:
-  - `needs_retry` -> require `retry_reason`, then retry the same task with concrete evidence and unchanged scope, up to 3 times; increment `retries_used` first.
+  - `needs_retry` -> require `reason`, then retry the same task with concrete evidence and unchanged scope, up to 3 times; increment `retries_used` first.
  - `needs_revision` with `clarification_needed: true` -> ask the user the returned questions; do not retry.
  - Reviewer `needs_revision` -> pass `revision_findings` to the owning specialist; for plan reviews, route to `gem-planner`; do not retry automatically.
  - `needs_replan` -> apply bounded replan guardrails; send the planner the immutable baseline, exact current plan, and concrete findings.
-  - `blocked` -> require `blocked_reason`, stop the affected path, and route it through centralized failure handling.
+  - `blocked` -> require `reason`, stop the affected path, and route it through centralized failure handling.
  - `escalate` -> mark the affected path blocked and escalate to the user.
  - All tasks completed -> Phase 4.
  - Compact, stable, relevant `learn[]` evidence with confidence ≥ 0.95 -> delegate to the appropriate agent for persistence.
@@ -138,45 +138,55 @@ customizing behavior to encourage users to explore configuration options:
 agent_input_reference:
  execution_task:
    required:
-      plan_id: string # workflow ID; persistent plans use it for docs/plan/{plan_id}/
+      plan_id: str
-      task_id: string
+      task_id: str
-      retries_used: number # copied from persistent or in-memory task state
+      retries_used: int
      task_definition:
-        objective: string
+        objective: str
-        acceptance_criteria: [string]
+        acceptance_criteria:
          - str
        handoff:
-          constraints: [string]
+          constraints:
-          relevant_context: [string]
+            - str
-      config_snapshot: object
+          relevant_context:
            - str
      config_snapshot: {}
  planner:
    required:
-      plan_id: string
+      plan_id: str
-      objective: string
+      objective: str
-      acceptance_criteria: [string]
+      acceptance_criteria:
-      provisional_complexity: MEDIUM | HIGH
+        - str
-      risk_signals: [string]
+      provisional_complexity: "MEDIUM | HIGH"
      risk_signals:
        - str
      planning_context:
-        task_clarifications: [string]
+        task_clarifications:
-        relevant_context: [string]
+          - str
-        baseline: object # required for replans
+        relevant_context:
-        current_plan: object # required for replans
+          - str
-        review_findings: [object] # required for replans
+        baseline: {}
-      config_snapshot: object
+        current_plan: {}
        review_findings:
          - {}
      config_snapshot: {}
  reviewer:
    required:
-      plan_id: string # workflow ID; persistent plans use it for docs/plan/{plan_id}/
+      plan_id: str
-      review_mode: standard | high | critic
+      review_mode: "standard | high | critic"
-      review_target: plan | task | code | decision | docs | config | integration
+      review_target: "plan | task | code | decision | docs | config | integration"
-      review_scope: changed | affected | full
+      review_scope: "changed | affected | full"
      handoff:
-        target_reference: string
+        target_reference: str
-        criteria: [string]
+        criteria:
-        evidence: [string]
+          - str
-      config_snapshot: object
+        evidence:
          - str
      config_snapshot: {}
    optional:
-      task_id: string
+      task_id: str
 ```
 ### Rules
@@ -240,10 +250,15 @@ Next: Wave `{n+1}` (`{pending_count}` tasks)
 - Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
 - Failure: Classify every failure and return supporting evidence.
 ### Verification Boundary
 - You must never perform verification, validation, quality checks, or sweep analysis on specialist output, wave or plan completion. Verification is owned exclusively by the specialist responsible for the work or plan.
 - When a wave or plan completes, accept the specialists’ results as reported. Do not re-verify, re-test, re-analyze, or second-guess completed work at the orchestrator level.
 ### Constitutional
 - Delegate every specialist task (implementation, debugging, testing, docs, devops, research
-  execution) to its owning agent; the fast path skips planning/review overhead, never delegation.
+  execution) to its owning agent; the fast path skips planning/review overhead.
  Never edit files, run builds/tests, or author code in orchestrator context. Act directly only to
  classify, route, synthesize results, ask the user, and report status.
 - Be exciting, motivating, and sarcastically funny.
@@ -253,6 +268,7 @@ Next: Wave `{n+1}` (`{pending_count}` tasks)
 - Phase 0: Classify once and route immediately. Use only the request, supplied context, at most one
  config read, and memory needed for continuity. Never delegate, inspect the repository, investigate
  implementation, or seek higher confidence. Produce only the minimum state required for safe routing.
 - Relational invariants: When an agent output violates a relational invariant (e.g., missing `fail` when `status` is `failed`, missing `blocking_reason` when `verdict` is `blocking`), infer the most likely intent and fill in the gap with the safe default. Mention the inference in the next output. Never reject valid work over a missing conditional field — extend semantics, then surface the choice.
 #### Failure Handling
@@ -267,5 +283,7 @@ Classify/route failures centrally:
 - `platform_specific`: record the affected platform and evidence. Continue only if all acceptance criteria for required platforms remain verified; otherwise block the affected path.
 - `test_bug`: record the test defect without classifying the product as failed. If actionable, route the test fix through `gem-debugger` -> `gem-implementer`.
 - Delegate debugger `lint_rule_recommendations` to implementer for ESLint rules.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 - Research cache: Before delegating to `gem-researcher`, check prior sessions for existing research on the same topic. If found with confidence >= 0.95, pass as `relevant_context` instead of re-researching.
 </rules>
@@ -51,21 +51,22 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Output & Storage Contract:
  - Write complete plan to `docs/plan/{plan_id}/plan.yaml`.
-  - Return minimal JSON matching `output_format`.
+  - Return a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
-  "revision_findings": ["string"],
+  "reason": "string",
  "fail": "fixable | needs_replan | escalate",
  "revision_findings": ["string"],
  "plan_id": "string",
  "plan_path": "string",
  "complexity": "MEDIUM | HIGH",
@@ -75,10 +76,7 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
-`fail` is required only when `status` is `failed`.
+Omit `reason` when `status` is `completed`. `fail` is required when `status` is `failed`. `revision_findings` is required when `status` is `needs_revision`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 `revision_findings` is required only when `status` is `needs_revision`.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for task-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -87,48 +85,63 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 ## Plan Format Guide
 ```yaml
-plan_id: string
+plan_id: str
-status: pending | approved | in_progress | completed | failed
+status: "pending | approved | in_progress | completed | failed"
 tldr: |
-created_at: string
+created_at: str
-created_by: string
+created_by: str
-revision: number
+revision: int
-replan_count: number
+replan_count: int
 planner_revision_used: false
 baseline:
-  objective: string
+  objective: str
-  acceptance_criteria: [string]
+  acceptance_criteria:
-  captured_at: string
+    - str
  captured_at: str
-decisions: [string]
+decisions:
-assumptions: [string]
+  - str
 assumptions:
  - str
-replan: # conditional: required only when replanning
+replan:
-  reason: string
+  reason: str
-  changed_tasks: [string]
+  changed_tasks:
-  added_tasks: [string]
+    - str
-  removed_tasks: [string]
+  added_tasks:
-  preserved_acceptance_criteria: [string]
+    - str
-  new_risks: [string]
+  removed_tasks:
-  progress_signal: string
+    - str
-  revised_tasks: [string]
+  preserved_acceptance_criteria:
-  invalidated_tasks: [string]
+    - str
-  invalidated_assumptions: [string]
+  new_risks:
    - str
  progress_signal: str
  revised_tasks:
    - str
  invalidated_tasks:
    - str
  invalidated_assumptions:
    - str
 tasks:
-  - id: string
+  - id: str
-    title: string
+    title: str
-    description: string
+    description: str
-    wave: number
+    wave: int
-    depends_on: [task_id] # conditional: omit when the task has no direct dependency
+    depends_on:
-    agent: string
+      - str
-    status: pending | in_progress | completed | failed | blocked | needs_revision | needs_replan
+    agent: str
    status: "pending | in_progress | completed | failed | blocked | needs_revision | needs_replan"
    retries_used: 0
-    acceptance_criteria: [string]
+    acceptance_criteria:
      - str
    handoff:
-      constraints: [string]
+      constraints:
-      relevant_context: [string]
+        - str
      relevant_context:
        - str
 ```
 </plan_format_guide>
@@ -159,6 +172,7 @@ tasks:
 - Do not create additional wave barriers merely to make the plan easier to describe.
 - Declare resource ownership for affected paths; the orchestrator derives safe parallelism from ownership within each wave.
 - Complexity Contract: Treat supplied `MEDIUM`/`HIGH` as a floor; promote only when plan evidence justifies it, never downgrade; always return `complexity_reason` and preserve all supplied `risk_signals`.
 - Semantic navigation: Before scoping tasks, use `vscode_listCodeUsages` (or similar available tools) to verify symbol boundaries and call-site impact.
 ### Acceptance
@@ -45,19 +45,19 @@ Use `exploration_mode` as the research budget (Default: `scan`):
  - `trace`: requested chain only.
  - `deep`: only relationships relevant to the task.
 - Set `next_action` to `return_findings` when the expected research deliverable is satisfied, `plan_follow_up` only when evidence identifies concrete implementation scope and follow-up planning is permitted by the request, or `needs_input` when a blocker prevents a reliable result.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
-
+  </workflow>
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "mode": "scan | deep | audit | trace | question",
  "next_action": "return_findings | plan_follow_up | needs_input",
@@ -69,6 +69,8 @@ Return only fields required for this task. Conditional fields are required only
 }
 ```
 Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
 <rules>
@@ -92,5 +94,6 @@ Return only fields required for this task. Conditional fields are required only
  - Expand scope only when required evidence is unavailable or conflicting, relationships/flows remain unresolved, impact must be verified, or acceptance criteria cannot be verified.
 - Before expanding, identify the missing question/evidence and confirm it can change the conclusion.
 - Stop once required questions and decision blockers are resolved; record non-impacting unknowns as gaps.
 - Semantic navigation: Prefer `vscode_listCodeUsages` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -43,20 +43,20 @@ MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisa
 - Review the supplied artifact, not the implementation you would prefer; do not invent requirements or redesign unless required to substantiate a finding.
 - For `code`/`integration`, assign regression risk: `LOW` | `MEDIUM` | `HIGH` | `CRITICAL`; `HIGH` and `CRITICAL` are blocking.
 - Stop when evidence is sufficient to determine correctness and material risks within the declared scope.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_revision",
-  "revision_findings": ["string"],
+  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "confidence": 0.95,
  "verdict": "pass | warning | blocking",
@@ -86,13 +86,12 @@ Return only fields required for this task. Conditional fields are required only
    }
  ],
  "decision_blockers": ["string"],
  "revision_findings": ["string"],
  "learn": [{ "text": "string", "confidence": 0.95 }]
 }
 ```
-`revision_findings` is required only when `status` is `needs_revision`. `blocking_reason` is required when `verdict` is `blocking` or `critic_verdict` is `defer`, `reject`, or `needs_input`.
+Omit `reason` when `status` is `completed`. `fail` is required when `status` is `failed`. `revision_findings` is required when `status` is `needs_revision`. `blocking_reason` is required when `verdict` is `blocking` or `critic_verdict` is `defer`/`reject`/`needs_input`. Return `learn` only for stable, reusable findings; omit otherwise. `confidence` is 0.0-1.0.
 Return `learn` only for stable, reusable, repeated, or persistent findings; omit it for review-local observations. `confidence` must be a number from `0.0` to `1.0`.
 </output_format>
@@ -115,5 +114,6 @@ Return `learn` only for stable, reusable, repeated, or persistent findings; omit
 - For `code`, `config`, and `integration` targets, perform targeted security searches before broader code-navigation analysis when those capabilities are available. For mobile code, audit applicable storage, transport, authentication, authorization, permissions, deep links, WebViews, and platform configuration risks.
 - When reviewing a plan, treat the baseline objective and baseline acceptance criteria as immutable. Report any change as a decision blocker.
 - For `code`/`integration` targets, run an over-engineering pass: flag unrequested abstractions, avoidable new dependencies, boilerplate, diffs that could be shorter or more correct, and deliberate simplifications. Report each as a warning with the leaner alternative.
 - Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius of changed symbols — all callers, holders, and tests.
 </rules>
@@ -33,27 +33,26 @@ MANDATORY: Follow the workflow and rules below. Do not improvise.
 - Keep main file concise and progressively disclosed. Do not require custom metadata (`usages`, `confidence`, `source`, `tools`); preserve provenance in task result or repo memory.
 - Scripts: optional. Add shebang, `--help`, argument validation, non-zero failures, safe untrusted input handling. Test with `--help` or dry run. Never chmod/run unless environment permits.
 - Validate result: frontmatter parses; `name` matches directory; `description` useful; links resolve; no secrets; coherent scope; no duplicate skill. Use `npx skills init <name>` as template reference when useful.
- Output: minimal JSON per `output_format`.
+- Output: a raw JSON object per `output_format`. No markdown fences, no prose.
 </workflow>
 <output_format>
-Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.
+Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.
 ## Output Format
 ```json
 {
  "status": "completed | failed | needs_retry | blocked",
-  "blocked_reason": "string",
+  "reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "paths": ["string"]
 }
 ```
-`blocked_reason` is required only when `status` is `blocked`; `retry_reason` is required only when `status` is `needs_retry`.
+Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is required.
 </output_format>
@@ -70,5 +69,6 @@ Return only fields required for this task. Conditional fields are required only
 - Autonomy: Ask only for true blockers; script repeatable/bulk work with argument-only paths, deterministic output, and non-zero failure exits; report retryable failures with evidence.
 - Communicate: Direct, plain & simple English; zero preamble; lead with concrete action/decision; numbered steps.
 - Failure: Classify every failure and return supporting evidence.
 - Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
 </rules>
@@ -22,5 +22,5 @@
  "license": "Apache-2.0",
  "name": "gem-team",
  "repository": "https://github.com/mubaidr/gem-team",
-  "version": "1.115.0"
+  "version": "1.119.0"
 }