Tune load test thresholds for concurrent deployment pipeline

[temma02]

Description

apps/backend/tests/load/deployment-pipeline.load.test.ts runs concurrent deployments but the pass/fail thresholds (p95 latency, error rate) are not enforced — the test always passes. Define and enforce realistic SLO thresholds.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure
• Relevant files: apps/backend/tests/load/deployment-pipeline.load.test.ts

Suggested execution

• Create branch: issue-014-load-test-deployment-pipeline-thresholds
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Define SLO constants: p95 latency ≤ 3 s, error rate ≤ 1%, throughput ≥ 10 req/s
• Add assertions in generateReport that fail the test when SLOs are breached
• Parameterise concurrency level via an env var so CI can run a lighter variant

Test and commit

• Run the load test locally and confirm thresholds are achievable
• Include the baseline report output in the PR description
• Note: thresholds are for the simulated pipeline, not production Vercel/GitHub APIs

Example commit message

test(load): enforce SLO thresholds in deployment pipeline load test

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs

[Georgebingi]

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

Hi my name is George and I'm a full stack develop I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

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

[drips-wave]

Congratulations, @Georgebingi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Georgebingi: 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 @Georgebingi as part of the Stellar Wave Program's 4th Wave 🥳

😎 @Georgebingi: You earned 150 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.