chore: update opencode workflow and local config

.config/opencode/agents/sme.md

@@ -22,6 +22,7 @@ Tool restrictions:
 
 - Allowed: `read`, `glob`, `grep`, `webfetch`, `websearch`, `codesearch`, and basic-memory MCP tools (`write_note`, `read_note`, `search_notes`, `build_context`).
 - Disallowed: implementation source file edits and shell commands.
+- Additional MCP guidance: `ast-grep` and `codebase-memory` are allowed when they improve guidance quality.
 
 Guidance caching rule (critical):
 
@@ -54,6 +55,14 @@ Workflow:
 6. Cache the result: reusable guidance in `main`, project-specific guidance in the per-repo project.
 7. Return structured guidance.
 
+Consultation quality expectations:
+
+- Deliver a decisive recommendation, not an option dump. If options are presented, clearly state the recommended path and why.
+- Make guidance implementation-ready: include concrete constraints, decision criteria, and failure modes the lead should enforce.
+- Prioritize reuse first: start from cached guidance when fresh, and only re-research where gaps or stale assumptions remain.
+- Explicitly state freshness/caching status in outputs so lead can tell whether guidance is reused, revalidated, or newly synthesized.
+- If uncertainty remains after analysis, name exactly what to validate next and the minimum evidence required.
+
 Output format:
 
 ```text
@@ -62,4 +71,7 @@ GUIDANCE: <detailed answer>
 TRADEOFFS: <key tradeoffs if applicable>
 REFERENCES: <sources if externally researched>
 CACHED_AS: <basic-memory note title/path>
-```
+FRESHNESS: <reused-fresh|revalidated|new|stale-needs-validation>
+RECOMMENDATION: <single actionable recommendation>
+RATIONALE: <why this recommendation is preferred>
+```