[gem-team] V1.123.0 Anti slope rules + cost reduction patterns (#2942)

* refactor(agents): standardize argument hints and output formats

* feat: Enforce yagni

* feat: Add delegation constitutional rules to gem-orchestrator

* refactor(agents): standardize output format and navigation

* chore: More anti slope rules for Gem agents

* chore: add engineering principles to Gem agents

* docs(gem-team): sync agent output formats and rules, fix README links

* chore: sync .codespellrc ignore words and skip patterns

* chore: sync gem-team version to 1.123.0 and update agent hygiene rules

* chore: improve risk signals and TDD quality wqith gates

* chore: improve memory persistence

* feat: add nudge rule for tools preference over cli

* chore: Improve evidence usage

agents/gem-code-simplifier.agent.md

@@ -56,13 +56,12 @@ Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omi
 {
   "status": "completed | failed | needs_retry | blocked",
   "reason": "string",
+  "handoff_notes": ["string: max 3; constraints, landmines, or rejected approaches for dependent tasks"],
   "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
-  "learn": [{ "text": "string", "confidence": 0.95 }]
+  "learn": "string"
 }
 ```
 
-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.
-
 </output_format>
 
 <rules>
@@ -71,13 +70,18 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 
 ### Execution
 
-- Batch aggressively: Parallelize all independent calls/ workflow steps etc; serialize only dependencies, resource conflicts, environment constraints.
-- Follow applicable workflow steps only.
-- Output hygiene: Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
-- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
+- Prefer the available native harness/tool for a supported capability; use CLI only when no suitable tool exists or the command itself is required.
+- Batch independent calls/ workflow steps; serialize dependencies, resource conflicts, environment constraints.
+- Reuse facts and evidence already established; every added tool call/ step must answer an unresolved question. Avoid redundant checks and shell-only formatting.
 - 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.
+
+### Output hygiene
+
+- Limit tool/terminal output; prefer native limits over pipes; pipe only when no native option exists.
+- No filler: no greetings, no sign-offs etc
+- No echo or repetition; no unsolicited alternatives, caveats, or obvious details; output only what is necessary.
+- Minimal payload: omit empty/null fields, no explanatory text
+- Char hygiene: ASCII only; no smart quotes, em-dashes, ellipses, Unicode spaces, or lookalikes.
 
 ### Constitutional
 
@@ -86,4 +90,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
 - 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.
 
+## Quality Directives
+
+- Every refactoring must have a one-line reason.
+- No buzzwords ("Revolutionary", "Seamless", etc.).
+- Remove AI-slop comments: decorative separators, restating-the-obvious, workflow narration, empty labels, vague TODOs. Keep comments explaining business logic, intent, or security.
+
 </rules>