How to submit failing / unexpected transforms

I ran this on a project recently and hit a few types of failing or unexpected behavior. I don't know how best to iterate on this so I figured I'll submit a few steps & screenshots and we can decide split them into new tickets or whatever.

1. After working around #1, it ran successfully

2. but failed a lint check with 2 types of errors

3. The parsing error was due to this (note `import { "path/to/file" ...`)

4. The "restricted path" errors were because a transform lost a comment that was above it

After that, I went through the changes and found a found a few patterns of errors

Duplicate/repeated member imports

**Lost members**

Lost `import * as`

I'm not sure what correct behavior is for 4. It wasn't hard to fix, just pointing it out. That said, I don't understand this comment move

There might be 5-20 different examples for the lost import and duplicated members patterns. There might be some others, but let's start with these few. Let me know where and how best I can help and I'm glad to do it.

Thanks for this. Even with these issues it was still very useful.

No source file or test is named. Start by reproducing the reported TypeScript CLI transforms, then separate the parsing, restricted-path, duplicate-import, lost-member, lost namespace-import, and comment behaviors into distinct cases. Done means each case has clear expected and actual behavior suitable for a focused ticket.

Written by the indexing model from the issue text.