Open Loop: drive the domain loop as a run phase

[suleimansh]

Follow-up to the framing+bridge issue (part of #204).

Once a run exposes a driver-backed domain LoopEngine, actually run it (dispatch major-change / bug-fix events so the domain's review chain fires through the driver).

OPEN DECISION for @brillout: does the domain loop REPLACE the Bootstrap production-grade checklist, run AFTER it as a domain review, or interleave? These are two different loops today (Bootstrap checklist vs the Open Loop event->chain). Deciding this is the point of this issue.

[brillout]

If possible, I'd say that "boostrap" is just a preset? Is that possible or would it introduce a limitation?

[brillout]

If possible, I'd say that "boostrap" is just a preset? Is that possible or would it introduce a limitation?

(As always, feel free to let me know if you want more input from me.)

[suleimansh]

Partly yes. The review loop can be a preset. bootstrap's checklist already returns { blockers }, which is exactly what the Open Loop engine gates on. So let's make the built-in checklist the default loop, and let a preset swap it. That also settles this issue: the domain loop replaces the checklist.

The rest (architect, deploy, prototype/full) can't easily be a preset yet. They return structured data the dashboard and real deploy need, while a preset only holds prose prompts today.

So: presets own the review loop now, keep architect/build/deploy as the spine. Good with that?

[brillout]

Sounds good. (We can experiment as we go what we want to be hardcoded via code, or just loose and slightly-less-efficient prose prompts.)