Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/app/e2e/inputs/select-review-filter.spec.ts`:
- Around line 16-18: Replace the brittle ID selector used in
page.locator("#right-panel") with a semantic or data-* locator: locate the panel
using a role (e.g., getByRole('region' / 'complementary' with an accessible
name) or a stable data attribute like data-component="right-panel"), then reuse
that locator for tabList and reviewTab (symbols: rightPanel, tabList, reviewTab)
so tests target a resilient semantic/data selector instead of the CSS ID.

In `@packages/app/e2e/inputs/text-field-ghost-inline-rename.spec.ts`:
- Around line 1-39: Update the test to target the dialog-based rename flow
instead of a sidebar-scoped ghost input: change the file header comment to
reflect that the rename uses DialogRenameSession (dialog-based) rather than a
ghost TextField, replace the locator that scopes the input to
sidebar.locator(`[data-session-id="${session.id}"] ${inlineInputSelector}`) with
a dialog-scoped lookup such as page.getByRole("dialog") to find the TextField
(since inlineInputSelector — `[data-component="input"][data-variant="ghost"]`)
no longer applies), and assert/operate on the dialog's input element (the
TextField without the ghost variant) so the locator resolves correctly.

In `@packages/app/src/i18n/en.ts`:
- Around line 1103-1104: The i18n key "session.rename.hint" is defined but not
used; update dialog-rename-session.tsx to wire it into the TextField (use
placeholder={language.t("session.rename.hint")} or equivalent) so the hint
appears, referencing the TextField component and language.t call, or remove the
unused key from en.ts/zh.ts if you prefer to delete dead i18n state.

In `@packages/ui/src/components/select.test.tsx`:
- Around line 93-100: The test "item selected state uses
--surface-interactive-base and --font-weight-medium" is falsely asserting that
--font-weight-medium appears inside the 200-char slice anchored at
"[data-selected]" even though the font-weight declaration lives in the parent
selector [data-slot="select-select-item"] which appears earlier; fix by either
removing the --font-weight-medium assertion from this test (since it's already
covered at the item-block level) or change the slice anchor to locate the parent
selector ([data-slot="select-select-item"]) and then assert that the slice
contains --font-weight-medium, keeping the existing checks for
--surface-interactive-base and [data-selected] intact.
- Around line 63-66: Add the missing CSS rule for the review-filter variant in
select.css: create a selector for [data-trigger-style="review-filter"] and
include the expected properties asserted by the tests (height: 24px, appropriate
border-radius value, expected font-weight, and background: transparent) so the
tests in components/select.test.tsx that look for
'[data-trigger-style="review-filter"]' and assert those properties pass; keep
naming and specificity consistent with the other trigger-style variants already
in select.css.

In `@packages/ui/src/components/switch.test.tsx`:
- Around line 89-91: The test named "checked thumb translate is 14px (28 - 12 -
1 - 1)" is asserting translateX(14px) but the correct value in switch.css is
translateX(12px); update the test assertion in that test (the
expect(css).toContain(...) call) to expect "translateX(12px)" and also update
the test description to reflect the correct calculation (28 - 2px borders - 1px
padding-left - 1px padding-right - 12px thumb = 12px) so the assertion and
message match the stylesheet.

In `@packages/ui/src/components/text-field.css`:
- Around line 137-176: The ghost variant ([data-variant="ghost"] with
[data-slot="input-wrapper"] and [data-slot="input-input"]) currently uses
padding: 10px 12px which makes it ~32–34px tall and can expand/clip the sidebar
inline editor row from inline-editor.tsx/SessionItem; update the styles to
either reduce vertical padding (e.g., 6–8px top/bottom) so it fits ~28px rows or
add a second modifier/class (e.g., [data-ghost="compact"] or .inline-editor) and
apply tighter vertical padding only for that modifier, then verify inline
rename/message-editing rows visually in the sidebar and that the search-bar
still looks acceptable.

---

Outside diff comments:
In `@packages/ui/src/components/select.css`:
- Around line 97-99: The select content container currently uses the wrong
variable; update the CSS rule that styles the select content block (the selector
referencing select-content / [data-component="select-content"]) to use
background-color: var(--surface-base) instead of var(--surface-raised) and
ensure no direct background-color: var(--surface-raised) remains on that
container so the select.test.tsx assertions (lines checking --surface-base and
absence of --surface-raised) pass.
- Around line 172-202: Add CSS rules for the missing review-filter variant:
create a [data-component="select"][data-trigger-style="review-filter"] block
(set height: 24px; border-radius: var(--radius-sm); background: transparent;
font-weight: var(--font-weight-regular); and any other token-based properties
the tests expect) and a corresponding
[data-component="select-content"][data-trigger-style="review-filter"] block
(match content sizing/padding/any variables asserted by select.test.tsx). Ensure
the exact attribute selectors used by select.tsx
(data-trigger-style="review-filter") are present so the tests can find those
rules.

In `@packages/ui/src/components/text-field.tsx`:
- Around line 82-115: The error icon visibility is currently tied to local.error
while the component derives validationState via the validationState() helper,
causing mismatches when a caller overrides validationState; update the Show that
renders the error icon to check the derived validationState() (e.g.,
validationState() === "invalid" or truthy invalid-state check) instead of
local.error so the icon and Kobalte validationState prop stay in sync; locate
the validationState const and the <Show when={local.error}> block in
text-field.tsx (around the Kobalte render) and change the condition to use
validationState(), keeping the data-slot="input-error-icon" attribute unchanged
so existing tests still find that element.

---

Nitpick comments:
In `@packages/app/e2e/inputs/select-review-filter.spec.ts`:
- Around line 37-57: The test defines a constant named patch in
select-review-filter.spec.ts but violates the test constant naming convention;
rename the variable to SCREAMING_SNAKE_CASE (e.g., PATCH or REVIEW_FILTER_PATCH)
and update all usages (references in the llm.toolMatch call, the JSON input
passed to project.sdk.session.prompt, and any other places) to the new name so
the test uses a properly cased constant.

In `@packages/app/e2e/inputs/todo-toggle.spec.ts`:
- Around line 7-14: The spec currently imports Playwright's Page type from
"@playwright/test" (symbol Page); update the file to use the project test
fixtures instead by removing the direct "@playwright/test" import and sourcing
Playwright utilities/types from "../fixtures" (or simply rely on the inferred
parameter types provided to test functions) so the spec uses the same
fixture-provided test/expect types as the rest of the suite; ensure any
references to the Page type are updated to the fixture-provided type or omitted
to match the harness conventions.

In `@packages/app/src/pages/layout/inline-editor.tsx`:
- Around line 87-91: The TextField usage passes label="" and hideLabel which is
redundant; remove the hideLabel prop from the TextField invocation in
inline-editor (keep label="" or omit label prop if you prefer the Show gate) so
the component relies on the existing <Show when={local.label}> behavior; locate
the TextField JSX (the ref callback block) and delete the hideLabel attribute to
clean up the props.

In `@packages/ui/src/components/inputs-state-matrix.test.tsx`:
- Around line 96-100: The test "error/invalid: error prop sets validationState
to 'invalid'" is brittle because expect(textFieldSrc).toContain("local.error ?
\"invalid\"") depends on exact whitespace; change the assertion to use a
whitespace-tolerant regex match against textFieldSrc (e.g., use toMatch with a
pattern like /local\.error\s*\?\s*["']invalid["']/) so the derived accessor
check still verifies the conditional but won't break on formatter/whitespace
changes; update the assertion that currently references textFieldSrc and the
literal "local.error ? \"invalid\"" accordingly.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/ui/src/components/inputs-state-matrix.test.tsx`:
- Around line 144-152: The "checked: Kobalte manages aria-checked via
checked/defaultChecked prop" test uses splitMatch =
switchSrc.match(/splitProps\(props,\s*\[([^\]]+)\]/) and then accesses
splitMatch![1] without a null guard; add the same defensive assertion used in
the "disabled" test by asserting splitMatch is not null (e.g.,
expect(splitMatch).not.toBeNull()) before accessing splitMatch[1], so the regex
failure yields a clear test assertion rather than a TypeError.

In `@packages/ui/src/components/switch.css`:
- Around line 88-109: The active state selector is too specific and overrides
the checked track color; add a checked-specific active selector to preserve
brand styling when pressed by adding a rule targeting
&[data-checked]:active:not([data-disabled],[data-readonly])
[data-slot="switch-control"] that sets background-color and border-color to the
brand-active values (mirroring the checked hover rule) so the checked track
keeps --brand-primary (or its hover/active variant) during pointer-down; update
CSS around the existing &[data-checked] [data-slot="switch-control"] and
&:active... [data-slot="switch-control"] rules to include this new selector.

---

Nitpick comments:
In `@packages/ui/src/components/toast.css`:
- Around line 88-97: The &:first-child color override is redundant because child
icons/buttons already use color: inherit (see [data-slot="toast-icon"] and its
[data-component="icon"] and the base [data-slot="toast-action"] rule); remove
the redundant &:first-child { color: inherit; } block from the toast action
rules so the stylesheet is cleaner and behavior unchanged.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@packages/ui/src/components/select.css`:
- Around line 49-58: Remove the redundant CSS block nested under the settings
variant that targets [data-slot="select-select-trigger-icon"]; since it is now
byte-for-byte identical to the base [data-slot="select-select-trigger-icon"]
declarations (and is inherited via the [data-component="select"] wrapper),
delete the duplicate block to avoid unnecessary duplication and future
drift—locate the nested rule inside the settings variant and remove it, leaving
only the base selector's declarations.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/app/e2e/inputs/select-review-filter.spec.ts`:
- Around line 34-35: Remove the redundant project.trackSession(session.id) call
inside the withSession callback: since withSession manages the session lifecycle
and calls cleanupSession, delete the project.trackSession invocation (in the
withSession callback in select-review-filter.spec.ts) so sessions created by
withSession are not double-tracked; use project.trackSession only for resources
created outside the fixture.

In `@packages/ui/src/components/inputs-state-matrix.test.tsx`:
- Line 32: The test loads text-field.css into the variable textFieldCss but
never uses it; either remove that unused readFileSync call or add assertions in
the describe("state-matrix: TextField") block to verify the CSS contracts.
Specifically, if keeping it, add at least one selector check that uses
textFieldCss (similar to switchCss/selectCss tests) to assert expected selectors
like [data-invalid], ghost/inline variants, or the error ring are present;
otherwise delete the textFieldCss declaration to remove dead code. Locate
textFieldCss and the describe("state-matrix: TextField") block to implement the
change.

---

Nitpick comments:
In `@packages/ui/src/components/inputs-state-matrix.test.tsx`:
- Around line 55-57: The test currently asserts pickerCss contains
"[data-picker-item]" and "[data-selected]" separately which doesn't guarantee
the combined rule exists; update the assertion to check for the exact combined
selector used in the stylesheet (e.g.,
"[data-picker-item]:where([data-selected])") by replacing the two separate
expects with a single expect on pickerCss for that combined selector (keep the
"--row-active-overlay" assertion as-is if still required) so the test enforces
the actual rule interaction produced by the picker CSS.