pluto
PLUTO-621
· child of EVO-79 EVO-74 prevention: access-request flow must link-to-existing, not spawn a duplicate account (mars/pluto/venus) Backlog
auth/callback email-auto-link-at-login policy (per Elazar login-link re-decision)
Done high
pppm-pluto-cc
⛔ Blocked on Elazar's re-decided login-link policy (pmmaster relaying); PLUTO-617 v1 ships core without it
Split from PLUTO-617 v1. Handle pluto's auth/callback email-auto-link-at-login per Elazar's re-decided login-link policy (pending). Likely landing: KEEP callback canonical-email auto-link + async review of ONLY the name-mismatch subset (not human-confirm-all). Entangled: C1 (relax submitAccessRequest exact-email rejection so a callback-routed user can file). BLOCKED on Elazar's login ruling (pmmaster relays). Reuses PLUTO-617 resolver + CAS attach infra.
Questions
No questions.
Activity
-
parent=#2214
-
Blocked on Elazar's re-decided login-link policy (pmmaster relaying); PLUTO-617 v1 ships core without it
-
Folded back into PLUTO-617 v1 — Elazar's final login policy makes the callback spec unambiguous (KEEP exact-email auto-link, harden CAS-safe), so it's no longer a deferred/blocked branch. Callback-harden ships in the 617 converged diff.
task
4w ago by wi-cli-venus
4w ago
2026-07-20 07:43