[Feature Request] UX & Storage enhancements: Canvas "Pick Element" inspector and Clean Cache storage breakdown with DB compaction

Here are two proposed quality-of-life enhancements for daily workflows, focusing on visual Canvas revisions and Host storage transparency:

1. Canvas: "Pick Element" Inspector Tool (Targeted Revisions into GOA Draft)

Problem

Currently, asking GOD of Agents (or worker sessions) to revise a specific element inside a Canvas frame (e.g. a particular button, badge, sidebar width, or card) requires taking manual screenshots or writing lengthy spatial descriptions so the agent knows what to patch.

Proposed Workflow

Add an inspection cursor icon (like DevTools / Figma inspector) to the Canvas toolbar:

1. User toggles the Pick Element tool in the Canvas top bar.
2. Hovering over components in the Canvas webview highlights them with a visual bounding box.
3. Clicking a component:
   • Captures its target metadata (e.g., Frame ID, CSS selector/class, ID, and brief text snippet).
   • Automatically populates this reference into the active GOD of Agents input composer (e.g. [Canvas Frame 2: div.sidebar-feed] ).
   • Crucially: Does NOT send automatically. The composer keeps the text as an active draft with the cursor placed at the end.
4. The user simply types their revision instruction (e.g. make this 296px wide and use white-space: nowrap) and hits Enter when ready.

Benefit

• Zero manual screenshot cropping for visual tweaks.
• Eliminates ambiguous prompt instructions.
• Keeps the user in full control of the prompt before sending.

2. Host -> Clean Cache: Session Storage Breakdown & One-Click DB Compaction

Problem

Across intensive multi-agent workflows, disk usage can balloon without visibility:

• On our Windows 11 machine, OpenCode's SQLite database (~/.local/share/opencode/opencode.db) grew to 4.85 GB, causing noticeable disk I/O latency when loading sessions or histories.
• Session histories, canvas snapshots, and temporary screenshots accumulate over time.
• Currently, Host -> Clean cache operates as an opaque, all-or-nothing action with no visibility into which session or database is consuming space.

Proposed Enhancements to "Clean Cache"

Enhance the Clean cache page under Host into a transparent storage manager:

1. Storage Breakdown Table:
   Display a sorted summary list showing exactly where storage is allocated:

   • Agent Databases: e.g., OpenCode SQLite (opencode.db): 4.85 GB, Claude Code data: 220 MB.
   • Top Bloated Sessions (Dummy Example):
     • Session 5d866d3e (webapp-dashboard): 1.4 GB
     • Session abb15638 (canvas-prototype): 950 MB
     • Session b60df483 (GOD of Agents): 620 MB
   • Temporary Artifacts: Screenshots folder (~/.enowx-app/screenshots): 140 MB.

2. Targeted Optimization Actions:

   • [Compact & Vacuum Databases]: Executes an automated SQLite VACUUM on opencode.db and other local stores to reclaim unused allocated pages without deleting conversation histories.
   • [Prune Temporary Screenshots]: Safely removes screenshots older than 3 days from ~/.enowx-app/screenshots/.
   • [Clean Selected Session Cache]: Cleans caches for specific settled/inactive sessions while preserving active project sessions.

Benefit

• Immediate visibility into what is consuming drive storage.
• Compacting multi-gigabyte SQLite databases restores UI responsiveness and reduces disk lag on Windows.
• Recovers gigabytes safely without destroying active session context.