Add e2e coverage for the open-house API: no end-to-end spec exercises scheduling and RSVP

[nanaf6203-bit]

Add e2e coverage for the open-house API: no end-to-end spec exercises scheduling and RSVP

Labels / Complexity: testing · Medium Complexity — Medium

Problem

The test/e2e/ suite has no spec for the open-house module (6 files, 0 unit specs). Open-house scheduling and RSVP involve property owners and attendees, and none of it is pinned at the HTTP level. A regression that lets attendees RSVP to cancelled events or owners lose control of their listings ships silently.

Why this is architecturally hard

1. Ownership boundaries are the test design. The spec must assert that only the property owner can schedule/modify, and attendees can RSVP — the RBAC e2e pattern applied to a resource-ownership model.
2. State transitions need fixtures. Schedule → RSVP → cancel flows need seeded properties and users.

Acceptance criteria

• An e2e spec covers scheduling, RSVP, and cancellation with correct ownership/attendee access.
• The spec runs in CI with the existing e2e harness.

Out of scope

Unit coverage (#30); open-house behavior changes.

Getting started

• src/open-house/open-house.controller.ts — the endpoints
• test/e2e/rbac-enforcement.e2e.spec.ts — the access-boundary pattern

Commands: npm run test:e2e (or the repo's e2e script from package.json).

Good first files to read: test/e2e/rbac-enforcement.e2e.spec.ts, src/open-house/open-house.controller.ts.

[iorchirmyom-afk]

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

Hello Maintainer, I’ve carefully reviewed the issue and understand the requirements and acceptance criteria. I’m confident I can implement a clean and effective solution. Kindly assign it to me. Thank you.

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

[coolman77-ctrl]

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

Hi Maintainer! I'm a senior developer with experience building high-quality, production-ready software. I'd love to take on this issue and deliver a clean, well-tested solution that aligns with the project's standards. Please assign it to me—I'm ready to get started and contribute effectively.

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

[drips-wave]

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

🧑‍💻 @coolman77-ctrl: 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 🌊