/newtask

[Keyrxng]

Resolves #32

this PR introduces the /newtask command which is used by bot admins to create new tasks in the correct repository.

Usage: /newtask ubiquity-os-marketplace/ubiquity-os-kernel-telegram

• The admin must reply to the message which they want to turn into a task spec
• They must include the repo.full_name after the command in order to open it in the correct repo
• Only admins are able to use this new command
• New tasks are currently opened under my alt account because the org secret APP_PRIVATE_KEY issue, no one has replied to me about it so I'm assuming it's still unresolved. It needs fixed ASAP.

QA: ubq-testing#9

Task creation comment:

The plugin DM interface needs to be standardized so that all plugins can easily use it to enable notifications for any reason.

Not just that but the logger can have a plugin built to enable it to be able to DM errors too. That feels like covering both the good and bad outcomes regarding notifications

[Keyrxng]

1. Using GPT to structure a proper spec.
2. Using Directives and Constraints to guide, please offer suggestions on improvements.
3. With embeddings I expect the specs to be more insightful and less generic.

Broke this into it's own PR and task via a task list, I think that's the right thing to do here. Once I get the embeddings data I can make moves on the other.

[Keyrxng]

I saw the thumbs up on the task to my comment so I'll take that as a go-ahead and I'll merge this today tomorrow.

I fell into a rabbit whole with the logger error debugging and stacks in gh comments trying various solutions, found a few will PR that and close this tmrw