WindowPromptHost

The prompt-host window-feature (§ACW-7.5, W7 slice 3).

In the namespace octomy::window. Declared in src/libs/libwindow/window/WindowPromptHost.hpp.

Detailed description

A window asks the person a question with a MessagePromptActivity on its activity stack, and receives the answer in a callback, matched by the prompt id. This is Activity::pushPromptForResult for a window. Both use the same octomy::activity::PromptResultRouter.

Why it exists

NodeWindow pushed eight prompts by hand. Each site that needed the answer connected to ActivityStack::activityPopped and matched the id itself. The quit prompt had a member slot for it. The startup-failed retry had a listener that stayed connected for the life of the window. The owner chose option 2 of §ACW-7.5 on 2026-10-11: one feature that pushes, routes the answer by id, and refuses when there is no stack.

Where the stack comes from

The host supplies a stack provider, and this feature calls it on each ask(). It does not keep a stack. NodeWindow can replace its stack host (setActivityStack), so a stack captured at construction can be the wrong one or a destroyed one.

Dependencies

libactivity only, so the libwindow leaf stays clean. The feature pushes the activity by NAME. It does not include MessagePromptActivity, which lives in libwidgets.

Note: §ACF-5 classification: **GLUE**. No lifecycle tier, no Node.