# V1 team handoff · accepted locally

The user accepted the V1 standard, reusable artifacts and adoption skill. All nine roadmap milestones are complete locally. The deliverables are prepared in this checkout. No application repository was migrated. The user subsequently authorized GitHub submission; see ROADMAP.md for that checkpoint. Site deployment and application adoption remain separate.

## Entry points

- [Integrated CSS reference](../examples/components/css.html) and [scoped Sass reference](../examples/components/sass.html).
- [Adoption guide](adoption.md) for assets, imports, build commands and current limits.
- [Team skill](../skills/kb-design-standard/SKILL.md), with [source conflicts](../skills/kb-design-standard/references/conflicts.md) and [verification checklist](../skills/kb-design-standard/references/verification.md).
- [Roadmap and run evidence](../ROADMAP.md).

Keep the skill in this checkout so its relative links resolve. A team's skill loader may point to skills/kb-design-standard/SKILL.md; when installing a copy elsewhere, provide an accessible KB checkout and resolve the linked source/documents there. The skill is guidance, not a runtime dependency or an automatic application migration. This run does not install or activate it globally.

## Reusable assets

For CSS consumers: theme.css, optional fields.css/actions.css/surfaces.css, optional fonts.css plus assets/fonts/noto-sans/ and assets/licenses/NotoSans-OFL.txt. Keep assets/licenses/lucide-LICENSE when distributing Lucide icons. Copy the actual SVG glyph markup from examples or use the consuming app's Lucide dependency; CSS does not supply glyphs. Runtime application code owns theme preferences, validation/state and modal lifecycle.

For Sass consumers: scss/ with its module structure; call the theme and optional component mixins. See examples/components/consumer.scss. Source imports alone emit nothing. Do not hand-edit generated CSS. The checked-in local font files are unmodified static normal faces; exact hashes and upstream URLs are in their provenance.json.

## Reproduce local checks

```sh
npm ci
npm run build:theme
npm run build:fields
npm run build:actions
npm run build:surfaces
npm run build:examples
npm run check:theme
npm run check:fields
npm run check:actions
npm run check:surfaces
npm run test:theme
npm run dev
```

Open examples/components/css.html or sass.html through the server. The server is a development tool; runtime generated CSS needs no Node/Sass dependency. Browser audit JSON files contain the verification evidence for this initiative; the one-off browser harness is not shipped as a supported CI suite. Teams should add checks appropriate to their applications.

## Known limits

The original company kb-standards-stylesheet.css remains unavailable. Wizard source is the accepted visual baseline, with explicit readable-text, optional-caret and semantic/lifecycle refinements documented by component. Chromium verification is not a claim of full browser or assistive-technology coverage. Restored subtle source borders/focus halos supersede earlier stronger-contour contrast claims; verify actual application backdrops and focus identification.

Current references can load their local fonts without external font requests; this does not make an application offline-ready. The rebuilt landing embeds current components; its expandable reference area retains historical content and extended patterns. Broader language/italic requirements, app-specific dirty-data policy, supported-browser testing and package/version/publication decisions belong to adoption. Reference repositories remain unchanged.