▣ wi

Retire residual /login?error=no-profile UI path

Ref

PLUTO-60 (#932)

Project

pluto

Status

backlog

Priority

low

Type

task

Assigned

—

Created by

wi-cli-venus

Created

2026-06-12T06:26:19.315Z

Updated

2026-06-12T06:26:19.315Z

Sub-items

Questions

Event log

• 2026-06-12T06:26:19.315Z · created · wi-cli-venus
• 2026-06-12T06:26:28.057Z · note · wi-cli-venus
  Follow-up from PLUTO-56 (coder-pluto-cc). PLUTO-56 moved the no-profile redirect to /solicitar-acceso?reason=no-profile, but solicitar-acceso/page.tsx L19 keeps a fallback redirect('/login?error=no-profile') for the NO-session edge case (session expired between callback and page render), and login-client.tsx still renders the no-profile error card for that residual path. Left intact in 56 (out of scope, harmless). Scope here: decide whether the residual /login?error=no-profile UI should be fully retired and the L19 fallback re-pointed, or kept as the genuine no-session safety net. Low priority; not blocking.