[Improvement] CI lint gate allows 250 warnings while syntax.yml allows zero

[RUKAYAT-CODER]

Overview

.github/workflows/ci.yml runs npm run lint -- --cache --max-warnings=250, while .github/workflows/syntax.yml runs npx eslint . --max-warnings=0. Two gates on the same tool with thresholds 250 apart means one of them is always the real gate and the other is theatre — and neither can pass today. A 250-warning allowance also has no ratchet, so warnings can accumulate up to the cap without any signal.

Specifications

Features:

• One lint gate with one threshold
• A ratcheting warning budget that can only decrease
• The redundant gate removed

Tasks:

• Fix the ESLint configuration, then measure the real warning count
• Set a single threshold at the measured count and remove the duplicate gate
• Add a CI step that fails if the count rises
• Schedule the warning count down over time

Impacted Files:

• .github/workflows/ci.yml
• .github/workflows/syntax.yml
• eslint.config.js

Acceptance Criteria

• Exactly one workflow gates on lint
• The warning budget is measured, not guessed
• The budget can only decrease

[RemmyAcee]

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

Interested in contributing to this issue. I'll ensure the implementation is clean, tested, and follows project conventions.

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

[snowrugar-beep]

@snowrugar-beep has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will resolve the discrepancy where the CI lint gate allows 250 warnings while syntax.yml allows zero warnings. The core deliverable establishes a consistent warning threshold across both configurations that matches the projects quality standards. I will either tighten the CI gate to zero or document the rationale for allowing warnings in local development.

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

[drips-wave]

Congratulations, @snowrugar-beep! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @snowrugar-beep: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@snowrugar-beep's PR #1059 was approved and merged by @RUKAYAT-CODER.

🏆 @snowrugar-beep: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,308 total points). Track your full progress on GrantFox.

👏 Great work, @snowrugar-beep! Keep contributing to rinafcode.

[drips-wave]

This issue has been completed by @snowrugar-beep as part of the Stellar Wave Program's 8th Wave 🥳

😎 @snowrugar-beep: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.