go
/
svelte-kit-vice
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '72e8fb57ea'
${ noResults }
svelte-kit-vice/audit/components/time-range-field.md

36 lines
3.1 KiB
Raw Normal View History Unescape

docs(audit): deep component audit — 124/124 audited + executable fix plan Stateful deep audit of the whole UIX component system across 8 batches (words/palabras/chronos excluded). Read-only: zero code changes. Result: 0 CRITICAL · 18 HIGH · 129 MEDIUM · 60 LOW. Deliverables (audit/): - components/{kebab}.md one machine-reparseable report per component - 00_WORKLIST.md resumable index (all audited) - SUMMARY.md verdict + systemic findings + per-batch counts - THEMING_COHERENCE.md E-bis coherence roll-up (roles/sizes/variants clean) - SHARED_EXTRACTION.md extraction opportunities (EX-3 selectedSet highest value) - VALIDATOR_GAPS.md 12 proposed validator extensions (prevent the class) - FIX_PLAN.md prioritized, executable fix roadmap (Phase 1 = SYS-7) Method: per-batch adversarial workflow (analyze -> skeptical verify), with every HIGH/CRITICAL lead-verified against the cited source + independent greps. The verify stage refuted false positives in both directions (eidos->soma, CSS.escape on framework values, inert archetype metadata, content-color slots mistaken for non-canonical roles). Top systemic finding: SYS-7 — A31 O(N^2) per-item .includes selection across 9 components (6 HIGH), one ~3-line selectedSet/expandedSet lift each. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3 months ago
# Audit: time-range-field
audit-version: 1
audited-at: 2026-06-26
scope: (SCOPE-DRIFT → SYS-1)
method: adversarially-verified workflow (analyze → refute); HIGH/CRITICAL lead-verified. Clean-check pseudo-findings dropped. B4 ground-truth: segmented date/time/color-field register inputId via $effect (SYS-A30-EFFECT, no loop); number-field is the direct-assignment reference.
provider: G:\dev\svelte\vicen\src\uix\soma\components\time-range-field\time-range-field-provider.svelte.ts
## Summary
Counts (post-verification): CRITICAL 0 · HIGH 0 · MEDIUM 1 · LOW 0.
## Findings
### MEDIUM: SYS-1: scope-drift — eidos recipe dir exists but morfo 'scope' omits 'eidos' — time-range-field-001 <!-- id: time-range-field-001 -->
- dimension: A Contract
- rule: SYS-1: scope-drift — eidos recipe dir exists but morfo 'scope' omits 'eidos'
- location: src/uix/morfo/components/time-range-field.ts:7
- evidence: Morfo declares `scope: ['soma']` but directory src/uix/eidos/components/time-range-field/ exists with time-range-field.svelte, types.ts, time-range-field.css, time-range-field-input.svelte, time-range-field-label.svelte.
- impact: Contract validator will not enforce eidos presence rules; consumers may ignore eidos-layer variants/size/color constraints.
- proposed-fix: Add 'eidos' to morfo scope: `scope: ['soma', 'eidos']`
- verify: [confirmed] CONFIRMED. src/uix/morfo/components/time-range-field.ts:7 reads `scope: ['soma'],` — 'eidos' is absent. The eidos directory src/uix/eidos/components/time-range-field/ genuinely exists with 6 files (time-range-field.svelte, time-range-field.css, types.ts, index.ts, time-range-field-input.svelte, time-range-field-label.svelte) per Glob. This is textbook SYS-1 scope-drift. The omission is real (not intentional): the sibling component using the IDENTICAL overlay trick — date-range-field, explicitly named in this recipe's header comment ('Same trick DateRangeField uses') — declares `scope: ['soma', 'eidos']` (src/uix/morfo/components/date-range-field.ts:10). So time-range-field's `['soma']` diverges from its own established sibling precedent. MEDIUM is correct per the SYS-1 baseline.
docs(audit): mark SYS-1 scope-drift fixed (212624e0) SYS-001 (SUMMARY) resolved + 46 per-component scope-drift findings set to fixed. The other drifted components annotate the drift in their report header (not a fix-status finding) or capture it only via the systemic SYS-001, so they have no per-component line to flip. scroll-area's data-overflow finding is a distinct undeclared-attr issue (not scope) and stays open. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3 months ago
- fix-status: fixed (212624e0)
docs(audit): deep component audit — 124/124 audited + executable fix plan Stateful deep audit of the whole UIX component system across 8 batches (words/palabras/chronos excluded). Read-only: zero code changes. Result: 0 CRITICAL · 18 HIGH · 129 MEDIUM · 60 LOW. Deliverables (audit/): - components/{kebab}.md one machine-reparseable report per component - 00_WORKLIST.md resumable index (all audited) - SUMMARY.md verdict + systemic findings + per-batch counts - THEMING_COHERENCE.md E-bis coherence roll-up (roles/sizes/variants clean) - SHARED_EXTRACTION.md extraction opportunities (EX-3 selectedSet highest value) - VALIDATOR_GAPS.md 12 proposed validator extensions (prevent the class) - FIX_PLAN.md prioritized, executable fix roadmap (Phase 1 = SYS-7) Method: per-batch adversarial workflow (analyze -> skeptical verify), with every HIGH/CRITICAL lead-verified against the cited source + independent greps. The verify stage refuted false positives in both directions (eidos->soma, CSS.escape on framework values, inert archetype metadata, content-color slots mistaken for non-canonical roles). Top systemic finding: SYS-7 — A31 O(N^2) per-item .includes selection across 9 components (6 HIGH), one ~3-line selectedSet/expandedSet lift each. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3 months ago
## No-findings dimensions
B Behavior, C DOM-selector, D Frontier, E-bis Theming (roles/aliases/spacing/radius/z-index/opacity naming), F Tests, G Redundancy
## Theming facts (E-bis)
- magic z-index: none
- magic literals: 0.9em (line 84 time-range-field.css) — separator font-size should be tokenized
- undeclared parts: none
- roles clean: true · variants clean: true
- label-font (one step below input?): CLEAN — label uses var(--time-field-label-font-size, var(--font-size-sm)) = 0.875rem (14px), input uses var(--_time-field-font-size) defaulting to var(--time-field-font-size-md) = var(--font-size-md) = 1rem (16px). One typographic step below.
## Tests (F)
- exists: true · env: jsdom
- covers: validation (endpoint ordering, min/max bounds, custom validation); label click focus behavior (first start segment); custom validation preference over built-in rules
- untested: readonly segment propagation (startReadonlySegments / endReadonlySegments behavior); readonly-without-value warning scenario

Powered by TurnKey Linux.