---
title: Compatibility
description: What Forge has actually verified against Omarchy and what remains heuristic.
---

# Compatibility



Forge distinguishes installed upstream evidence from its own static quality
rules.

## Current target [#current-target]

* Installed package verified: `omarchy 4.0.0-1`.
* Manifest schema: JSON number `1`.
* Forge compatibility selector: `--omarchy-version 4`.
* Official pinned inspection: Omarchy `quattro` revision `ed7bae4`.
* Reference plugin inspection: Basecamp revision `abc1ba7`.

The installed official validator remains authoritative. Findings labeled
`official-parity` mirror the inspected validator contract so CI can run without
an Omarchy installation. Findings labeled `forge` cover additional structural,
security, UX, and publish-readiness expectations.

## Runtime evidence [#runtime-evidence]

A generated sample has been installed, enabled, exercised, disabled, and
removed on the actual Omarchy system. Verified scenarios include horizontal and
vertical bars, keyboard behavior, dark and light themes, ready/empty/error demo
states, hot reload, and exact restoration of user shell configuration.

Static heuristics are not runtime proof. Pattern matches are labeled as
heuristics and require human review.

Generated projects also contain a separately invoked, explicitly trusted
Quickshell smoke test. It uses the installed Omarchy QML modules inside a
temporary HOME/XDG environment and is intentionally excluded from static checks
and CI.

See the repository's `docs/UPSTREAM_COMPATIBILITY.md` for commands, inspected
paths, limitations, and the complete evidence log.


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)