indifferentketchup/boocode
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: remove Go codecontext sidecar, wire all boocontext MCP tools

Browse Source 
Deletes all 17 native codecontext tool wrappers (~2,400 lines). Code analysis now provided entirely by boocontext MCP server (discovered at startup via appendMcpTools()). Adds 9 previously missing MCP tools (get_summary, scan, get_coverage, get_schema, get_env, get_events, get_knowledge, get_wiki_index, lint_wiki) to all relevant agent tool lists. Updates AGENTS.md, guidance files.
This commit is contained in:
indifferentketchup
2026-06-08 04:18:04 +00:00
parent 397234edaf
commit 6bc3c1cdd6
33 changed files with 50 additions and 2412 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
apps/server/src/services/synthesisPrompt.ts
View File

@@ -1,19 +1,19 @@
// v1.13.13: synthesis pipeline system prompt. Verbatim from the v1.13.13
// dispatch — do not paraphrase. The synthesis pass loads this as its sole
// system message, followed by a user message that concatenates the
// codecontext tool result, auto-fetched top files, auto-fetched project
// boocontext tool result, auto-fetched top files, auto-fetched project
// docs, and the original user message.
export const SYNTHESIS_SYSTEM_PROMPT = `You are synthesizing structural data into an accurate, detailed answer about the user's codebase.
Inputs you have been given:
1. The output of a codecontext analysis tool (raw structural data — file counts, symbols, dependencies, frameworks).
1. The output of a boocontext analysis tool (raw structural data — file counts, symbols, dependencies, frameworks).
2. The contents of the top files referenced in that output.
3. Any project documentation found in the repo root (BOOCHAT.md, AGENTS.md, roadmap docs, CONTEXT.md).
Rules:
- Cite specific files and line numbers when making claims about code.
- If project docs contradict the code, docs win for questions about state, version, status, or roadmap. Code wins for questions about runtime behavior or implementation.
- If the codecontext output looks sparse (low symbol count for a TypeScript project, missing dependency edges, empty framework list), explicitly say so — codecontext falls back to the JavaScript grammar for TypeScript and loses interfaces, generics, decorators, and type aliases.
- If the boocontext output looks sparse (low symbol count for a TypeScript project, missing dependency edges, empty framework list), explicitly say so — boocontext falls back to the JavaScript grammar for TypeScript and loses interfaces, generics, decorators, and type aliases.
- Do not invent symbols, files, or relationships that are not present in the inputs.
- Do not respond with a generic "this looks like a [framework] project" summary. The user has the framework analysis already. Add specifics: what is actually in this codebase, what is shipped, what is planned, what is load-bearing.
- Length: match the depth the user asked for. Overview questions get structured multi-section answers. Specific questions get focused answers.