chore: update frontend version to v0.1.8-p1

[think-in-universe]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @think-in-universe, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the error messaging for user bans within the API. By introducing a more generalized constant and updating its message, the change aims to provide a clearer and more consistent user experience when access is temporarily restricted, abstracting away specific ban reasons from the end-user message.

Highlights

• Error Message Refactoring: The pull request renames the NEAR_BAN_ERROR_MESSAGE constant to USER_BANNED_ERROR_MESSAGE to make it more generic and reusable.
• Updated Ban Message: The content of the ban error message has been updated from 'User is temporarily banned from using this feature; please try again later' to 'Access temporarily restricted. Please try again later.' for broader applicability.
• Consistent Error Handling: The new USER_BANNED_ERROR_MESSAGE constant is now consistently used in both the ensure_near_balance_for_near_user and ensure_user_not_banned functions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the error message for banned users to be more generic, replacing NEAR_BAN_ERROR_MESSAGE with USER_BANNED_ERROR_MESSAGE and updating its value. While this is a good refactoring, it causes an integration test to fail because the test was not updated with the new error message. Additionally, the pull request title is misleading as it refers to a frontend version update, while the changes are in the backend API. Please update the title to accurately reflect the changes and fix the failing test.

[claude]

Code Review - PR #87

Analyzed the refactoring of ban error message constants. Changes look good overall.

Summary

This PR renames NEAR_BAN_ERROR_MESSAGE to USER_BANNED_ERROR_MESSAGE and updates the message text. The constant is moved from top of file to line 38, and both usage sites are correctly updated.

Analysis

✅ No Critical Issues Found

What was checked:

• Correctness: Both usage sites updated correctly (api.rs:1311 and api.rs:1357)
• No dangling references: Verified old constant name is completely removed
• Backward compatibility: This is a user-facing error message change, but:
  • Error message changes are acceptable for temporary ban scenarios
  • HTTP status code remains 403 FORBIDDEN (no API contract break)
  • Error response structure unchanged
• Privacy compliance: ✅ New message follows CLAUDE.md guidelines - no customer data exposed, generic message appropriate
• Consistency: Message now applies to both NEAR balance bans and general user bans, making it more generic and appropriate

Minor observations (non-blocking):

• The new message "Access temporarily restricted. Please try again later." is more generic than the old "User is temporarily banned from using this feature; please try again later"
• This is actually an improvement as the constant is used for multiple ban types (NEAR balance bans and general user bans), so a generic message is more appropriate

✅ APPROVED - Safe to merge

[Copilot]

Pull request overview

This PR refactors the error messaging for banned users in the API backend. Despite the title mentioning a frontend version update, the actual changes focus on renaming and generalizing the user ban error constant.

• Renamed NEAR_BAN_ERROR_MESSAGE constant to USER_BANNED_ERROR_MESSAGE for better generalization
• Updated error message text to be more concise and less implementation-specific
• Relocated constant definition within the file for better organization

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.