Signup and login lacked autofill hints and a shared credential group, leaving Safari to guess which email and password fields belonged together. The auth form now exposes username/contact metadata, current-password for login, and new-password on both signup password fields. Password visibility changes retain these roles.
Accepted signup credentials finalize before clearing. Login waits for any second factor and completion before saving; invalid input, service failure, unverified-account recovery, abandonment and mode changes cannot prematurely request saving. Existing domain boundaries and semantic journey analytics remain unchanged, with no credential telemetry.
Validation: formatting of all five changed Dart files, flutter analyze in frontend/app, make test-frontend (212 tests), and flutter build web passed. Focused tests simulate grouped platform autofill in EN/RU and check success, failure/retry, stale results, mode changes, visibility, abandonment and second-factor cancellation. Built-page DOM inspection confirmed username/current-password for login and two new-password inputs for signup in a single form.
Native Safari popup/saved-credential behavior needs a manual check because computer-control permission was unavailable. Flutter web accessibility semantics can leave unfocused inputs at framework-default autocomplete values until focused; assistive-technology/password-manager integration also needs a native browser audit. Details and release checks: docs/ux/auth-journeys.md.
Deployment update (19 October 2026): merged into main as 30f06c2 and rebuilt/recreated the local frontend only. Fresh stable base-image/Flutter pins, formatting, app analysis, all 212 frontend tests and the Docker frontend build passed. The replacement container is healthy, HTTPS returns 200, and the served JavaScript hash matches the new container and includes the autofill hint arrays. Running image: sha256:3bc4fcb9c469be29a160cd8a6951e1424098bf87e3ff31b255d1eec4ad04b78c. Native Safari popup verification remains manual; reload the page to use the new build. Detailed deployment evidence is recorded on task #56.
Signup and login lacked autofill hints and a shared credential group, leaving Safari to guess which email and password fields belonged together. The auth form now exposes username/contact metadata, current-password for login, and new-password on both signup password fields. Password visibility changes retain these roles.
Accepted signup credentials finalize before clearing. Login waits for any second factor and completion before saving; invalid input, service failure, unverified-account recovery, abandonment and mode changes cannot prematurely request saving. Existing domain boundaries and semantic journey analytics remain unchanged, with no credential telemetry.
Validation: formatting of all five changed Dart files, flutter analyze in frontend/app, make test-frontend (212 tests), and flutter build web passed. Focused tests simulate grouped platform autofill in EN/RU and check success, failure/retry, stale results, mode changes, visibility, abandonment and second-factor cancellation. Built-page DOM inspection confirmed username/current-password for login and two new-password inputs for signup in a single form.
Native Safari popup/saved-credential behavior needs a manual check because computer-control permission was unavailable. Flutter web accessibility semantics can leave unfocused inputs at framework-default autocomplete values until focused; assistive-technology/password-manager integration also needs a native browser audit. Details and release checks: docs/ux/auth-journeys.md.
Closes #56.
Deployment update (19 October 2026): merged into main as 30f06c2 and rebuilt/recreated the local frontend only. Fresh stable base-image/Flutter pins, formatting, app analysis, all 212 frontend tests and the Docker frontend build passed. The replacement container is healthy, HTTPS returns 200, and the served JavaScript hash matches the new container and includes the autofill hint arrays. Running image: sha256:3bc4fcb9c469be29a160cd8a6951e1424098bf87e3ff31b255d1eec4ad04b78c. Native Safari popup verification remains manual; reload the page to use the new build. Detailed deployment evidence is recorded on task #56.
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.
Signup and login lacked autofill hints and a shared credential group, leaving Safari to guess which email and password fields belonged together. The auth form now exposes username/contact metadata, current-password for login, and new-password on both signup password fields. Password visibility changes retain these roles.
Accepted signup credentials finalize before clearing. Login waits for any second factor and completion before saving; invalid input, service failure, unverified-account recovery, abandonment and mode changes cannot prematurely request saving. Existing domain boundaries and semantic journey analytics remain unchanged, with no credential telemetry.
Validation: formatting of all five changed Dart files, flutter analyze in frontend/app, make test-frontend (212 tests), and flutter build web passed. Focused tests simulate grouped platform autofill in EN/RU and check success, failure/retry, stale results, mode changes, visibility, abandonment and second-factor cancellation. Built-page DOM inspection confirmed username/current-password for login and two new-password inputs for signup in a single form.
Native Safari popup/saved-credential behavior needs a manual check because computer-control permission was unavailable. Flutter web accessibility semantics can leave unfocused inputs at framework-default autocomplete values until focused; assistive-technology/password-manager integration also needs a native browser audit. Details and release checks: docs/ux/auth-journeys.md.
Closes #56.
Deployment update (19 October 2026): merged into main as
30f06c2and rebuilt/recreated the local frontend only. Fresh stable base-image/Flutter pins, formatting, app analysis, all 212 frontend tests and the Docker frontend build passed. The replacement container is healthy, HTTPS returns 200, and the served JavaScript hash matches the new container and includes the autofill hint arrays. Running image: sha256:3bc4fcb9c469be29a160cd8a6951e1424098bf87e3ff31b255d1eec4ad04b78c. Native Safari popup verification remains manual; reload the page to use the new build. Detailed deployment evidence is recorded on task #56.