Land the password login and admin temporary reset UI that Dev main already pins and runs.
Why:
Dev main pins modules/frontend at 92864db (deployed together with Backend b00e192), but that commit only lives on feature/auth-password-management-frontend; Frontend main never received it. The next Dev pin back to Frontend main (RDM settings phase 1a) would silently roll back password login and admin temporary resets.
Backend counterpart already landed in Backend main (Backend PR #211). No new code here: the three commits (2f8009b, fb1f9f2, 92864db) were reviewed and verified in Dev task feature-auth-password-management.
Evidence:
git merge-tree --write-tree origin/main 92864db is conflict-free (5 files, +72/-91).
Frontend CI runs governance checks only; tsc -b, vitest run and vite build are run locally on the merged tree (SELF) and repeated in the Dev composition CI when Dev re-pins Frontend.
Impact:
No behaviour change for Dev or the deployed system (already running this code). Frontend main gains the commits Dev pins.
Refs:
Backend PR #211; Dev task feature-rdm-settings-phase1a.
Land the password login and admin temporary reset UI that Dev main already pins and runs.
Why:
- Dev main pins `modules/frontend` at `92864db` (deployed together with Backend `b00e192`), but that commit only lives on `feature/auth-password-management-frontend`; Frontend main never received it. The next Dev pin back to Frontend main (RDM settings phase 1a) would silently roll back password login and admin temporary resets.
- Backend counterpart already landed in Backend main (Backend PR #211). No new code here: the three commits (`2f8009b`, `fb1f9f2`, `92864db`) were reviewed and verified in Dev task `feature-auth-password-management`.
Evidence:
- `git merge-tree --write-tree origin/main 92864db` is conflict-free (5 files, +72/-91).
- Frontend CI runs governance checks only; `tsc -b`, `vitest run` and `vite build` are run locally on the merged tree (SELF) and repeated in the Dev composition CI when Dev re-pins Frontend.
Impact:
- No behaviour change for Dev or the deployed system (already running this code). Frontend main gains the commits Dev pins.
Refs:
- Backend PR #211; Dev task `feature-rdm-settings-phase1a`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Land the password login and admin temporary reset UI that Dev main already pins and runs.
Why:
modules/frontendat92864db(deployed together with Backendb00e192), but that commit only lives onfeature/auth-password-management-frontend; Frontend main never received it. The next Dev pin back to Frontend main (RDM settings phase 1a) would silently roll back password login and admin temporary resets.2f8009b,fb1f9f2,92864db) were reviewed and verified in Dev taskfeature-auth-password-management.Evidence:
git merge-tree --write-tree origin/main 92864dbis conflict-free (5 files, +72/-91).tsc -b,vitest runandvite buildare run locally on the merged tree (SELF) and repeated in the Dev composition CI when Dev re-pins Frontend.Impact:
Refs:
feature-rdm-settings-phase1a.