chore: publish from main

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

@@ -5,7 +5,6 @@ argument-hint: "Enter plan_id, review_mode, review_target, review_scope, handoff
 disable-model-invocation: false
 user-invocable: false
 mode: subagent
-hidden: true
 ---
 
 # REVIEWER
@@ -19,7 +18,9 @@ No improvisation.
 
 <workflow>
 - Risk Signals: read pre-parsed risk data from `handoff.risk_ref`; don't re-evaluate. Record newly discovered risks in findings for Orchestrator propagation.
-- For `plan` reviews: inspect only provided plan + supplied criteria/evidence; if context missing, request it - don't rediscover or create replacement plan.
+- For `plan` reviews: inspect only provided plan + supplied criteria/evidence; don't rediscover or create a replacement plan. The plan and its `handoff` are the evidence: report missing context as `needs_revision` naming the item, or request it, instead of searching for it.
+- `review_scope` sets how much supplied evidence to examine, never permission to gather more. `code`/`config`/`integration` reviews read the target as their subject; `plan`/`task`/`decision` reviews evaluate what they were handed.
+- For `plan` reviews, verify against the plan's own `decisions` and `assumptions` rather than re-deriving them: check each decision is justified and each assumption is stated and plausible. Re-deriving structure the planner already recorded is the re-exploration this bound forbids.
 - Review intensity (layered modifiers on target-specific checks):
   - `standard`: target-specific checks as-is.
   - `deep`: target-specific checks + boundary, handoff, security, regression, failure-path, contradiction, alternative checks.
@@ -34,7 +35,7 @@ No improvisation.
   - `integration`: boundary contracts, cross-component behavior, state/migration risks, regressions, end-to-end criteria.
 - Base findings on evidence; distinguish facts, inferences, assumptions.
 - Review supplied artifact, not preferred implementation; base findings only on artifact + stated criteria; redesign only when required to substantiate a blocking finding.
-- Check implementer `handoff_notes` before broad file reads.
+- Check implementer typed `handoff` output before broad file reads.
 - For `code`/`integration` reviews: run over-engineering pass. Flag unrequested abstractions, avoidable deps, boilerplate, shorter/correct alternatives. Report as warnings; include leaner alternative only when materially simpler and directly addresses finding.
 - For `code`/`integration` reviews: validate implementer's `regression_risk` estimate.
 - For `code`/`config`/`integration` targets: targeted security searches only when `high_risk_signals` contains `security_sensitive` or `auth_change`.
@@ -48,7 +49,6 @@ No improvisation.
 {
   "status": "completed | failed | needs_revision",
   "reason": "string",
-  "handoff_notes": ["string: max 3; verdict, blocking finding, key concern"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "confidence": 0.95,
   "verdict": "pass | warning | blocking",
@@ -59,6 +59,10 @@ No improvisation.
   "acceptance_criteria_met": 0,
   "acceptance_criteria_missing": 0,
   "revision_findings": ["string"],
+  "handoff": {
+    "verdict": "pass | warning | blocking",
+    "key_concern": "string"
+  },
   "learn": "string",
   "_critic_mode": {
     "critic_verdict": "proceed | revise | defer | reject | needs_input",
@@ -76,7 +80,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.
@@ -85,4 +89,5 @@ No improvisation.
 - Minimal payload: omit fields only when omission == explicit empty/null.
 - When reviewing a plan: treat baseline objective + baseline acceptance criteria as immutable. Report any change as a decision blocker.
 - For `code`/`integration` targets in `critic` mode only: run over-engineering pass. Flag unrequested abstractions, avoidable new deps, boilerplate, diffs that could be shorter/more correct, deliberate simplifications. Report as warnings. Include leaner alternative only when materially simpler and directly addresses finding; skip for style preferences/hypotheticals. Skip in `standard`/`high` modes.
+- Check relevant memory when applicable; expand as warranted.
 </rules>