Task 2 code-quality review (subagent verdict: Ready to merge? No) found
two critical correctness bugs in the original CSS template from spec §3.2:
1. Vuetify's outlined variant collapses sub-element opacity through
--v-field-border-opacity (= 0.38 at idle). Without explicit opacity:1
on each override block, --liderra-line (alpha 0.08) effective alpha
becomes 0.03 → border essentially invisible on ivory backgrounds.
2. Overriding border-color with an explicit value breaks the
currentColor inheritance Vuetify uses for the error state
(color: rgb(var(--v-theme-error)) on .v-field--error.v-field__outline).
Without an explicit error rule that restores currentColor, the red
error border never appears on any of the 5 validated fields.
Also tightened hover from .ld-input-quiet:hover (which is on the .v-input
root, including hint/error message area) to .v-field:hover inside
:deep() — matches Vuetify's own hover scope and avoids triggering on
helper text hover.
Spec §3.2 and plan Task 2.2 updated to the corrected CSS block with
explicit «almost-trap-avoidance» notes documenting why each adjustment
is needed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Дмитрий
ab47ad250b