zenit-ui 0.2.3

Added

• Responsive game covers. button[zGameTile] and a[zGameTile] take three optional inputs. coverSrcset is passed through as srcset, coverSizes as sizes; with a srcset and no sizes the library sets "(max-width: 639px) 50vw, 272px", the widest a cell of z-game-grid gets. coverLoading ('lazy' | 'eager', default 'lazy') lets the first visible tiles load at once. cover stays the src and the fallback; a failing srcset candidate ends in the same text fallback and (coverError).

Changed

• Cover images load lazily. The <img> of a game tile now always carries loading="lazy" (or the value of coverLoading) and decoding="async". Without the new inputs this is the only change to the markup of 0.2.2; classes, skeleton and accessibility stay as they were. Tiles visible on first paint should get coverLoading="eager".

zenit-ui 0.2.2

Changed

• MIT license. The package was published as UNLICENSED, which gave nobody the right to use it. It is now "license": "MIT", with LICENSE at the repository root and in the package (projects/zenit-ui/LICENSE, shipped by ng-packagr). The name Zenit-Hosting and its logo are not covered; the new section "License" in the package README says so and names the licenses of the fonts an application self-hosts (SIL OFL 1.1, Apache 2.0). CONTRIBUTING.md states that contributions come under the same license. tools/check-pack.mjs now fails when the manifest does not declare MIT or when LICENSE is missing from the tarball or differs from the root file.

zenit-ui 0.2.1

Added

• Tooling for Claude Code. Subagents in .claude/agents/ (explorer, architect, component-builder, designer, test-writer, build-fixer, api-guardian, code-reviewer, docs-writer, escalation) with the rules of CONTRIBUTING.md, the skill /feature for their order, and the Angular CLI MCP server (.mcp.json, tools/angular-mcp.mjs). npm run design:shot -- <route> (tools/design-shot.mjs) renders demo pages at any width and colour scheme to tmp/design/, with axe, an overflow check and focus and hover close-ups. npm run check:agents (tools/check-agents.mjs) validates the frontmatter, models, tools and paths of the agents and skills and is the first step of npm run check. Hooks format written files with Prettier and, in cloud sessions, run npm ci; tools/cloud-setup.sh installs Node 24 there. Nothing in the published package changes.

Changed

• A release is a merge. .github/workflows/publish.yml also runs on a push to main that changes the version in projects/zenit-ui/package.json: it publishes that version, then creates the tag v<version> and a GitHub release whose text is the version's section of this file (tools/release-notes.mjs). A push whose version is already on npm does nothing (RELEASE_AUTO=1 in tools/check-release.mjs, which now also fails a version without a CHANGELOG section). npm run release:vorbereiten -- patch|minor|major|<version> (tools/release-prepare.mjs) raises the version and turns [Unreleased] into the dated section. Documented in docs/veroeffentlichen.md.
• Documentation matches the npm release. The package README, the root README, CONTRIBUTING.md, docs/ng-add.md, docs/migration-from-material.md, docs/theming.md, docs/llms.md, the example app README and the setup step of llms.txt/llms-full.txt install @zenit-hosting/zenit-ui from npmjs.org under the alias zenit-ui (npm install zenit-ui@npm:@zenit-hosting/zenit-ui@^0.2.0) and run the setup with ng generate zenit-ui:ng-add instead of ng add; a local tarball is only the way to try an unreleased build, installed under the same alias. The release sections describe the merge-to-publish flow with npm run release:vorbereiten, docs/veroeffentlichen.md marks the GitLab pipeline as the alternative and states that the package ships its source map with the TypeScript sources, and the contrast gate figures read 3 schemes × 8 accents, 1776 pairs. The page "Einbindung" of beispiel-app shows the aliased install and ng generate zenit-ui:ng-add instead of ng add zenit-ui and a tarball (its e2e:beispiel baselines need re-recording), and tools/check-pack.mjs and tools/check-release.mjs default to @zenit-hosting/zenit-ui; the GitLab CI keeps setting @hosting/zenit-ui itself.

v0.2.0: feat(theme): Akzente indigo, orange und rose; Version 0.2.0

Damit hat jede Akzentfarbe, die ein Zenit-Konto wählen kann, eine Entsprechung
in der Library, und das Frontend kann die Wahl als data-accent durchreichen.
orange nimmt im hellen Schema ein tieferes accent-text (#7c2d12), sonst lag es
1,20:1 neben --danger. theme.spec nutzte orange als unbekannte Id und nimmt
jetzt gelb. check:themes: 1776 Paare über 24 Kombinationen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JwP4ACEK9yZvjztkA51w3Z

v0.1.0

Merge ui/ci-culture: deutsches Regionalformat in der CI, Tag ohne v