Why was Multi-Account Auth introduced in PR:85 and then removed in PR:253 in just over a day

[shankscoder]

As per this issue: #293

This feature was added to gws in this PR: #85

But it was then removed within a day or so in this PR: #253

Multi-account auth is a really useful feature for wide variety of use-cases, and I'm curious why it was removed after being added.

Some clarity would be useful to understand the thinking behind the decision to remove.

Thanks.

[aniruddhaadak80]

From my point of view, a feature like multi-account auth usually gets reverted when the state model is not stable enough rather than because the use case is unimportant. If it was introduced and removed that quickly, a short explanation of what went wrong would help users understand whether the blocker was security, UX complexity, token storage, or maintainability.

Even a noncommittal roadmap note would be better than silence, because this is one of those features people build their workflow around.