Action tabs within rule edit page

This post is definitely like one of those, if I had more time, I would have said less. But this info is related and will be useful later.

>> action tabs when editing a rule / component: edit, clone, execute, schedule, export
I think you could either be referring to actions on the rule/component itself or its (E,C,A) contents.

I see what you mean about including more operators than [edit] and [delete] for the (ECA); and/or for the rule/component only having [enable/disable] in the lower settings fieldset. But, I'm also looking for a bit of a different solution for this.

I'll respond to each of the operations you mentioned in groups. Each of them are applicable to both rule/component editing as well as e,c,a editing, except for schedule and execute.

Clone and import:
These are very different from the other ones and possibly each other. Clone is, as far as I can tell, so far, a more basic implementation of converting single instances to a set of those instances, see #1495718: Add option to convert a set of conditions or actions to a component, as well as a less robust views-like:configuration/display/override.

Import / export:
These have a couple of problems: one is that it's performing functions meant for the developer, resulting in using/maintaining weaker tools. The API is designed for coders to code against, and the copy/paste config text blobs are a major afterthought. Plus it's bloat for the interface that already needs a great effort on simplification. See #1496184: Factor out import/export ui elements to a sub-module

Edit:
Almost always, it's the same thing as clicking on the title. So, it's unlikely that this will be necessary.

Schedule and execute:
These a wholly different group. I see them as "reactions" in the same sense that they are all configured events or sets of configured events that represent the binary yes of "execute?". They are all configured.. either with one click (execute), a couple of clicks (selecting an event), or a few clicks (planning a delayed response in relation to a selected event).

I've started on some wireframes of this at #1496256: Overview page: Interlinked Design, which also includes some other ideas.