STAB-BE-005 — Restore the API Required CI Gate Set

[dDevAhmed]

Objective

Restore a truthful, non-skippable API verification pipeline on the stabilized dependency baseline.

Required gates

• clean install / lockfile integrity
• lint and typecheck
• unit and integration tests
• production build
• container smoke build
• dependency/security scan
• migration/schema drift check where applicable

Acceptance criteria

• Every gate runs on pull requests and the default branch.
• Failures fail the workflow; no continue-on-error, unconditional success, or concealed skip.
• Job names are stable and suitable for branch-protection requirements.
• A test pull request demonstrates that a deliberate failure blocks the gate.
• Workflow permissions are least-privilege and third-party actions are pinned.

Dependencies

STAB-BE-001 and STAB-BE-002; coordinate with STAB-BE-003/004.

Activation status

Reserved for the next Stellar Wave. Do not begin work and do not self-assign until maintainers apply the Stellar Wave label.

This issue is additive. It does not replace, close, or reduce any existing V2 issue.

Contribution rules

• One issue per pull request.
• Rebase on the then-current main before implementation.
• Do not bundle dependency upgrades, redesigns, or unrelated cleanup.
• Do not weaken or skip CI checks.
• Include reproducible before/after evidence and update relevant documentation.
• A pull request is not eligible to merge until the Stellar Wave has started and all required gates and human reviews pass.

Maintainer revalidation — 2026-09-21

• Classification: Contributor-suitable, reserved until activation
• Complexity: Medium
• Points: 150
• Activation position: Later recovery batch
• Required review: API maintainer; CI/security review
• Overlap/dependency note: Overlaps existing issue V2-BE-044 — Make API Security, Build, and Artifact Checks Non-Skippable #395 and PR ci(gates): Make API security, build, and artifact checks non-skippable (#395) #443. Reconcile and reuse valid work without closing V2-BE-044 — Make API Security, Build, and Artifact Checks Non-Skippable #395 automatically.
• Wave state: Not assigned and not active. Maintainers will apply Stellar Wave only when selected for an activation batch.

[ykargeee-bit]

@ykargeee-bit has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi Maintainer,

I’m a full-stack developer, and I’d like to contribute to the task. I’ll implement it carefully and efficiently thoroughly understand requirements and edge cases
Communicate promptly about suggestions or improvements. And I will provide regular progress updates and address blockers
Align with project goals through feedback and clarification.

Thank you,

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

[drips-wave]

Congratulations, @ykargeee-bit! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @ykargeee-bit: 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 🌊

[drips-wave]

This issue has been completed by @ykargeee-bit as part of the Stellar Wave Program's 9th Wave 🥳

😎 @ykargeee-bit: 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.