j3w1 1.1.0 — True Black / Rose and themed controls

The j3w1 design-system portal, Vue demo and reusable package now use themed single/multiple choices, a date calendar, time editor and step buttons, and shared checkbox/radio/range/file-button styling. Command search fills its dialog below the label. This addresses the native blue selection and cramped search field reported during the preview.

True Black / Rose remains permanent, with red graphs and underlined red links, near-white titles, rose headings and distinct table-header/body colors. All 67 inventory entries have modular implementations, typed APIs, complete copy bundles and pinned contracts. The Vue 3 JavaScript demo has 31 destinations using resettable synthetic data.

• Design-system portal
• Vue demo
• Complete UI theme specification
• Agent entry and task-kit picker
• Pinned consumption documentation

Download j3w1-ui-1.1.0.tgz, verify it against release.json, then install it and prepare a Vue copy kit:

npm install --save-exact ./j3w1-ui-1.1.0.tgz
npx --no-install j3w1-ui kit --components text-field,button,dialog --mode copy --framework vue --out ./j3w1-kit

The public enhanceControls(root) API lets existing applications use the same rendering. Original controls retain form data, defaults, events and reset. The documentation covers lifecycle, keyboard interaction, date/time fallback constraints, explicit enhancement roots and complete copy dependencies. No-JavaScript fallback and browser-owned system dialogs retain host behavior.

The delivery workflow passed source validation, generated-artifact checks, 110 source tests, build, 12 distribution tests, 63 packed-consumer checks across Chromium/Firefox/WebKit, 234 specification browser checks (134 scoped skips), and verification-report gates. Public readback matched 606 files to the tested artifact. The live browser report exercises the palette, search layout, themed agent-kit choices, Kanban focus, all Vue destinations at desktop/narrow/zoom widths, record validation/save/reset and no-JavaScript documentation.

The attached isolated settings application was authored through the installed public copy CLI and exercised against the same archive. Evidence records retain their actual environments and limits. This is automated implementation evidence, with no manual screen-reader, physical-device or independent acceptance claim. Windows-local Firefox context teardown and the large reference settings test exceeded their existing time limits; those runs are not presented as passes. The attached complete reports come from the successful Linux CI run.

The npm registry package has not been published; registry publication remains an owner release action. The archive is directly consumable. The existing v1.0.0 tag remains immutable; v1.1.0 identifies this additive control correction. delivery-provenance.json binds the release to revision 7d1389e, its CI run and artifact digests.