I think we could just make this test check the order of whatever the items are. Otherwise someone in the future is likely to run CI and realize this test failed and then have to add another item to this list in the test.

Good call — updated to just assert that whatever items are rendered come out alphabetically, no hardcoded list.

Nit [CRF-1] AGENTS.md says: "Do not create standalone vitest/RTL test files for components or pages. Stories double as living documentation, visual regression coverage, and interaction test suites via play functions. Reserve plain vitest files for pure logic only." This test renders the Sidebar component and asserts on DOM output, which is component testing.

The directory already has 6+ vitest/RTL .test.tsx files for other pages, so this follows local precedent while violating the documented rule. If the test becomes a story, the withDashboardProvider decorator already supports features and experiments through story parameters, and the 28 lines of boilerplate collapse into a decorator and a parameters block.

(Netero, Mafu-san)

🤖

Good catch — moved the assertion into the new Sidebar.stories.tsx play function and deleted Sidebar.test.tsx. The boilerplate collapses to the withDashboardProvider decorator with features/experiments parameters as suggested. Also gets us Chromatic visual coverage.

Nit [CRF-2] [...expectedOrder].sort(...) is the manual version of expectedOrder.toSorted(...). The project targets esnext, and toSorted is already used in 5 places across the codebase (e.g. userSkills.ts, chats.ts, TaskPrompt.tsx). The stdlib version communicates intent more clearly and avoids the intermediate spread.

expect(navItems).toEqual(
  expectedOrder.toSorted((a, b) => a.localeCompare(b)),
);

(Ging-ts)

🤖

Switched to toSorted in the play function.

Note [CRF-3] The dashboardValue object and Wrapper component duplicate the same pattern from ChatsSidebar.test.tsx:77-106 (same mocks, same provider chain). This is the second copy. A third would make extracting a shared renderWithDashboard helper worthwhile.

(Robin)

🤖

Acknowledged. The unit test got replaced with a story play function, so the duplicated wrapper is gone for this PR. Agree that a shared renderWithDashboard helper would be worth extracting if a third copy of the pattern shows up.