Document current coding-workflow stack state

Snapshot of where opencode + Qwen3-Coder + MCPs + Kimi-Linear + voice
  + Phoenix tracing land today, plus in-flight (oc-tree, kimi-linear
  context ramp) and next (ComfyUI) items with pointers to per-project
  NEXT_STEPS.md guides.

opencode/serena-ide-trim.yml

@@ -0,0 +1,92 @@
+# Custom Serena context for the localgenai stack.
+#
+# Extends Serena's built-in `ide` context with deeper exclusions tailored to
+# opencode + a local 70B-class model. Loaded by Serena via the
+# `--context /abs/path/to/this.yml` flag (install.sh rewrites the relative
+# path in opencode.json to the repo's absolute path at deploy time).
+#
+# Trim summary (see opencode/README.md for rationale):
+#   46 raw tools  →  ide context excludes 5  →  this context excludes 28 more
+#   →  ~12 visible tools, all unique LSP value
+#
+# Cut categories:
+#   - JetBrains backend (11)         — language_backend: LSP, never JetBrains
+#   - Line-level edits (5)           — opencode's Edit covers them
+#   - Memory tools (6)               — basic-memory MCP is canonical
+#   - Onboarding / meta (5)          — bootstrap noise the model rarely needs
+#   - Destructive / dashboard (2)    — remove_project, open_dashboard
+#
+# Kept (the unique LSP value, the reason we installed Serena):
+#   find_symbol, find_referencing_symbols, get_symbols_overview,
+#   replace_symbol_body, insert_after_symbol, insert_before_symbol,
+#   rename_symbol, safe_delete_symbol, restart_language_server,
+#   list_queryable_projects, query_project (+ activate_project, latent)
+
+description: opencode IDE context, trimmed for local 70B
+
+prompt: |
+  You are running in an IDE assistant context where file operations,
+  basic (line-based) edits and reads, and shell commands are handled by
+  your own, internal tools.
+
+  If Serena's tools can be used to achieve your task, you should
+  prioritize them. In particular, it is important that you avoid reading
+  entire source code files unless it is strictly necessary! Instead, for
+  exploring and reading code in a token-efficient manner, use Serena's
+  symbolic-search tools (find_symbol, find_referencing_symbols,
+  get_symbols_overview).
+
+excluded_tools:
+  # Inherited from built-in ide context (opencode built-ins cover these)
+  - create_text_file
+  - read_file
+  - execute_shell_command
+  - find_file
+  - list_dir
+
+  # Line-level edits — redundant with opencode's Edit and Grep
+  - replace_content
+  - delete_lines
+  - replace_lines
+  - insert_at_line
+  - search_for_pattern
+
+  # Memory tools — basic-memory MCP is the canonical persistent memory
+  - write_memory
+  - read_memory
+  - list_memories
+  - delete_memory
+  - rename_memory
+  - edit_memory
+
+  # Onboarding / meta — bootstrap noise
+  - check_onboarding_performed
+  - onboarding
+  - initial_instructions
+  - serena_info
+  - get_current_config
+
+  # Destructive / dashboard
+  - remove_project
+  - open_dashboard
+
+  # JetBrains backend — never used in this setup (language_backend: LSP)
+  - jet_brains_find_symbol
+  - jet_brains_move
+  - jet_brains_safe_delete
+  - jet_brains_inline_symbol
+  - jet_brains_find_referencing_symbols
+  - jet_brains_get_symbols_overview
+  - jet_brains_type_hierarchy
+  - jet_brains_find_declaration
+  - jet_brains_find_implementations
+  - jet_brains_rename
+  - jet_brains_debug
+
+tool_description_overrides: {}
+
+# When `single_project: true` and a project is given at startup, Serena
+# limits the toolset to what the project actually needs and disables
+# `activate_project`. With opencode launching Serena via
+# `--project-from-cwd`, a project is always present.
+single_project: true