Add omazed to fast release ring

[APS6]

Changes in the theme file position and the palette in Omarchy quattro broke omazed on release. And while I did push a fix on August 15 hoping that it would be picked up by the OPR soon I didn't realize that it would be stuck on edge for so long.
Considering the nature of the package I think it would make sense to put omazed on the fast release ring, which is what this pr does. But I would request to at least migrate version 2.1.0-2 to stable so that the fix can reach everyone.

[Copilot]

Pull request overview

This PR updates the Omarchy package metadata for omazed to move it onto the fast release ring, addressing slower propagation of upstream fixes that affected releases.

Changes:

• Added release_ring: "fast" to pkgbuilds/omazed/.omarchy/package.json so omazed follows the fast release cadence.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[greptile-apps]

Greptile Summary

This PR moves omazed into the fast release ring so fixed releases can reach the stable repository through normal stable automation.

• Adds the supported release_ring: "fast" package metadata.
• Makes omazed eligible for direct stable builds and scheduled stable releases.

Confidence Score: 5/5

The PR appears safe to merge because the metadata value is valid and implements the stated stable-release behavior.

The release tooling recognizes fast as the supported stable-ring value, and no additional package metadata or coordinated code change is required.

Important Files Changed

Filename	Overview
pkgbuilds/omazed/.omarchy/package.json	Adds the valid fast-ring metadata needed to include omazed in stable release selection; no correctness issue was identified.

_{Reviews (1): Last reviewed commit: "chore(omazed): add to fast release ring" | Re-trigger Greptile}