Omachord 0.4.0

Omachord 0.4.0 adds steady loading switches, faster connection changes, and stronger configuration and recovery handling.

Changes

• Pending switches keep their size and show progress. The panel and bar share confirmed connection state, and failed requests release controls for retry.
• Independent routine requests can run concurrently. Shortcut processing and filesystem inspection are batched while retaining locks, rollback and durable writes.
• Manual UI starts use the configuration revision displayed when clicked. A save made while the request waits requires a fresh review and retry, including saves to unrelated routines. Explicit CLI starts without a revision continue to use the latest committed configuration.
• Turning Omachord off also stops automatic requests already waiting for the configuration lock. Manual runner commands remain available while off.
• Configuration must contain exactly one JSON document. Startup can repair committed integration but cannot silently approve changed or unmarked executable configuration.
• Active routines retain their original end-action identity. Explicit revision-bound recovery can skip an ambiguous legacy action list while preserving typed setting restoration.
• Theme/status reads are bounded, metadata watchers avoid loading file bodies, cancellation stays tied to the owned process, and filesystem recovery reports surviving paths accurately.
• Production test-only fault/marker/count controls and the reload-validation bypass are removed. Explicit disposable fixtures retain deterministic failure coverage.
• Routine IDs that match JavaScript object property names work correctly. Wi-Fi names preserve exact leading and trailing spaces.
• Manual installation/update/removal documentation and portable CI coverage are expanded.

Compatibility and upgrading

Supported versions: Omarchy 4.0.2, Hyprland 0.56.2, Quickshell 0.3.1, GNU coreutils 9.5+, and GNU awk. See the README for all requirements.

Restart Omarchy Shell after updating to load the QML components. Existing routine configuration is retained. Review externally supplied routines before explicitly accepting or running them: routines remain trusted, unsandboxed local code executed with your user privileges, and may invoke sudo.

New active-recovery records use version 2. Complete restoration or explicit recovery before downgrading; older runners reject these records. Legacy records with ambiguous end actions require the documented recovery inspect and revision-bound recovery restore ... --skip-end-actions flow.

Connection changes may still wait for active-routine restoration, reload/validation, durability barriers or configuration locks. Retained recovery archives and detached audio have no global resource quota. See known issues and the security model.

Validation and provenance

Release commit: a8453858868b86c57ea101af4b0f2d66fd8347b2, merged through PR #6. Its source tree is byte-identical to the independently reviewed and live-tested candidate.

Main CI, tag CI, and CodeQL passed.

Validation includes complete clean-checkout and committed-archive suites, native QML interaction tests, filesystem/process/recovery and write-failure regressions, eight direct production-instrumentation boundary tests, non-root portable CI, CodeQL and eight reviewed offscreen views. The actual Off-state bar icon and its in-memory color transition were checked in the supported running Omarchy Shell; the full theme-set hook pipeline and active-routine visuals were not exercised in that live smoke check.

Omachord ships as source, scripts, QML and assets. The automatic source archives contain the complete project; there is no separate compiled application binary. This release does not claim renewed marketplace approval.

Full changelog