Having the `a-Shell` app register itself as an editor for files leads to major disturbances in the whole `Files` app

### Background

Apple's `Files` app will remember when you used `share` to open a file in a specific app, and will use that app from now on automatically when you tap a file of the same type.

But if you tap a file inside an app's (local) directory, it will first see if the app owning the directory can open that file type.

- If it can't open the app it will use the existing default.
- If it can it will open it in that app and from now on use it as the default app for that file type.

### Issue

`a-Shell` appears to register itself as an editor for `.md` and `.sh` files (and I'm assuming a whole bunch more like `.(c)js`, `.py`, etc.), so when you're trying to edit such a file located in the app's (local) directory you'll be greeted by `a-Shell` opening the file in `vim`, and from now on `Files` will open that file type, *regardless of where it's located*, in `a-Shell` in `vim` by default.

I *really* don't want that to happen. I will never want to open a markdown file in `vim`, nor do I want to use any terminal-based editor for any local file when I'm not actually currently using the terminal.

### Question

So is that meant to be exactly like that, or was the app just made to register itself for a bunch of file types without considering this behavior?
I find this behavior extremely disruptive and unintuitive, and I would very much prefer to not have it.

### Details

Os: iOS 18.5 (22F76)
Vs: 1.15.12 (459); a-Shell mini