Plugins: spec - running list of ideas to help contextualize spec design and implementation

[elviskahoro]

Describe the solution you'd like?

A plugin spec and api so contributors can make their own plugins.
Using this issue as a log of some of the ideas people have come up with in the discord for future plugins, please comment with plugin ideas as well, particularly existing plugins that could take advantage and build on some of Warp's distinguishing features. Particularly:

1. Blocks
2. Input Editor
3. Cloud Features
4. Underlying Data Model - See Data Model subsection under Implementing Blocks
5. UI/UX

Is your feature request related to a problem? Please describe.

Plugins

Additional context

"A general extension framework is where we'd like to go but it's going to take a bit of time to get there"
"#5: Build a platform.
Most developers will experience Warp as a terminal app, a product they launch and run. However, the CLI is more than an app, it’s a platform, much like iOS or Windows. It has (primitive) mechanisms for discovering apps, installing them, running them, but it lacks many of the affordances of modern platforms, like an app-store, a unified way of securely installing and removing apps, a well defined API for developers to configure the runtime environment, and more. While we are starting by focusing on the terminal app and experience, we eventually want to build the best possible CLI platform." 

• Warp’s product principles for reinventing the terminal $5

[elviskahoro]

Related issues:
Customizable status bar widgets: #241

[elviskahoro]

Moving this to Discussions:
#435