FEATURE IDEA: Categories and workflows

Summary
To support complex user projects and task automation within exxperts, I propose extending the base "Room" model by introducing two specialized Room Types: Category Rooms (Floors) and Workflow Rooms. This maintains UI simplicity while providing structural hierarchy and local process automation.

Category Room ("Floor")
Purpose: Acts as a organizational container (similar to a folder) to bundle related sub-rooms under a single context.

Key Features:

Nested Hierarchy: Displays a preview stack or list of contained sub-rooms directly on the card.
Unified Settings: Allows applying global settings, shared context, or system prompts across all sub-rooms within the floor.
Item Count Indicator: Shows total active sub-rooms inside (e.g., "contains 3 rooms").

Workflow Room ("Local Automation")
Purpose: Enables node-based automation within a localized scope (inspired by n8n architecture).

Key Features:

Visual Canvas: Built-in node editor connecting Triggers → Data Transformations → AI Actions → Outputs.
Local Execution Scope: Runs within the user's environment/session without requiring external webhook configurations.
Status Controls: Direct toggle switch (ACTIVE / STANDBY) and inline execution preview on the main dashboard card.

UI/UX Changes
Dashboard Grid Update:

Standard Rooms, Category Rooms, and Workflow Rooms coexist side-by-side in the main grid layout using visual distinction (folder shapes for Floors, node icons for Workflows).

Start by locating the base Room model and the main dashboard grid, then determine how room types and local execution are currently represented. Define the scope for Category Rooms and Workflow Rooms, including hierarchy, shared settings, node execution, status controls, and visual distinctions; done requires both types to coexist in the dashboard with their described behavior.

Written by the indexing model from the issue text.