sync: auto-sync from GURU-BEAST-ROG at 2026-06-08 08:40:52

Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-06-08 08:40:52

.claude/memory/MEMORY.md

@@ -58,6 +58,7 @@
 - [Paste-safe command formatting (Howard)](feedback_command_formatting.md) — Two clauses, one root cause: (a) multi-line scripts not semicolon one-liners (wrap breaks paste), (b) all code at column 0 inside fences (indentation breaks PowerShell paste).
 - [Autonomous infra/build setup](feedback_autonomous_infra_setup.md) — During infra/build/CI/dev setup, just install prerequisites and push through routine steps; reserve check-ins for genuine decisions (forks, destructive/outward, client/prod).
 - [Check patterns before asking](feedback_check_patterns_before_asking.md) — Before asking how to do something repeat-style (sync, save, sweep, billing), study existing artifacts and workflow docs first; reach for similar past artifacts as the template.
+- [Calibrate effort to stakes](feedback_calibrate_effort_to_stakes.md) — Don't over-verify or over-engineer low-consequence details; confirm the happy path, note the limitation, and take the simplest path (e.g. put the instruction in the prompt) instead of building robust mechanisms.
 - [Pricing verification — no guessing](policy_pricing_verification.md) — ANY cost presented to the team or a client MUST be verified via live web lookup (WebFetch/WebSearch, fallback to headless Chrome). Never estimate from training data. Cite source + date inline. If unreachable, say so — do NOT substitute a guess.
 - [Client communication tone](feedback_client_tone.md) — How to write client-facing Syncro comments — expert partner, not intake questionnaire.
 - [Default to inline links](feedback_inline_links.md) — Use `[text](url)` inline markdown links (clickable, wrap-safe) not bare URLs in code fences; exception = raw URL the user must copy/paste.

.claude/memory/feedback_calibrate_effort_to_stakes.md

@@ -0,0 +1,21 @@
+---
+name: feedback_calibrate_effort_to_stakes
+description: Don't over-verify or over-engineer low-consequence setup; prefer the simplest path
+metadata:
+  type: feedback
+---
+
+When a detail is low-stakes, Mike wants effort calibrated to it — stop deep
+verification and take the simplest path. Concretely: when the Grok `AGENTS.md`
+context file didn't load in every CLI mode (only review modes, not text/verify),
+Mike cut off the mode-by-mode probing with "It's not that consequential. You can
+just include those instructions in the prompt."
+
+**Why:** Chasing a complete fix for a marginal-value detail burns time and tokens
+for no real benefit. The cheap, good-enough path (put the instruction in the
+prompt when it actually matters) beats engineering robust file discovery.
+
+**How to apply:** Before deep-verifying or building a robust mechanism, judge the
+consequence. For low-stakes items, confirm the happy path works, note the
+limitation plainly, and move on — offer the heavier fix only if asked. Reserve
+adversarial verification for things where being wrong is costly.