Morgen ignores the Obsidian Tasks plugin's NON_TASK status type when importing checklist items

I use the Obsidian Tasks plugin with custom statuses. Several of them are explicitly configured as type "NON_TASK" in the plugin's data.json for example:

{ "symbol": "i", "name": "information", "type": "NON_TASK" }

{ "symbol": "k", "name": "key", "type": "NON_TASK" }

These are meant to be informational sub-notes under a real task (e.g. a log line noting something I learned while doing the task), not tasks themselves. In Obsidian, the Tasks plugin correctly treats them as non-actionable.

Morgen, however, reads any markdown checkbox line ("- [i] some text", "- [k] some text") straight from the file and imports it as a real task — grouped in the sidebar under labels that match the status names ("information", "key").

This happens even though the line has no due date, no 🆔, and is a sub-item indented under another task. Screenshot attached showing "information" and "key" groups full of what are just log notes, not tasks.

Request: please read the Tasks plugin's customStatuses config (data.json) and skip any status whose "type" is "NON_TASK" when importing/scheduling from a vault. This would let Morgen coexist with the Tasks plugin's full status vocabulary instead of only the default checkbox states.

As example, that’s a photo of a task that i forwarded to tomorrow , i used the symbol “i” to information , to information to me why i forwarded that task… Both fowarded symbol and information is recognized as non tasks by obsidian, but morgen catch that.

Thanks!