feat: block project owners from self-reviewing via service guard and …

[Challmejosh]

Closes #235

---

Summary

Project owners could previously submit ratings for their own projects, potentially biasing scores. This PR enforces the restriction at both the UI and service layers, and adds a dedicated hook to centralise the ownership check.

Changes

services/review/review.service.ts

• Added optional ownerAddress parameter to addReview
• Guards against self-reviews before any other validation or storage write; returns a structured ReviewValidationError so callers need no changes to their error-handling

hooks/useIsProjectOwner.ts (new)

• Reusable hook that compares the connected wallet's publicKey against a project's ownerAddress
• Returns false safely when either value is absent (disconnected wallet, unclaimed project)

app/projects/[id]/page.tsx

• Replaces the inline isOwner expression with useIsProjectOwner
• Passes project.ownerAddress through to reviewService.addReview so the service-layer guard fires even if the UI is bypassed

Tests

Suite	New cases	Result
review.service.test.ts — self-review guard	4	✅
useIsProjectOwner.test.ts	6	✅
Full existing suite	29	✅

39 / 39 tests pass.

Acceptance criteria

Criterion	Status
Owners cannot submit normal public ratings for their own project	✅ Blocked at service layer
The blocked state explains why	✅ Existing blue info-banner shown to owners
Tests cover owner and non-owner review attempts	✅ self-review guard describe block

[drips-wave]

@Challmejosh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits