feat(webapp): storybook gallery for the dashboard agent - #4516
feat(webapp): storybook gallery for the dashboard agent#4516kathiekiwi wants to merge 4 commits into
Conversation
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughAdded client-safe dashboard-agent demo fixtures for identifiers, charts, view blocks, investigations, intents, watches, and messages. Added reusable chart and intent components. Replaced the diagnosis-only Storybook route with a gallery framework and routes for agent UI, view blocks, reports, investigations, and watches. Added toast examples, gallery navigation, theme controls, validation tests, and a Playwright screenshot utility with optional chat capture support. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
The gallery pages for the agent chat, view blocks, report, investigation and watch cards, the demo fixtures behind them, and the screenshot script. This reverts commit bbdcb0881, which held these back out of the parent PR.
bfe64cc to
1b6dfb1
Compare
| { | ||
| sectionTitle: "Dashboard agent", | ||
| name: "Agent UI", | ||
| sectionTitle: "Trigger Agent", | ||
| name: "Chat UI", | ||
| slug: "agent-ui", | ||
| }, | ||
| { | ||
| name: "View blocks", | ||
| slug: "agent-view-blocks", | ||
| }, | ||
| { | ||
| name: "Report view", | ||
| slug: "agent-report", | ||
| }, | ||
| { | ||
| name: "Investigation card", | ||
| slug: "agent-investigation", | ||
| }, | ||
| { | ||
| name: "Watch card", | ||
| slug: "agent-watch", | ||
| }, | ||
| { | ||
| name: "Icons & Buttons", | ||
| slug: "ai-agent", | ||
| }, |
There was a problem hiding this comment.
🟡 Release-notes entry missing for a webapp-only change
This pull request changes only files under apps/webapp/ (see apps/webapp/app/routes/storybook/route.tsx:163) without adding the required release-note file, so the change will not appear anywhere in the published notes.
Impact: The change ships undocumented, and the repository's contribution checklist is not satisfied.
Where the rule comes from and how to satisfy it
AGENTS.md and CONTRIBUTING.md both state: "When modifying only server components (apps/webapp/, apps/supervisor/, etc.) with no package changes, add a .server-changes/ file instead" of a changeset. The full diff touches only apps/webapp/** (new storybook.agent-* routes, the dashboard-agent/demo fixtures and the toast story) and no files under packages/ or integrations/, and git diff --name-only against the merge base shows no new file under .server-changes/. The fix is to add a markdown file to .server-changes/ with area: webapp and type: feature/improvement frontmatter plus a one-line, user-facing description, per .server-changes/README.md.
Prompt for agents
This PR modifies only apps/webapp (new storybook gallery routes, dashboard-agent demo fixtures, toast story) and contains no changes under packages/ or integrations/. AGENTS.md and CONTRIBUTING.md require that server-only PRs add a file under .server-changes/ so the change lands in the user-visible release notes; no such file exists in this branch. Add a `.server-changes/<descriptive-name>.md` with frontmatter `area: webapp` and an appropriate `type`, and a single plain sentence describing the change for users (see .server-changes/README.md for the writing guidance).
Was this helpful? React with 👍 or 👎 to provide feedback.
Split out of #4418 so that PR carries only what ships to users.
Adds the agent gallery: five
storybook.agent-*pages (chat UI, view blocks, report, investigation, watch) with their shared shell and manifest, the demo fixtures and two demo-only cards that feed them, the agent toast examples, and the screenshot script.