# Omagen v2.0.0

> Stable release notes for the exact `main` snapshot tagged `v2.0.0`.

Omagen v2 turns the original image-to-theme idea into a reversible desktop
studio. It helps you explore a visual direction, test it in context, and keep
your existing desktop safe while you decide.

## Highlights

- Six image-derived palette directions: Source, Calm, Mute, Deep, Vibrant, and
  Balanced.
- Fast and In-depth workflows, so a quick generation and a detailed desktop
  composition can share the same session.
- Live Canvas Preview and Test live for reversible desktop inspection.
- Temporary Demo workspaces with capability detection and useful fallbacks.
- Optional Window, Shell, Bar, Animation, Look & Feel, terminal, and
  unlock-screen composition.
- Apply, Cancel, Quit, interrupted-session recovery, and ownership-aware
  rollback.
- An optional full-bar suite component through the separately registered
  `pretty.omagen.bar` package.
- Reproducible bundled Go backend and checked-in shader artifacts.

## What changes for users

Version 2 is a larger, safer workflow around the original image-to-theme
concept. You can inspect a generated direction, try it temporarily, and back
out before saving a permanent theme. Existing user-owned themes and unrelated
Omarchy resources remain outside Omagen's ownership boundary.

The core Studio package remains the normal installation. The full-bar package
is still separately registered and opt-in; it is not silently substituted for
Omarchy's native bar.

## Upgrade notes

The supported migration target is the current stable Omagen installation. The
release does not promise indefinite compatibility with undocumented legacy
branches or internal paths. During an upgrade, allow an active session to
finish or use Restore & close first.

Omagen preserves permanent themes, unrelated plugins, native shell settings,
external backgrounds, and resources without Omagen ownership markers. Use the
[recovery guide](../recovery.md) before manually removing state.

## Trust and limitations

Omagen is unsandboxed user-level plugin code. It can read selected images and
relevant Omarchy state, write generated themes and session state, invoke its
bundled backend and explicit user-level adapters, and interact with the active
Omarchy/Hyprland session. It does not require `sudo`, install system packages,
or configure privileged services.

Marketplace verification, when present, is evidence for one exact source
snapshot. It is not a security certification, endorsement, or guarantee. A
mutable branch or unpinned installation can differ from the reviewed commit.

## Verification record

This record is bound to the immutable stable snapshot. The marketplace report
is a deterministic baseline check, not a security certification or endorsement.

- Stable commit: recorded by the exact `main` commit and marketplace artifact at submission time; do not copy an older SHA here.
- Release tag: `v2.0.0`
- Marketplace preflight: Generate a new commit-bound report for the immutable
  final `main` SHA immediately before submission. Never reuse an older report.
- Live-desktop evidence: Maintainer-confirmed sufficient for the v2 product
  presentation. No new live-desktop test was run by this automation.
- Known working Omarchy versions: `4.0.1-1` and `4.0.2-1`, as confirmed by the
  maintainer; attach the exact capture records to the release evidence.
- Independent installations: Attach at least five exact records before
  marketplace submission.
- Upgrade runs: Attach at least two exact records before marketplace
  submission.
- Interrupted-session recovery: Attach at least one exact record before
  marketplace submission.

For maintainer-only build provenance, security findings, and live-validation
evidence, see the [developer release process](../../development/release-process.md)
and [maintainer release notes](../../releases/v2.0.0.md).