[adibmbrk]

Summary

• Replaced MessageLayout with StudioMessageLayout
• Replaced VForm with <form> and used generateFormMixin for validation, the same way as RequestNewActivationLink
• Replaced Banner with StudioBanner
• Replaced EmailField with StudioEmailField
• Updated the unit tests to check validation messages and the error banner

Screenshots

References

Closes #5932

[learning-equality-bot]

👋 Hi @adibmbrk, thanks for contributing!

For the review process to begin, please verify that the following is satisfied:

• Contribution is aligned with our contributing guidelines

• Pull request description has correctly filled AI usage section & follows our AI guidance:

  AI guidance

  
  

  State explicitly whether you didn't use or used AI & how.

  If you used it, ensure that the PR is aligned with Using AI as well as our DEEP framework. DEEP asks you:

  • Disclose — Be open about when you've used AI for support.
  • Engage critically — Question what is generated. Review code for correctness and unnecessary complexity.
  • Edit — Review and refine AI output. Remove unnecessary code and verify it still works after your edits.
  • Process sharing — Explain how you used the AI so others can learn.

  
  

  Examples of good disclosures:

  "I used Claude Code to implement the component, prompting it to follow the pattern in ComponentX. I reviewed the generated code, removed unnecessary error handling, and verified the tests pass."

  "I brainstormed the approach with Gemini, then had it write failing tests for the feature. After reviewing the tests, I used Claude Code to generate the implementation. I refactored the output to reduce verbosity and ran the full test suite."

📢✨ Before we assign a reviewer:

• @rtibblesbot will pre-review this pull request. Its comments are generated by an LLM, and should be evaluated accordingly.
• We'll also invite community pre-review. See the community review guidance for both authors and reviewers.

Also check that issue requirements are satisfied & you ran pre-commit locally.

Pull requests that don't follow the guidelines will be closed.

Reviewer assignment can take up to 2 weeks.

[rtibblesbot]

🟡 Waiting for changes

Outcome: skipped — no new commits since 3c46df4

Last updated: 2026-10-27 09:26 UTC

[rtibblesbot]

PR #6334 is blocked on missing screenshots. The code follows the merged RequestNewActivationLink.vue pattern (#6026) and covers all four replacements the issue lists.

CI: only Pull Request Template / Check template fails, on the screenshot placeholder. Manual QA did not run.

• blocking: screenshots missing. The PR body still has <!-- TODO: add screenshots -->. The issue's acceptance criteria require screenshots. Add before/after for the default state, the required-field error, the invalid-email error and the error banner (force it temporarily). Add RTL and mobile widths too.
• suggestion: validation now runs on every keystroke; note it in the PR body (inline).
• suggestion: validation-message assertions match on text alone; scope them to the email field (inline).

Next step: Needs a full code review by a human engineer, then manual QA once that reviewer sets Needs QA.

• The author is outside the team: confirm this should be built at all.
• User-visible files changed: contentcuration/contentcuration/frontend/accounts/pages/resetPassword/ForgotPassword.vue.
• Check that the required-field error, the invalid-email error and the error banner render correctly at mobile width and in RTL.
• Confirm that errors showing on each keystroke, rather than on blur, is acceptable.

---

Written by rtibblesbot, an LLM-based coding agent.

[rtibblesbot]

PR #6334: both prior findings are resolved. Manual QA did not run. The UI is unverified.

Prior-finding status

RESOLVED — contentcuration/contentcuration/frontend/accounts/pages/resetPassword/ForgotPassword.vue:25 — validation runs on every keystroke instead of on blur
RESOLVED — contentcuration/contentcuration/frontend/accounts/pages/tests/forgotPassword.spec.js:50 — text assertions match anywhere on the page

Next step: Needs a full code review by a human engineer, then manual QA once that reviewer sets Needs QA.

• The author is outside the team: confirm this should be built at all.
• User-visible files changed: contentcuration/contentcuration/frontend/accounts/pages/resetPassword/ForgotPassword.vue.
• Check the email error appears only after blur or submit, and the reset link sends for a valid email.

---

Written by rtibblesbot, an LLM-based coding agent.

Superseded by my review of 3c46df4: no blocking findings remain.

[akolson]

@adibmbrk Thanks for your work on this PR! Could you please update it to use the required PR template? Also be sure add screenshots to help reviewers assess your changes more thoroughly, as this is frontend focused issue.