feat(dashboard): make TUI editor tabs switch between projects

[duyet]

The landing terminal editor tabs are projects (conversations, leases, mcp, analytics). Clicking a tab swaps that project’s snippet, status, and inline diagnostic.

Each pane keeps the editor warning chip (e.g. ▲ 'autosave' is deprecated · F8 on conversations). Leftover IDE chrome stays gone: no fake file tree, git badges, Keys/Logs, or F1/Ctrl+K command bar.

Test

cd packages/dashboard && bun test src/lib/preset-stack.test.ts

  

Summary by Sourcery

Enable project-based switching in the landing-page TUI editor while simplifying its presentation to focus on project snippets and diagnostics.

New Features:

• Make the landing-page TUI editor tabs switch between conversations, leases, MCP, and analytics projects, each with its own code snippet, status, and diagnostic.

Enhancements:

• Remove leftover IDE-style file navigation and command-bar chrome from the editor mockup.
• Use syntax-highlighted project examples and preserve accessible keyboard-focusable tab controls.

Tests:

• Add coverage verifying project-based switchable tabs and the removal of obsolete IDE UI.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 41c4bdf4-2193-46ae-aaf8-16355cdbe810

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Sorry @duyet, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[sourcery-ai]

Reviewer's Guide

Refactors the landing TUI editor so its tabs represent switchable AgentState projects rather than static files, using radio inputs and CSS-only tab panels, and adds tests to assert the new project-based behavior and markup.

File-Level Changes

Change	Details	Files
Landing TUI editor tabs now switch between project-specific explorers, code snippets, and status bars using radios + CSS-only panels.	Replace static file-tab header with a dynamic tab bar rendered from a projects array and backed by radio inputs in a named group. Introduce Project and TreeRow interfaces plus a projects array containing per-project file trees, stats, and code snippets. Use highlightCode to render syntax-highlighted HTML for each project’s code snippet, including use of MCP_URL and API_BASE_URL for example snippets. Render a panel per project showing its explorer tree, highlighted code, and status bar, and wire visibility via :has() CSS selectors tied to radio values. Add CSS styles for visually-hidden radio inputs, tab hover/active states, focus outlines, and conditional display of panels and normalized code block styling.	packages/dashboard/src/components/home/tui-editor.astro
Add a preset-stack test ensuring the TUI editor uses project-based radio tabs and no longer exposes the old static file markup or img role.	Extend the terminal TUI stack test suite with a case that reads the TUI editor template and asserts presence of radio inputs and project tab data attributes. Verify that project names (conversations, leases, mcp, analytics) are present while old *.ts filenames and role="img" attributes are absent.	packages/dashboard/src/lib/preset-stack.test.ts

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

New security issues found

[sourcery-ai]

security (curl-auth-header): Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

Source: betterleaks

[sourcery-ai]

security (curl-auth-header): Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.

Source: betterleaks