3 Commits

Author SHA1 Message Date
eust-w
d4c768475b ✨ Switch login to phone-based lookup (ticket 03)
- handleAuthLogin now authenticates via store.FindUserByPhone instead of
  FindUserByEmail; the login/bootstrap-super-admin request payload field
  is now `phone`. Old email addresses are no longer valid login credentials.
- bootstrap-super-admin now validates phone format (isValidChinaMobilePhone)
  instead of net/mail.ParseAddress; net/mail is fully removed from
  internal/api.
- Same-class gap fix: handleAdminOrganizationUsersCreate (the legacy
  per-organization admin endpoint, not touched by ticket 02) still created
  users by email only, which would have left them unable to log in under
  the new phone-only login. Switched it to phone validation/uniqueness too,
  and removed the now-dead normalizeUserInput/validateUserEmailAvailable
  helpers.
- Frontend: authApi.login, UserContext's login signature, and
  UserBootstrapPanel's submit handler now send `phone` instead of `email`
  (the form/labels were already phone-based from ticket 04).
- Updated ~20 Go test files whose fixtures/helpers logged in via
  user.Email; adminCreateUser/loginSession/bootstrapSuperAdminSession now
  work in terms of phone (deterministically derived from existing
  email-shaped test identities via testPhoneFromSeed, to avoid rewriting
  every call site). Added internal/api/auth_phone_login_test.go covering
  phone login success/failure and old-email rejection.

go test ./internal/api/... and npm run test:frontend match their
pre-ticket baselines exactly (75 Go failures / 599 frontend tests with
586 pass, 13 fail) by failing test name, not just count.
2026-09-22 14:04:59 +08:00
eust-w
a343c5a37f 🐛 Fix multipart PTS pairing, safe moves and rework feedback 2026-09-06 10:06:52 +08:00
eust-w
0c163203ed 🛠️ fix: large-object-safe BOS moves with progress, prechecks, and capture-conflict guard
- MovePrefix/RenameObject now copy objects larger than the 5 GB BOS
  simple-copy limit via multipart part copy (preserving Content-Type and
  user metadata), with per-object rollback that only removes
  destinations created by the move itself
- MovePrefix reports per-object progress for async tracking
- directory moves and deletes guard against capture-automation watched
  prefixes with an explicit force confirmation (409
  capture_automation_conflict)
- move precheck rejects no-op destinations and parent/child overlapping
  selections with actionable error codes instead of a bare validation
  failure
- new POST/GET /api/object-storage/move-jobs async move jobs with
  progress polling so large directory moves survive HTTP timeouts
- frontend object browser surfaces validation issue details, uses the
  async move job for directory moves, and asks for force confirmation
  when a capture automation watches the affected prefix
2026-09-04 15:34:55 +08:00