Add integration test for the creator update endpoint persisting display name and bio changes

[Chucks1093]

Summary

Creators should be able to update their display name and bio after registration. An integration test should confirm updates persist correctly, that another wallet cannot update a creator's profile, and that empty string values are rejected.

Scope

• PATCH the creator profile with a new display name and bio, assert 200 and changes persisted
• Call the creator profile GET and assert the new values are returned
• Authenticate as a different wallet and PATCH the creator's profile, assert 403
• PATCH with an empty string display name and assert 422 with a validation error
• Assert the original values are unchanged after both failed attempts

Acceptance Criteria

• Display name and bio update and persist correctly
• GET returns updated values after successful PATCH
• Different wallet returns 403
• Empty display name returns 422
• Original values unchanged after failed attempts

ETA: 12 hours

---

Coordinate on Telegram

[omoh5]

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

Please can you assign this to me
Thank you very much

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

[apatafamilycompound123-ops]

@apatafamilycompound123-ops has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.

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

[Godfrey-Delight]

@Godfrey-Delight has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Sir please i would love to work on this

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

[DavisVT]

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

pls assign this issue to me

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

[chidii]

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

Hello Maintainer, I've reviewed this issue thoroughly and I'm well positioned to resolve it — experienced across the relevant stack and comfortable navigating the existing codebase. Ready to start right away.

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

[drips-wave]

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

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