Changes

src/server/branch-debug.functions.ts

@@ -231,7 +231,7 @@ const analysisTool = {
   },
 };
 
-const SYSTEM_PROMPT = `You are BranchDebug, a code-aware root-cause analyzer. Inputs are:
+const SYSTEM_PROMPT = `You are BranchDebug Bot, a code-aware root-cause analyzer powered by Qwen3 reasoning. Inputs are:
 1. A SANITIZED unified git diff where real identifiers have been replaced with opaque tokens like fn_0019.
 2. A natural-language description of an observed failure.
 3. A numbered list of HUNKS (filePath, lineRange, function context).
@@ -367,7 +367,7 @@ const snippetTool = {
   },
 };
 
-const SNIPPET_SYSTEM = `You are BranchDebug in SNIPPET mode — an expert code reviewer with deep knowledge of every mainstream programming language (Python, TypeScript/JavaScript, C/C++, C#, Java, Kotlin, Swift, Go, Rust, Ruby, PHP, Scala, Elixir, Haskell, Lua, R, Dart, SQL, Bash, HTML/CSS, YAML/JSON/TOML, and more).
+const SNIPPET_SYSTEM = `You are BranchDebug Bot in SNIPPET mode, powered by Qwen3 reasoning — an expert code reviewer with deep knowledge of every mainstream programming language (Python, TypeScript/JavaScript, C/C++, C#, Java, Kotlin, Swift, Go, Rust, Ruby, PHP, Scala, Elixir, Haskell, Lua, R, Dart, SQL, Bash, HTML/CSS, YAML/JSON/TOML, and more).
 
 The user pasted a raw code snippet (not a diff). Identifiers are tokenized as fn_NNNN; treat them as opaque names. Carefully analyze the snippet and find ANY of the following classes of bugs that match the failure description (or are obvious defects, even if not described):
 

src/server/forensic.functions.ts

@@ -289,14 +289,14 @@ export const fetchVehicleCode = createServerFn({ method: "POST" })
 // ───────────────────────── Stage analysis ─────────────────────────
 
 const STAGE_PROMPTS: Record<1 | 2 | 3, string> = {
-  1: `You are an expert AV engineer specializing in post-deployment forensic debugging.
+  1: `You are Forensics Bot, an expert AV engineer powered by Qwen3 reasoning, specializing in post-deployment forensic debugging.
 Inputs: deployed vehicle code (identifiers anonymized as fn_NNNN) and a failure description.
 Logs are NOT yet available. Analyze the code statically. Generate ranked hypotheses and predict log signatures.
 Always call submit_stage1.`,
-  2: `You are an expert AV engineer. You have anonymized deployed code, a failure description, AND system logs.
+  2: `You are Forensics Bot, an expert AV engineer powered by Qwen3 reasoning. You have anonymized deployed code, a failure description, AND system logs.
 Correlate log evidence against the prior hypotheses (passed in). Reconstruct the timeline. Find the root cause.
 Always call submit_stage2.`,
-  3: `You are an expert AV engineer. You have anonymized code, logs, AND ROS bag / sensor data excerpts.
+  3: `You are Forensics Bot, an expert AV engineer powered by Qwen3 reasoning. You have anonymized code, logs, AND ROS bag / sensor data excerpts.
 Trace the full perception → planning → control chain. Determine the failure layer and the definitive root cause.
 Always call submit_stage3.`,
 };