Add `area: zk` and `mainnet` labels to the repo label taxonomy

[Gbangbolaoluwagbemiga]

Overview

Verify and finalize the new component:zk, zk, and mainnet labels created for this wave are correctly applied across all 150 new issues and are documented in whatever central label reference the project maintains.

Background / Context

This issue exists to formally close the loop on label-taxonomy setup performed at the start of this wave (new labels were created directly via the GitHub API before issue creation began) and confirm consistent application.

Goal

A verification pass confirming every mainnet-wave issue carries the mainnet label and every ZK-wave issue carries the zk and component:zk labels as appropriate, with any missed issue corrected.

Scope of Work

1. Query all issues created in this wave and verify label consistency.
2. Correct any missing/inconsistent labeling found.

Out of Scope

• Creating additional new labels beyond component:zk, zk, mainnet — those were already added.

Acceptance Criteria

• Label audit completed with 100% consistency across the wave's issues.

Dependencies / Related

Depends on #1112-#1251 being created.

Difficulty & Estimated Effort

Easy — ~half a day, verification pass.

[Adjutant500]

@Adjutant500 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer please I will like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adjutant500 to this issue.

[Richiey1]

@Richiey1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi there! 👋 I'd love to help out with the repo organization! Adding proper taxonomy labels like area: zk and mainnet is super important for keeping the community and contributors aligned. I've helped maintain and organize several open-source repositories before, so I'm very familiar with configuring GitHub labels and updating contributing guidelines to make sure everyone knows how to use them properly. I'd be super excited to get this set up for you all! Let me know if I can take this on!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Richiey1 to this issue.

[drips-wave]

Congratulations, @Richiey1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Richiey1: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊