fix: browser integration for AI research agent

- Dockerfile: Install Google Chrome stable instead of Playwright npm package
  (playwright-cli defaults to /opt/google/chrome/chrome path). Removed unused
  Playwright npm package, kept Playwright Python for page automation.

- bundle/bundle.md: Fix orchestrator config override with correct key path
  (session.orchestrator.config.extended_thinking: false) to properly override
  foundation's extended_thinking: true default, which was causing empty
  AI text responses.

- bundle/agents/researcher.md: Add strong pre-installed environment guardrail
  telling agent NOT to install packages. Add explicit bash() tool call examples
  showing correct playwright-cli syntax. Fix snapshot command (removed non-existent
  -ic flag), change 'type' to 'fill' for form field syntax.

- bundle/context/researcher-instructions.md: Enrich from thin pointer to
  concrete examples with correct bash() wrapping and actual playwright-cli
  commands. Add 'do NOT install' guardrail.

Validated: Agent now opens Chrome browser during research queries, noVNC panel
shows live browser activity, AI generates text responses properly.

Generated with Amplifier

Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>

bundle/context/researcher-instructions.md

@@ -3,22 +3,56 @@
 This session runs inside the **Research Workbench**. You have access to the
 following capabilities:
 
-## Available Capabilities
+## CRITICAL: Pre-installed Tools
 
-**Browser** — Live Chromium browser controlled via `playwright-cli -s=research`.
-The browser is persistent across commands and visible to the user via VNC (noVNC
-panel). The user can take over at any time.
+All tools are **already installed**. Do NOT run npm install, pip install, or any
+package manager. Just use the commands directly via the bash tool.
 
-**Artifacts** — Persistent markdown documents written to `artifacts/<session_id>/`.
+## Browser Control
+
+Live Chromium browser controlled via `playwright-cli -s=research` through the
+bash tool. The browser is persistent across commands and visible to the user via
+the noVNC panel. The user can take over at any time.
+
+**Quick start — open a site and see what's on it:**
+```
+bash("playwright-cli -s=research open https://google.com")
+bash("playwright-cli -s=research snapshot")
+```
+
+**Click an element from the snapshot:**
+```
+bash("playwright-cli -s=research click @e5")
+bash("playwright-cli -s=research snapshot")
+```
+
+**Type into a field and submit:**
+```
+bash("playwright-cli -s=research fill @e3 \"search query\"")
+bash("playwright-cli -s=research press Enter")
+bash("playwright-cli -s=research snapshot")
+```
+
+Always snapshot after navigation to get fresh element refs.
+
+## Artifacts
+
+Persistent markdown documents written to `artifacts/<session_id>/`.
 They appear in the right panel and survive across sessions.
 
-**A2UI** — Inline interactive controls (filter chips, tables, card grids, forms)
+## A2UI
+
+Inline interactive controls (filter chips, tables, card grids, forms)
 rendered directly in chat via `a2ui` code blocks.
 
-**Inline Visuals** — Rich visual output (charts, maps, comparison tables with color
+## Inline Visuals
+
+Rich visual output (charts, maps, comparison tables with color
 coding) rendered directly in chat via `visual` code blocks.
 
-## Full Command Reference
+## Research Workflow
 
-For complete command syntax, workflow guidance, and best practices, see the
-researcher agent system prompt.
+1. Understand the request — clarify scope and constraints
+2. Plan — identify 2-4 sources to consult
+3. Browse and extract — use playwright-cli via bash to navigate sites and extract data
+4. Present — use A2UI, visuals, or artifacts to deliver results