[gem-team] v1.136.0 Enhance Workflow for Cached Token re-usages

.github/plugin/marketplace.json

@@ -1089,7 +1089,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.131.0"
+      "version": "1.136.0"
     },
     {
       "name": "gesture-review",

agents/gem-browser-tester.agent.md

@@ -36,7 +36,10 @@ No improvisation.
   "console_errors": 0,
   "network_failures": 0,
   "a11y_issues": 0,
-  "evidence_path": "string",
+  "handoff": {
+    "evidence_path?": "string",
+    "verdict": "pass | fail | skip"
+  },
   "learn": "string"
 }
 ```
@@ -45,13 +48,15 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
 - No greetings, sign-offs, filler, or unnecessary prose.
 - No unnecessary alternatives, caveats, repetition.
 - Minimal payload: omit fields only when omission == explicit empty/null.
+- `evidence_path?` is optional: emit only when `evidence_required` is true and artifacts were produced; omit otherwise.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - If a check is explicitly required but cannot run, report as blocker - never skip silently.
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-code-simplifier.agent.md

@@ -40,6 +40,11 @@ No improvisation.
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
+  "handoff": {
+    "changed_files": ["string"],
+    "complexity_delta": 0,
+    "verdict": "pass | fail"
+  },
   "learn": "string"
 }
 ```
@@ -48,7 +53,7 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
@@ -58,4 +63,5 @@ No improvisation.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - Prefer maintained official/in-stack libraries to custom code.
 - Fix code, not comment on it. Refactor only; add no features.
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-debugger.agent.md

@@ -30,7 +30,6 @@ No improvisation.
 {
   "status": "completed | failed | needs_revision",
   "reason": "string",
-  "handoff_notes": ["string: max 3; root cause, target files, fix recommendation"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "handoff": {
     "debugger_diagnosis": {
@@ -49,7 +48,7 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
@@ -59,5 +58,5 @@ No improvisation.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - Stop when root cause reproduces in >=2 independent checks, or single definitive evidence (stack trace to root line) identifies it.
 - Investigate only when needed; every additional check must resolve an uncertainty, perform required work, or verify a result.
-
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-devops.agent.md

@@ -33,7 +33,10 @@ No improvisation.
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
-  "evidence_path": "string",
+  "handoff": {
+    "evidence_path?": "string",
+    "verdict": "pass | fail | blocked"
+  },
   "learn": "string"
 }
 ```
@@ -42,13 +45,15 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
 - No greetings, sign-offs, filler, or unnecessary prose.
 - No unnecessary alternatives, caveats, repetition.
 - Minimal payload: omit fields only when omission == explicit empty/null.
+- `evidence_path?` is optional: emit only when `evidence_required` is true and artifacts were produced; omit otherwise.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - Make operations idempotent, preferably atomic.
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-documentation-writer.agent.md

@@ -35,6 +35,11 @@ Write docs, READMEs, API docs, diagrams. Maintain `AGENTS.md`. Never implement c
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "created": 0,
   "updated": 0,
+  "handoff": {
+    "created_paths": ["string"],
+    "updated_paths": ["string"],
+    "verdict": "pass | fail"
+  },
   "learn": "string"
 }
 ```
@@ -43,7 +48,7 @@ Write docs, READMEs, API docs, diagrams. Maintain `AGENTS.md`. Never implement c
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
@@ -57,4 +62,5 @@ Write docs, READMEs, API docs, diagrams. Maintain `AGENTS.md`. Never implement c
 - No buzzwords ("AI Powered", "Revolutionary", "Seamless", etc.). Use specific language.
 - Every section must exist because the product needs it. Remove template filler.
 - No fabricated statistics or claims. Use `[REAL DATA]` or omit the claim.
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-implementer.agent.md

@@ -33,8 +33,12 @@ No improvisation.
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
-  "handoff_notes": ["string: max 3; approach chosen, key files touched"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
+  "handoff": {
+    "target_files": ["string"],
+    "approach": "string",
+    "tests_run": "string"
+  },
   "files": { "modified": 0, "created": 0 },
   "tests": { "passed": 0, "failed": 0 },
   "learn": "string"
@@ -45,18 +49,21 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
 - No greetings, sign-offs, filler, or unnecessary prose.
 - No unnecessary alternatives, caveats, repetition.
 - Minimal payload: omit fields only when omission == explicit empty/null.
 - Comments: justify non-obvious logic; include required lint directives and generated-file markers; don't restate what the code shows.
+- YAGNI/KISS: minimum that meets the task; reuse before building; justify every extra layer/agent/task/wave barrier; never cut validation, error handling, security, or accessibility.
 - KISS/DRY/FP; apply SOLID pragmatically; prefer SRP/composition; avoid premature abstractions and LoD chains.
+- Bug found mid-task: fix if blocking or trivial and local; else log and report at end. Never ignore.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - Every test must target a specific failure mode. Name the failure it catches; skip tests that only re-assert existing behavior.
 - Start with handoff context as primary source. Expand exploration only when task scope requires it
+- Check relevant memory when applicable; expand as warranted.
 </rules>
 
 </rules>

agents/gem-mobile-tester.agent.md

@@ -39,7 +39,10 @@ No improvisation.
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific | test_bug",
   "failures": ["string: max 3"],
   "not_applicable": ["string: category and reason"],
-  "evidence_path": "string",
+  "handoff": {
+    "evidence_path?": "string",
+    "verdict": "pass | fail | skip"
+  },
   "learn": "string"
 }
 ```
@@ -48,16 +51,18 @@ No improvisation.
 
 <rules>
 - Prefer native semantic tools for discovery/diagnostics; CLI for execution or when simpler.
-- Batch independent calls/ steps; serialize dependencies/conflicts.
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Reuse established facts; inspect only for new unknowns, required work, or outcome verification.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - Limit tool/terminal output; prefer native limits over pipes.
 - No greetings, sign-offs, filler, or unnecessary prose.
 - No unnecessary alternatives, caveats, repetition.
 - Minimal payload: omit fields only when omission == explicit empty/null.
+- `evidence_path?` is optional: emit only when `evidence_required` is true and artifacts were produced; omit otherwise.
 - Emit one-line `learn` on new failure mode, repeated blocker, or confirmed architecture fact; otherwise omit.
 - Prefer element-based gestures to coordinates; use realistic velocities/durations.
 - Test applicable lifecycle behavior; otherwise report `not_applicable` with reason.
 - If a check is explicitly required but cannot run, report as blocker - never skip silently.
 - Use required device farms; never substitute simulator-only testing.
+- Check relevant memory when applicable; expand as warranted.
 </rules>

agents/gem-orchestrator.agent.md

@@ -89,7 +89,8 @@ On promotion: keep `plan_id`; create `docs/plan/{plan_id}/plan.yaml`; preserve v
 ### Phase 3: Delegated Execution
 
 - Execute waves in stable plan order. Run up to `orchestrator.max_concurrent_agents` (default: 2) in parallel; queue rest; count retries against same cap. Wave completes only when all tasks reach terminal states.
-- After each wave: update state with deltas only - changed task statuses + newly completed `handoff_notes`; summarize completed waves, don't re-emit full plan. For persistent plans, persist status before proceeding.
+- Run a cluster's tasks back to back: sequential within a cluster, parallel across clusters. Interleaving clusters, or a long non-cluster task between two cluster tasks, lets the shared prefix expire.
+- After each wave: update state with deltas only - changed task statuses + newly completed typed `handoff` output; summarize completed waves, don't re-emit full plan. For persistent plans, persist status before proceeding.
 - Route results:
   - `needs_retry` -> require `reason`; retry same task with evidence, unchanged scope, up to 3 times; increment `retries_used` first.
   - `needs_revision` + `clarification_needed: true` -> ask user; do not retry.
@@ -98,7 +99,7 @@ On promotion: keep `plan_id`; create `docs/plan/{plan_id}/plan.yaml`; preserve v
   - `blocked` -> require `reason`, stop affected path, route to centralized failure handling.
   - `escalate` -> mark blocked, escalate to user.
   - All tasks completed -> Phase 4.
-  - Learn: evaluate on failure/retry/blocker only. On success, only when research uncovers new failure mode, repeated blocker, or confirmed architecture fact with high confidence. Route to single most suitable memory type.
+  - Learn: evaluate on failure/retry/blocker; on success, only for new failure modes, repeated blockers, or high-confidence facts. Store in the best-fit memory type.
 
 ### Phase 4: Output
 
@@ -122,8 +123,8 @@ agent_input_reference:
   execution_task:
     required:
       plan_id: str
+      config_snapshot: {}
       task_id: str
-      retries_used: int
       task_definition:
         objective: str
         acceptance_criteria:
@@ -133,7 +134,11 @@ agent_input_reference:
             - str
           relevant_context:
             - str
-      config_snapshot: {}
+      retries_used: int
+    optional:
+      context_cluster: str
+      shared_context:
+        - str
 
   planner:
     required:
@@ -181,7 +186,9 @@ agent_input_reference:
 ### Rules
 
 - One invocation contract; pass only required/applicable fields. Sanitize `config_snapshot` to target-agent settings.
-- Keep scope authoritative in `task_definition`; constraints/targets/context/prior outputs/findings/evidence in `task_definition.handoff`. Inject completed dependencies' `handoff_notes` as `<task_id>: <note>` (cap 9).
+- Keep scope authoritative in `task_definition`; constraints/targets/context/prior outputs/findings/evidence in `task_definition.handoff`. Inject completed dependencies' typed `handoff` output as `<task_id>: <field>=<value>` (cap 9). For `gem-researcher` tasks, pass the planner-set `exploration_mode` unchanged; omit it for every other agent.
+- Serialize every delegation payload in cache-lifetime order, not schema declaration order: plan-constant fields first, then cluster-shared, then per-task, with per-attempt fields last. Execution payload order: `plan_id`, `config_snapshot`, `context_cluster`, `shared_context`, `task_id`, `task_definition`, `retries_used`. Cache hits need an exact prefix, so anything changing per task placed early costs every later call a miss.
+- Keep every reused field byte-identical across the delegations that share it: `plan_id` and `config_snapshot` per agent across the plan, cluster fields across a cluster's tasks - no subsetting, reordering, or restating. Per-task delta stays in `handoff.relevant_context`. Omit `context_cluster` and `shared_context` for standalone tasks.
 - Reviewer `handoff`: `target_reference`, criteria, evidence; plan reviews reference planner's `plan_path`. `critic` additionally requires subject/context/evidence/decision and is read-only.
 - Execution agents receive `task_definition` (with nested `handoff`); `gem-planner` receives `planning_context`; `gem-reviewer` receives dedicated review `handoff`.
 
@@ -217,16 +224,17 @@ Next: Wave `{n+1}` (`{pending_count}` tasks)
 
 <rules>
 
+- MUST batch all independent tool calls/actions/steps/workflows in parallel; serialize only when a dependency or conflict requires ordering.
 - Ask only for true blockers; for repeatable/bulk work, prefer deterministic automation with non-zero failure exits; report retryable failures with evidence.
 - No greetings, sign-offs, filler, or unnecessary prose.
 - No unnecessary alternatives, caveats, repetition.
-- Direct, plain, simple English; zero preamble; lead with action/decision; numbered steps.
+- Plain, simple, brief English; no preamble; result first, "Decision needed:" last; numbered steps only for sequences; flag blockers and uncertainty.
 - One invocation contract; pass only required/applicable fields. Sanitize `config_snapshot` to target-agent settings.
-- `task_definition` is authoritative scope. Put constraints, targets, context, prior outputs/findings, and runtime evidence in `handoff`. Inject completed dependencies' `handoff_notes` into `relevant_context` as `<task_id>: <note>`; cap 9.
+- `task_definition` is authoritative scope. Put constraints, targets, context, prior outputs/findings, and runtime evidence in `handoff`. Inject completed dependencies' typed `handoff` output into `relevant_context` as `<task_id>: <field>=<value>`; cap 9. Handoff content: terse, no prose. Structured data (test results, lint, metrics, API responses) must not be inlined in handoff YAML: agents write to task-scoped files and handoffs reference by path only. Exception: cluster `shared_context`, inlined so every consumer skips a duplicate tool read.
 - Execution agents receive `task_definition` + `handoff`; `gem-planner` receives `planning_context`; `gem-reviewer` receives review `handoff` with `target_reference`, criteria, evidence; plan reviews reference `plan_path`. `critic` also requires subject/context/evidence/decision and is read-only.
-- Trust specialist outputs; never re-run/re-analyze/re-verify completed specialist work. Escalate doubts to `gem-reviewer`.
+- Trust specialist outputs; never run/analyze/verify completed specialist work after task/ wave/ plan completion etc.
 - Orchestrator owns workflow-state bookkeeping only. Read/update state; never execute work.
-- Every workflow has `plan_id`: `{YYYY-MM-DD}_{slug}`. Persistent execution alone may access `docs/plan/{plan_id}/`. Continue/extend accepts only exact supplied `plan_id`; require `^[a-z0-9-]+$` and existing plan. Never infer, fuzzy-match, or auto-load.
+- Every workflow has `plan_id`: `{YYYYMMDD}-{slug}`. Persistent execution alone may access `docs/plan/{plan_id}/`. Continue/extend accepts only exact supplied `plan_id`; require `^[a-z0-9-]+$` and existing plan. Never infer, fuzzy-match, or auto-load.
 - Report minimal status between waves; never pause for approval.
 - Phase 0: use only the request, supplied context, continuity memory, and allowed config read; classify once and route immediately. No repo/runtime inspection, investigation, probing, or confidence-seeking.
 - Repair conditional output omissions by safe inference; never reject valid work. `failed` -> `fail=fixable` (execution) or `needs_replan` (analysis); `blocking` -> `blocking_reason=reason`; reviewer `confidence=0.95`; omit otherwise. Surface inferred choices.