7 Commits

Include renames

Author	SHA1	Message	Date
Clintchiz	2c960fc1dc	refactor: migrate legacy wire namespace to wrn	2026-08-12 18:51:15 +05:30
Clintchiz	b1086d14e9	fix(auth): secure hydration and align password forms	2026-08-11 17:05:04 +05:30
ClintchizandClaude Opus 5	c7ab605e85	feat(ui): migrate the page and section components, add the layout tour ... Section, SectionHeader and PublicPageShell move onto wire-* classes with local style blocks, variants as data attributes. SectionHeader loses 38 utility lines, and Section stops spending one line per variant and colour pairing: tinted and solid now select on two attributes. PageHeader was already on the convention and only needed the audit. examples/basic-app/app/pages/layout.wrn composes the whole set into one page. Building it surfaced a library-wide bug. Ten custom properties were referenced by components and defined by nothing: --wire-color-focus, --wire-color-surface-soft, --wire-color-on-danger, --wire-color-surface-subtle and the input-* family, plus hover and contrast for every semantic colour except primary and secondary. An undefined custom property does not warn, it resolves to nothing, so focus rings drew with no colour and every soft surface rendered transparent -- 27 components referenced surface-soft alone. They are derived in the theme now, and a test checks every token a component references against the rendered theme CSS rather than the source, since most are generated. The semantic spread also had to move ahead of the primary and secondary entries so the palette keeps winning for those two. Known and unresolved: LayoutSplitter emits its sizeChange output and the component does fire it, but a parent binding on the tag is not invoked. The tour page therefore points at the handle aria-valuenow rather than wiring a handler that would never update. Outputs work elsewhere, so this is narrower than an outputs-are-broken problem and needs its own investigation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-08 15:50:33 +05:30
ClintchizandClaude Opus 5	7bd4574b08	fix(example): theme the basic-app palette and surface the navigation tour ... global.css defined its own fixed palette -- bg 0b1020, text e7ecff -- while Wire UI surfaces follow the theme tokens. Switching to light turned the cards light and left this text light with them, so the sign-in form rendered at a contrast of about 1.1 and could not be read. The palette now derives from the wire tokens, and the body wash is tinted from the primary token rather than a fixed blue. Measured on the login form: light goes from 1.1 to 17.7, dark stays at 18.2. Anything an application hardcodes has to be themed as well, or it only ever looks right in one mode. The navigation tour is also reachable now: a Navigation entry in the site nav, translated in both locales, and the page adopts the public layout so there is a way back out of it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-08 10:19:12 +05:30
Clintchiz	586a6db8ff	release: WRNexusJS 0.8.0	2026-08-02 23:18:51 +05:30
Clintchiz	3e565e8d03	Pre Release New Changes	2026-07-31 16:30:13 +05:30
Clintchiz	ee98026cc5	first commit	2026-07-12 15:55:18 +05:30