v2.3.1

Patch Changes

• #34 5faed09 Thanks @ryuhzk! - Support optional iconDirections metadata so one theme arrow can be rotated correctly for Home quick actions and the Gateway picker. Authors declare the direction actually drawn into the image; older Apps ignore this metadata and keep their existing icon behavior.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/2.3.1

v2.3.0

Minor Changes

• #32 3a9470f Thanks @ryuhzk! - Accept dust, embers, snow, and stars ambient effects in theme manifests and generated authoring schema. Document static speed, restrained particle settings, and the requirement for a compatible App release before publishing themes with these new values.

  Add bounded density and size controls, theme color role palettes, and eight motion directions. Unsupported controls remain valid and produce authoring warnings instead of validation errors.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/2.3.0

v2.2.0

Minor Changes

• #30 188b766 Thanks @ryuhzk! - Document and scaffold the optional chrome.create icon for OpenCode’s new-session control. Existing Apps ignore the new icon name and keep their native Plus; no theme schema version change is required. Clarify chrome.attach usage across composer controls.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/2.2.0

v2.1.0

Minor Changes

• #28 Thanks @ryuhzk! - Theme System v2 architecture, slot normalization, and ambient effects.

  • Standardize decoration slots to v2 architecture:
    • shell.background -> shell.wallpaper
    • home.background -> home.wallpaper
    • emptyState.illustration -> empty.artwork
  • Introduce home.arrow navigation icon to THEME_ICON_SLOTS and CLI scaffolding with fallback to system chevrons.
  • Add effects ambient shader schema support and validation (rain, particles, scanlines, bloom).
  • Update starter manifest, scaffold, and bundled authoring documentation.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/2.1.0

v2.0.0

Major Changes

• #26 1d0e899 Thanks @ryuhzk! - Unify Home artwork authoring and synchronize previews with the current Classic and Editorial layouts.

  This is a breaking theme-contract change. Replace home.hero and home.decoration with one home.artwork foreground in decoration and every light/dark override. When both old slots exist, choose the intended foreground rather than rendering both. Rename homeIdentity.hero to homeIdentity.artwork; keep home.background as separate wallpaper.

  Use the optional launch.artwork slot only when startup needs different artwork. Without a resolved override (including an explicit null override), startup falls back to home.artwork, then branding. Provide compact/regular overrides and focal points for phone and tablet crops. Legacy foreground slots have no aliases and are no longer recognized by validation; the old identity field is rejected.

  The starter now creates one Home foreground asset shared with the example startup override, avoiding duplicate illustrations. The bundled authoring skill, schema, and layout guidance use the new contract. Editorial themes may configure homePresentation.header and independent toolbarBackground, with custom scan/settings glyphs. CLI preview accepts layout, device, and mode selections for the website preview.

  Upgrade the CLI and theme sources together, then run muqun-theme validate, muqun-theme pack, and muqun-theme check before distribution. Consumers must use App and website builds supporting the unified artwork contract; older clients do not render the new foreground slot. No Gateway or Herdr update is required for this theme-only change.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/2.0.0

v1.9.0

Minor Changes

• #23 fd9f4f5 Thanks @ryuhzk! - home.hero is a decoration slot this build knows, and homeIdentity.hero its
  default/hidden switch — parity with the Muqun app, which now draws the
  theme's own illustration between Home's header row and the server list. The
  slot is validated like emptyState.illustration: an image reference with
  fit, opacity, focalPoint and per-mode and per-width overrides, sized
  against the same 1024px budget.

  check and validate stop reporting home.hero as a slot they have never
  heard of, and init now scaffolds a seventeenth placeholder, home-hero.png,
  wired to the slot with the switch written out beside the Home name and logo.
  No schemaVersion bump: the field is additive, and a pack that declares it
  still installs on an app that has not heard of it.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/1.9.0

v1.8.1

Patch Changes

• #21 26d3d11 Thanks @ryuhzk! - The vendored agent skill is 1.4.0: every theme is asked for a 1024x640 preview
  cover, light on the left half and dark on the right, named in preview.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/1.8.1

v1.8.0

Minor Changes

• #19 a5fd650 Thanks @ryuhzk! - A theme's preview image is published beside its package. When a manifest
  declares preview, build copies that asset out of the packed theme -- the
  bytes as packed, so the optimised WebP -- into dist/previews/<id>.<ext>,
  with the extension (webp, png or jpg) chosen by inspecting the bytes,
  and the index entry gains preview: "dist/previews/<id>.<ext>". A gallery
  can show the picture without downloading the package.

  dist/previews/ mirrors the index: a theme that stops declaring a preview,
  or whose source is gone, loses its file, and build removes anything the
  index does not name. check reports a missing, stale or stray preview file
  and names muqun-theme build as the fix. list --json carries previewUrl
  beside url when the index came from a URL and the entry has a preview.

• #19 d9d4cc5 Thanks @ryuhzk! - init scaffolds a placeholder preview cover (assets/preview.png, 1024x640)
  and names it in preview, so a fresh theme already has what galleries show.
  check --sources --require-preview refuses a source without one; the themes
  repository's CI uses it.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/1.8.0

v1.7.1

Patch Changes

• #17 60521ba Thanks @ryuhzk! - validate no longer warns that a theme's preview image is "declared but
  never drawn". The gallery draws it.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/1.7.1

v1.7.0

Minor Changes

• #15 306a0fe Thanks @BANG88! - chrome.attach is the third chrome glyph a theme may replace, beside
  chrome.back and chrome.send. It is the composer's attachment control, drawn
  at 17pt in the primary colour by default.

  src/schema.ts stays byte-identical to the app's src/theme/schema.ts and the
  vendored skill is regenerated from it, both pinned by tests. init now
  scaffolds a placeholder for the new glyph as it does for the other two, so an
  author sees the mechanism rather than having to read about it.

  No schemaVersion change: iconsSchema is an open record, so a pack naming
  chrome.attach already parsed — it was simply not drawn. Older app builds keep
  ignoring it, which is the forward compatibility the contract provides.

npm: https://www.npmjs.com/package/@osuki-dev/muqun-theme/v/1.7.0