Action Flows: implement INPUT/DIALOG/REDIRECT/CALL/CUSTOM step renderers on the Vue side

[marioserrano09]

Summary

Part of #79.

runActionFlow (platform/packages/vue/src/actions/runActionFlow.ts) only renders CONFIRM and NOTIFY flow steps. INPUT, DIALOG, REDIRECT, CALL, and CUSTOM all hit:

throw new Error(`runActionFlow: no renderer wired yet for flow step type "${step.type}"`);

Problem

Any FlowRemoteAction that returns one of these step types fails hard on the Vue side today. This is real missing functionality, not just an unimplemented "future work" note — §1's core motivating scenarios (multi-step wizards, "pick one of three", entity-editing dialogs) need DIALOG/INPUT at minimum.

Proposed work

• INPUT: a prompt primitive (composable + component), same shape as useConfirm.
• DIALOG: render step.viewDescriptor as a <DynamiaForm> inside <DynamiaDialog>, collect and submit the whole form as the answer — this is the one explicitly called out in the design doc as reusing the existing YAML view-descriptor system (§2 constraint: "no new form-description language").
• REDIRECT/CALL: pin down the semantics first (see Server-Driven Action Flows for RemoteAction #79's tracked open question — does the client resume the same flow after a redirect/nested call, or are these always terminal?) before implementing the renderer.
• CUSTOM: a client-registered step-renderer registry, parallel to the existing ClientActionRegistry (platform/packages/ui-core/src/actions/ClientAction.ts), keyed by data.component.

References

• platform/packages/vue/src/actions/runActionFlow.ts
• docs/design/SERVER_DRIVEN_ACTION_FLOWS.md §3, §6, §9

[marioserrano09]

`CONFIRM`/`NOTIFY`/`INPUT`/`DIALOG`/`CUSTOM` are now all wired on `feature/action-flows` (commits bfca871, 8dafa1d, 7f13881):

• INPUT → `PromptManager` (ui-core, mirrors `ConfirmManager`) + `useInput()`/``.
• DIALOG → `runActionFlow` fetches `step.viewDescriptor` for the request's `dataType` via `client.metadata.getEntityView`/`getEntity`, builds and prefills a `VueFormView` from `step.data`, hands it to `useFormDialog()`/`DialogFormManager` + `` (renders as `` inside ``).
• CUSTOM → `FlowStepRendererRegistry`/`registerFlowStepRenderer` (ui-core), keyed by `step.data.component`, same shape as `ClientActionRegistry`.

Mounted in `theme-dynamical-vue`'s `App.vue` alongside the existing confirm/toast hosts, with matching styles. `ui-core` unit tests added (`PromptManager`, `FlowStepRendererRegistry`); `typecheck`/`build` clean for both `ui-core` and `vue`.

Left open on purpose: `REDIRECT`/`CALL`. Their semantics (does the client resume the same flow after a redirect/nested call, or are they always terminal?) are still undecided — implementing a renderer ahead of that would bake in an answer by accident. This needs a real use case to settle, per the design doc's §9. Keeping this issue open, scoped down to just that remaining gap.

Pending: PR against `main`.

[marioserrano09]

Verificado end-to-end contra theme-dynamical-vue (rama feature/action-flows, sin commitear aún) — hasta ahora INPUT/DIALOG/CUSTOM solo tenían tests unitarios del lado cliente, ningún FlowRemoteAction real los había ejercitado.

Setup: examples/demo-zk-books ahora también depende de tools.dynamia.themes.dynamical-vue (además de dynamical), con un profile Spring vue (dynamia.app.template=DynamicalVue) para arrancar con el theme Vue sin tocar el demo ZK por defecto.

3 FlowRemoteAction nuevos en mybookstore.actions, uno por cada step type sin cobertura real:

• ApplyDiscountAction — INPUT (pide % descuento, aplica onSale/discount/salePrice)
• QuickEditPricingAction — DIALOG (reabre el "form" descriptor de Book prefilleado)
• RateBookAction — CUSTOM (componente "star-rating", registrado vía registerFlowStepRenderer solo en theme-dynamical-vue, no en ui-core/vue — es el escape hatch app-specific)

Para CUSTOM hizo falta un manager+host nuevo en el theme (starRatingManager.ts + StarRatingHost.vue), mismo patrón que PromptManager/PromptHost pero deliberadamente fuera de ui-core.

Verificación: sin extensión Chrome disponible en esta sesión, se verificó el protocolo completo por HTTP directo contra ApplicationMetadataController (start → resume con resumeToken, los 4 step types: CONFIRM regresión + INPUT/DIALOG/CUSTOM nuevos) — los 4 flows completan a DONE con el resultado esperado. Frontend (pnpm build/vite build) compila limpio con el nuevo StarRatingHost.

Hallazgos menores, no bloqueantes:

1. themes/theme-dynamical-vue/sources/pom.xml tenía el <parent><version> en 26.7.0 mientras themes/pom.xml ya está en 26.8.0 (drift desde el commit que agregó el theme) — corregido.
2. ApplicationMetadataLoader arma el campo informativo endpoint de las entity actions con /actions/{id} (plural) pero el @PostMapping real es /action/{id} (singular) — el SDK no usa ese campo (hardcodea la ruta correcta), así que es cosmético, pero vale una issue aparte si alguien lo llegara a consumir.

REDIRECT/CALL siguen sin implementación — eso no cambia con esto, sigue siendo el único gap real de #81.