v2.3.0-sampling-params-ask-user: agent sampling params, ask_user_input in CoderPane, UX polish

Add top_p/top_k/min_p/presence_penalty to AGENTS.md frontmatter and thread
through inference (agents.ts parser → Agent type → stream-phase → sentinel
summaries). Null means omit from request body, preserving provider defaults.

Wire ask_user_input interactive card into both BooCoder frontends: the
CoderPane in BooChat's SPA (CoderMessageList now renders AskUserInputCard
instead of ToolCallLine for ask_user_input tool calls) and the standalone
coder SPA (MessageBubble + new AskUserInputCard + shadcn ui primitives).

Additional fixes: SessionLandingPage uses ChatInput with slash-command
support and lazy chat creation; Session.tsx hydrate-race fix for empty pane
promotion; AgentPicker wider dropdown with line-clamp; ModelPicker min-width;
Textarea converted to forwardRef; Recon agent added to AGENTS.md; codecontext
host port exposed in docker-compose.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

data/AGENTS.md

@@ -2,7 +2,11 @@
 
 ## Code Reviewer
 ---
-temperature: 0.3
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
 tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
 description: Reviews code for bugs, security issues, and maintainability. Read-only.
 ---
@@ -37,7 +41,11 @@ Codecontext usage:
 
 ## Debugger
 ---
-temperature: 0.4
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
 tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
 description: Diagnoses bugs from error messages, logs, or described symptoms.
 ---
@@ -58,7 +66,11 @@ Rules:
 
 ## Refactorer
 ---
-temperature: 0.3
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
 steps: 5
 tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
 description: Proposes refactors for clarity, deduplication, or decoupling. Read-only — outputs plans, not edits.
@@ -97,7 +109,11 @@ Codecontext usage:
 
 ## Architect
 ---
-temperature: 0.5
+temperature: 1.0
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 1.5
 steps: 20
 tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
 description: Designs new features, modules, or architectural changes. Outputs a build plan.
@@ -136,7 +152,11 @@ Codecontext usage:
 
 ## Security Auditor
 ---
-temperature: 0.2
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
 tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
 description: Audits code for security vulnerabilities. Read-only.
 ---
@@ -177,7 +197,11 @@ Codecontext usage:
 
 ## Prompt Builder
 ---
-temperature: 0.4
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
 tools: [view_file, list_dir, grep, find_files]
 description: Builds prompts for OpenCode, Claude Code, or BooCode dispatch.
 ---
@@ -208,3 +232,29 @@ Rules:
 - For BooLab frontend prompts, always include the "verify shadcn primitives exist" preflight
 
 Output: the prompt, ready to paste. Nothing else.
+
+## Recon
+---
+temperature: 0.6
+top_p: 0.95
+top_k: 20
+min_p: 0.0
+presence_penalty: 0.0
+tools: [find_files, get_codebase_overview, get_dependencies, get_file_analysis, get_framework_analysis, get_semantic_neighborhoods, get_symbol_info, grep, list_dir, search_symbols, view_file, watch_changes]
+description: Discovers and maps unfamiliar codebases. Reads architecture, traces data flow, identifies key symbols.
+---
+You map codebases. Start broad, then drill into specifics.
+
+Process:
+1. get_codebase_overview for the big picture — file count, languages, top-level structure.
+2. list_dir the top-level directories to understand the layout.
+3. get_semantic_neighborhoods and get_hot_files to find core modules and high-impact files.
+4. Trace data flow: entry points → handlers → services → data stores.
+5. Identify conventions: error handling, logging, testing patterns, naming.
+
+Output:
+- Architecture overview (one paragraph)
+- Key files and their roles
+- Data flow map (entry → transform → output)
+- Conventions observed
+- Areas that need deeper investigation