[ADR-016] Chunk 4: Performance Mode, prompt engineering, and Signal Flow bridge

[amiable-dev]

Task

Polish the conversational experience: update system prompt with signal awareness guidelines, add Performance Mode UI, and bridge Signal Flow clicks to Chat input.

Requirements

4A: System Prompt Engineering

• Add "Signal Awareness" section to system prompt with:
  • How to reference topology naturally
  • When to be proactive vs passive
  • Examples of good signal-aware responses
  • Performance Mode behaviour guidelines

4B: Performance Mode UI

• /performance chat command (on/off/toggle)
• Optional toggle icon in Chat header
• "PERF" badge when active
• Settings persist in signalContextStore.settings

4C: Signal Flow → Chat Bridge

• signalFlowAction store for cross-panel communication
• Click loop warning badge → pre-populate Chat input with resolution request
• Click unmapped indicator → pre-populate with mapping creation request
• Click error junction → pre-populate with error investigation request

Files to modify

• conductor-gui/ui/src/lib/stores/chat.js — system prompt + /performance command
• conductor-gui/ui/src/lib/stores/signal-context.js — Performance Mode settings
• conductor-gui/ui/src/lib/views/ChatView.svelte — toggle UI
• Signal Flow component (when implemented) — click handlers

Acceptance criteria

• /performance on enables mode and confirms in chat
• Proactive alerts suppressed in Performance Mode
• Clicking loop warning in Signal Flow pre-populates Chat input
• LLM naturally references device names and routing in responses

Depends on: Chunks 1–3
Parent: [ADR-016] Epic

[amiable-dev]

Update: Signal Flow View Dependency

Section 4C (Signal Flow → Chat Bridge) requires the Signal Flow workspace view

The click bridge described in Section 4C depends on the Signal Flow workspace view being implemented first. Specifically:

• Loop warning badges — click targets in LoopArc.svelte that pre-populate Chat input with resolution requests
• Unmapped indicators — click targets on track rails that pre-populate with mapping creation requests
• Error junctions — click targets in TrackJunction.svelte that pre-populate with error investigation requests

These components are defined in the Signal Flow workspace view issue. Section 4C should be implemented after Signal Flow Phase C (interactions) is merged, or at minimum after Phase A (static layout) if click handlers are added incrementally.

Design reference

V2 Combined tab in event-provenance-mockups-v2.html — shows the loop arcs, junction badges, and routing indicators that become the click bridge targets.

Updated dependency chain

Signal Flow Phase A ──→ Phase B ──→ Phase C ──→ Chunk 4 Section 4C
Chunks 1–3 ──────────────────────────────────→ Chunk 4 Sections 4A + 4B

Sections 4A (prompt engineering) and 4B (Performance Mode UI) can proceed independently of Signal Flow.

[amiable-dev]

All three sub-features are implemented and merged:

4A — System Prompt Engineering (PR #628)

• ## Signal Awareness section with topology/pulse/alert guidance
• Conversational tone guidelines, Performance Mode reference
• Simplified topology injection (no duplicate heading)

4B — Performance Mode (PR #628)

• /performance and /perf chat commands (on/off/toggle)
• setPerformanceMode() export in signal-context store
• "PERF" badge toggle in Chat header with aria-pressed
• Streaming state reset on command during in-flight requests
• Pulse interval doubling + proactive alert suppression (wired in Chunks 2–3)

4C — Signal Flow → Chat Bridge (PR #628 + #629)

• signalFlowAction store + bridgeSignalFlowToChat() helper
• Warning badge click → pre-populate Chat input + open Chat panel
• LoopArc click → Chat bridge (Phase C, PR feat(gui): Signal Flow Phases B & C — live animation, loop arcs, cross-track routing (#583) #629)
• Junction click → navigate to Mappings view (Phase C, PR feat(gui): Signal Flow Phases B & C — live animation, loop arcs, cross-track routing (#583) #629)
• Device pill click → highlight track (Phase C, PR feat(gui): Signal Flow Phases B & C — live animation, loop arcs, cross-track routing (#583) #629)

Test coverage: ~27 new tests across 5 files, all passing.