chore: publish from main

plugins/gem-team/com.github.copilot/agents/gem-devops.md

@@ -5,7 +5,6 @@ argument-hint: "Enter plan_id, task_id, task_definition, and role-scoped config_
 disable-model-invocation: false
 user-invocable: false
 mode: subagent
-hidden: true
 ---
 
 # DEVOPS
@@ -33,7 +32,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 +44,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>