feat(ui): new layout

[rafavalls]

What is this contribution about?

Describe your changes and why they're needed.

Screenshots/Demonstration

Add screenshots or a Loom video if your changes affect the UI.

How to Test

Provide step-by-step instructions for reviewers to test your changes:

1. Step one
2. Step two
3. Expected outcome

Migration Notes

If this PR requires database migrations, configuration changes, or other setup steps, document them here. Remove this section if not applicable.

Review Checklist

• PR title is clear and descriptive
• Changes are tested and working
• Documentation is updated (if needed)
• No breaking changes

---

Summary by cubic

Rebuilt Settings, Connections, Members, Monitoring, Automations, and Virtual MCP with a consistent Page layout. Added a Profile & Preferences page, shared @deco/ui SearchInput, and polished buttons and tables.

• New Features

  • Profile & Preferences: theme (light/dark/system), notifications, global and per-event sound toggles with test sounds, and tool approval level.
  • New Page.Title and Page.Body building blocks; shared @deco/ui SearchInput across org and settings pages.
  • UI polish in @deco/ui: smaller default buttons with new icon-sm; Table now rounded and bordered.

• Bug Fixes

  • Prevent blank profile name saves by deferring editable state until the session loads.
  • Org slug edits now validate and set touched state on change.
  • Status sounds: SOUND_MAP intentionally omits in_progress (no sound); map is Partial and previews guard missing sounds.
  • Chat input always renders a border to avoid layout shift when toggling plan mode.

^{Written for commit 9dea632. Summary will update on new commits.}

[github-actions]

🧪 Benchmark

Should we run the Virtual MCP strategy benchmark for this PR?

React with 👍 to run the benchmark.

Reaction	Action
👍	Run quick benchmark (10 & 128 tools)

Benchmark will run on the next push after you react.

[github-actions]

Release Options

Suggested: Patch (2.214.2) — default (no conventional commit prefix detected)

React with an emoji to override the release type:

Reaction	Type	Next Version
👍	Prerelease	2.214.2-alpha.1
🎉	Patch	2.214.2
❤️	Minor	2.215.0
🚀	Major	3.0.0

Current version: 2.214.1

Note: If multiple reactions exist, the smallest bump wins. If no reactions, the suggested bump is used (default: patch).

[cubic-dev-ai]

2 issues found across 23 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/mesh/src/web/views/settings/profile-preferences.tsx">

<violation number="1" location="apps/mesh/src/web/views/settings/profile-preferences.tsx:85">
P2: `name` is initialized before the session resolves, so once the user data arrives the input stays empty and `isDirty` becomes true, allowing an accidental save of a blank name. Defer the editable state until the user data is available (e.g., track an "uninitialized" state and derive the displayed value from `user?.name` until the user edits).</violation>
</file>

<file name="apps/mesh/src/web/components/settings/organization-form.tsx">

<violation number="1" location="apps/mesh/src/web/components/settings/organization-form.tsx:174">
P2: The custom `onChange` replaces React Hook Form’s registered handler, so field re-validation/touched updates won’t run. Use `setValue` with `shouldValidate`/`shouldTouch` (or call the registered onChange) so errors clear as the user edits the slug.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/mesh/src/web/hooks/use-status-sounds.ts">

<violation number="1" location="apps/mesh/src/web/hooks/use-status-sounds.ts:10">
P2: Avoid `Partial<Record<SoundEventKey, ...>>` here; it removes exhaustiveness checks and can silently drop sounds for valid event keys.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: Avoid Partial<Record<SoundEventKey, ...>> here; it removes exhaustiveness checks and can silently drop sounds for valid event keys.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/mesh/src/web/hooks/use-status-sounds.ts, line 10:

<comment>Avoid `Partial<Record<SoundEventKey, ...>>` here; it removes exhaustiveness checks and can silently drop sounds for valid event keys.</comment>

<file context>
@@ -7,7 +7,7 @@ import { clickSoftSound } from "@deco/ui/lib/click-soft.ts";
 import { usePreferences, type SoundEventKey } from "./use-preferences";
 
-export const SOUND_MAP: Record<SoundEventKey, { dataUri: string }> = {
+export const SOUND_MAP: Partial<Record<SoundEventKey, { dataUri: string }>> = {
   completed: successChimeSound,
   failed: error005Sound,
</file context>

[tlgimenes]

Partial is intentional here. in_progress is a valid SoundEventKey (users can toggle it in preferences) but it deliberately has no associated sound — the comment on line 9 documents this. Removing Partial would force a dummy/null entry for in_progress, which is less clean than the current approach where if (sound) on line 23 (and line 269 in profile-preferences) handles missing entries gracefully.

Exhaustiveness is not needed: if a new key is added to SoundEventKey, the default behavior of "no sound" is the safe default until a sound asset is explicitly assigned.

[cubic-dev-ai]

Thanks for the feedback! I've saved this as a new learning to improve future reviews.