Replace NEXT_PUBLIC_MOCK_MAINTAINER env flag with useUserRole hook

[Benjtalkshow]

components/bounty/bounty-sidebar.tsx:32 gates maintainer-only UI on the NEXT_PUBLIC_MOCK_MAINTAINER env var:

const IS_MAINTAINER = process.env.NEXT_PUBLIC_MOCK_MAINTAINER === "true";

PR #254 added a real useUserRole() hook at hooks/use-user-role.ts that returns "sponsor" | "contributor" | undefined from the session. The env var bypasses this entirely, and the console.warn block at lines 36-43 even acknowledges the env var is a dev shim that should not be enabled in production.

What to do

• Remove the IS_MAINTAINER env-based constant and the console.warn block
• Import useUserRole from @/hooks/use-user-role
• Replace IS_MAINTAINER references with the role check that matches the maintainer-gated UI (likely role === "sponsor" based on the PR Add sponsor role feature - gate Create access to sponsors #254 contract)

Acceptance criteria

• No reference to NEXT_PUBLIC_MOCK_MAINTAINER remains in bounty-sidebar.tsx
• The same maintainer-only UI now appears for users with the sponsor role and is hidden for contributors
• No new env vars required
• console.warn block removed

Files

• components/bounty/bounty-sidebar.tsx
• hooks/use-user-role.ts (reference)

[linear]

BOU-296

[coderabbitai]

🔗 Related PRs

#88 - feat: Implement bounties detail page [merged]
#154 - feat: implement Stellar Explorer Integration and Transaction Links [merged]
#161 - feat(bounty): add FCFS single-claim flow with claim/approve UI and cl… [merged]
#254 - Add sponsor role feature - gate Create access to sponsors [merged]
#265 - feat: implement maintainer dashboard actions for multi-winner milestone bounties [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Olajcodes]

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

Hi maintainer! I would love to help you with this issue. Given my theoretical knowledge and background, I am quite sure that I am well-equipped to tackle it. Please kindly assign it to me.

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

[Jerry-Tekh]

@Jerry-Tekh has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi repo Manager, I'll like to take up this task.

I’ll remove the NEXT_PUBLIC_MOCK_MAINTAINER flag + http://console.warn from bounty-sidebar.tsx, swap in useUserRole() from @/hooks/use-user-role, and gate the maintainer UI on role === "sponsor" so it shows for sponsors only and hides for contributors. No new env vars.

Assign me and I’ll ship the hook replacement with the UI behavior matched in one PR.

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

[YashMahawa]

Opened PR #286 for this: #286

[lekanay2005-coder]

@lekanay2005-coder has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer. I am interested in this issue.

I have experience working across frontend, backend, smart contracts, and developer tooling, and I’m comfortable making targeted fixes and improvements in existing codebases. I’ll ensure the implementation is clean, tested, and aligned with the project requirements.

Thanks!

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

[drips-wave]

Congratulations, @Olajcodes! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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