[pull] master from GaijinEntertainment:master

.gitignore

@@ -29,6 +29,13 @@ _aot_generated/
 
 opencoede.json
 
+# blind-mouse — ignore the regenerable SQLite index, but check in the .md
+# corpus under mouse-data/docs/ so curated answers ship in PRs.
+mouse-data/index.db
+mouse-data/index.db-journal
+mouse-data/*.db-wal
+mouse-data/*.db-shm
+
 modules/dasSFML/libsfml/
 site/
 doc/sphinx-build/

CLAUDE.md

@@ -35,6 +35,21 @@ Same applies to lint/format: `mcp__daslang__lint` / `format_file`, not shell `bi
 
 Fall back to `Bash`/`Grep`/`Read` only when the MCP tool reports an error or the question is genuinely outside MCP coverage (RST prose, CMake, Python tooling).
 
+## Asking blind-mouse
+
+Before doing significant research on a "how do I X?" / "what's the pattern for Y?" / "why does Z behave this way?" question, ask `mouse__ask`. blind-mouse (`utils/mouse/`) is a personal Q&A cache backed by curated `.md` answers — full vision in `utils/mouse/OVERVIEW.md`. Same deferred-tool dance as the daslang MCP: `ToolSearch select:mcp__mouse__<tool>` → invoke.
+
+**During plan mode / planning phase, ask the mouse early and often.** Planning is exactly the phase where prior-session research has the highest leverage: each "what's the pattern for X" / "where do we usually put Y" / "why did we pick Z" answer that's already in the cache saves a research detour, and each new finding worth keeping is one `mouse__add` away from being free next time. Concrete planning-phase prompts: design questions ("what's the right pattern for adding a new `[sql_*]` annotation?"), prior-art questions ("have we hit this glob-vs-rfind path bug before?"), gotcha-recall ("what's the const-stripping reinterpret incantation?"), trade-off recall ("why did we pick (a) over (b) last time?"). If the cache has nothing useful, do the research yourself — then `mouse__add` the answer before moving on, even if rough. The cost of writing a brief `.md` is far smaller than re-researching the same thing.
+
+| Reach for the mouse when… | Don't, when… |
+|---|---|
+| Planning a non-trivial change — sweep `mouse__ask` across the open questions before diving in | symbol lookup — use the daslang MCP (`find_symbol`, `grep_usage`, `find_references`) |
+| "how do I write a `[typefunction]` macro?" / "what's the right pattern for X?" / "why does Y behave this way?" | categorical conventions — those belong in `skills/*.md` / `CLAUDE.md` |
+| Discovered facts that don't fit any `skills/*.md` slot | project state, branch status, who's doing what — use git/issues/memory |
+| Recurring questions you remember answering before but forget the answer | |
+
+If `mouse__ask` returns nothing relevant and you do the research yourself, finish with `mouse__add` so the next session doesn't redo the work. If a returned answer is stale or wrong, edit the `.md` directly under `mouse-data/docs/` (it's a regular file, `Edit` works) and bump `last_verified`.
+
 ## Skill Files (REQUIRED)
 
 Task-specific instructions are split into skill files under `skills/`. You MUST read the relevant skill file(s) before performing the corresponding task.

CMakeLists.txt

@@ -1559,6 +1559,20 @@ install(DIRECTORY ${PROJECT_SOURCE_DIR}/utils/find-dupe/tests/
     FILES_MATCHING PATTERN "*.das"
 )
 
+# Install blind-mouse (personal Q&A cache MCP server).
+file(GLOB DAS_MOUSE_FILES ${PROJECT_SOURCE_DIR}/utils/mouse/*.das)
+install(FILES ${DAS_MOUSE_FILES} DESTINATION utils/mouse)
+install(FILES
+    ${PROJECT_SOURCE_DIR}/utils/mouse/README.md
+    ${PROJECT_SOURCE_DIR}/utils/mouse/OVERVIEW.md
+    ${PROJECT_SOURCE_DIR}/utils/mouse/.das_package
+    DESTINATION utils/mouse
+)
+install(DIRECTORY ${PROJECT_SOURCE_DIR}/utils/mouse/tests/
+    DESTINATION utils/mouse/tests
+    FILES_MATCHING PATTERN "*.das" PATTERN "*.md"
+)
+
 # Install daspkg (package manager)
 file(GLOB DAS_DASPKG_FILES ${PROJECT_SOURCE_DIR}/utils/daspkg/*.das)
 install(FILES ${DAS_DASPKG_FILES} DESTINATION utils/daspkg)