Projection Restart action does nothing (no command sent, UI state unchanged)

[erdtsieck]

Summary

On the projection detail page, clicking Restart shows a confirmation dialog, but confirming it has no observable effect. No backend command appears to be sent and the UI state does not change.

Steps to reproduce

1. Open a projection detail page, e.g. /projections/Zorgdeclaraties/claim_lines:V9:All.
2. Click the Restart button.
3. A confirmation dialog appears: "This will restart claim_lines. Continue?"
4. Click Restart to confirm.

Expected

• A command/request is sent to the backend to restart the projection shard.
• The projection State reflects the restart (e.g. transitions through a running/active state).

Actual

• Nothing observable changes after confirming.
• State remains Orphaned.
• Mode remains Continuous.
• Current Sequence is unchanged.

Technical detail

• Network: No REST/API request is fired when confirming the Restart action (verified by inspecting the network tab during the action).
• Console: No errors are logged. Only unrelated Element Plus deprecation warnings are present (el-radio label, el-link underline).

Related

Same root cause as the Pause action (#18) and the Rebuild action — none of the three projection action buttons issue a backend command.

[jeremydmiller]

Restart now issues and applies against registered shards.

Root cause: the targeted shard had no live Wolverine agent (State Orphaned/non-running), so agent resolution returned null and the handler silently returned — no command effect, no error. This was agent-resolution behavior, not a licensing problem.

Fixed by, in combination:

• WolverineFx 6.12.0 (Document + test that FindAgentUriAsync resolves registered (not just live) projection shards (#3124) wolverine#3126) — FindAgentUriAsync now resolves shards from the registered subscription set, not just live agents, so a registered-but-not-running projection is actually targeted (commit d0944ef4).
• Result surfacing to the SPA (commit efd53dd3) — the action now reports its outcome to the UI instead of being silently swallowed.
• License-gated controls (PR #475, commit 1394fce8) — the action buttons are disabled without a license (with an explanatory tooltip) and the handlers throw LicenseRequiredException rather than silently no-op'ing, closing the other path that could look like "nothing happened."

Residual case tracked separately: a truly orphaned shard — a progression row with no registered projection at all (e.g. a renamed/versioned projection) — still can't be Paused/Restarted/Rebuilt because there is nothing live to act on. The proper remediation (an "Eject Shard" action + reconciliation of stale orphaned shards) is tracked in #22 for the next release cycle.

Closing as resolved.