[BE-127] Build a real E2E suite — the CI job currently passes with no tests

[mftee]

Overview

CI has a well-configured backend-e2e job with Postgres 16 and Redis 7 service containers, correct environment variables, and PR-only triggering — genuinely good infrastructure. But it runs npm run test:e2e -- --passWithNoTests against a single placeholder spec, so all of that runs and proves nothing.

Tasks

• Write E2E specs covering the critical journeys: register → login → upload document → risk assessment → verification → retrieve.
• Cover authorization end to end: a user cannot read another user's documents, disputes, or access logs.
• Cover the public verification path without authentication.
• Truncate tables between tests for isolation.
• Remove --passWithNoTests once specs exist.
• Once [BE-111] lands, ensure the E2E job provisions schema via real migrations so migration correctness is validated on every PR.

Acceptance Criteria

• npm run test:e2e exercises real journeys against the service containers.
• Cross-user authorization tests fail if a guard is removed.
• The job no longer passes vacuously.

Dependencies

Best after [BE-111].

Notes for Contributors

Comment below to be assigned.

[Lynndabel]

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

I’d like to work on this issue. I have experience working with Stellar and Web3 projects, including Soroban contracts and frontend/backend integrations. I’ll go through the existing code first, make the required changes, and test everything properly. I’m ready to start.

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

[ustaxs]

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

Good day

I have read the requirements of this issue and i am confident that i can solve this

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

[drips-wave]

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

🧑‍💻 @ustaxs: 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!

@ustaxs's PR #1230 was approved and merged by @mftee.

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

👏 Great work, @ustaxs! Keep contributing to CodeGirlsInc.

[drips-wave]

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

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