Zeroclaw: Add quick access entry points

[Keith-CY]

Summary

Users currently must navigate to the Doctor page to interact with zeroclaw. This adds unnecessary steps, especially when a quick diagnosis is needed from other parts of the app.

Proposal

• Add a global keyboard shortcut or floating action button to invoke a quick zeroclaw dialog from any page
• Add a "Quick Diagnose" button on each instance card in the instance list, pre-filling the instance context
• Support one-click diagnosis from error dialogs, automatically carrying the error context into the zeroclaw conversation
• The quick dialog should be a lightweight overlay, not a full page navigation

Affected Files

• Frontend: new global dialog component
• Instance list page — add per-instance action button
• Error dialog components — add "Diagnose with Crayfish" action
• src-tauri/src/doctor_commands.rs — support context-prefilled sessions

Motivation

Lowers the barrier to using zeroclaw. Users encountering problems should be one click away from intelligent help, regardless of where they are in the app.

[dev01lay2]

Implementation Plan

Phase 1 — Global Quick Dialog

1. Create a QuickDiagnoseDialog component (lightweight overlay, no full-page navigation)
   • Closes on Escape or backdrop click
   • Accepts an optional prefillContext?: DiagnoseContext prop (error message, instance id, etc.)
2. Register a global keyboard shortcut (suggested: Cmd/Ctrl + Shift + D)
3. Mount the dialog and shortcut listener at the app root

Phase 2 — Instance Card Entry Point

4. Add a "Quick Diagnose" button to each instance card in the instance list
   • Opens QuickDiagnoseDialog pre-filled with the instance context (id, name, current status)

Phase 3 — Error Dialog Entry Point

5. Add a "Diagnose with Zeroclaw" action to all error dialogs
   • Automatically carries the error message / stack as prefill context

Phase 4 — Backend Support

6. doctor_commands.rs — add a start_quick_diagnose_session(context: DiagnoseContext) Tauri command
   • Supports context pre-filling, injecting it at the start of the zeroclaw session

---

Acceptance Checklist

• The zeroclaw dialog can be invoked from any page via keyboard shortcut without triggering page navigation
• When the dialog opens with a prefill context, the first message is automatically populated with that context
• Every instance card in the instance list has a "Quick Diagnose" button that opens the dialog pre-filled with the instance's information
• All error dialogs have a "Diagnose with Zeroclaw" button that carries the current error details
• The keyboard shortcut works on pages other than the Doctor page
• The dialog can be dismissed via Escape or backdrop click
• Existing Doctor page full-flow is not broken
• The start_quick_diagnose_session Tauri command accepts a structured context and correctly serializes/deserializes it on the Rust side
• New components have basic unit tests (prefill logic, keyboard shortcut binding)
• E2E: clicking Quick Diagnose on an instance card opens the dialog with the correct prefilled context

[dev01lay2]

Additional note: All quick access entry points (dialog, instance card button, error dialog action, keyboard shortcut) should only be visible when the Doctor / zeroclaw feature is enabled in Alpha Features settings. Add this to the acceptance checklist:

• Quick access entry points (global shortcut, instance card button, error dialog action) are hidden when the Doctor / zeroclaw alpha feature is disabled, and appear only after it is enabled