Visualize continue-as-new chains and stalled recovery

[ccarvalho-eng]

Problem

Continue-as-new will make one logical recurring workflow span multiple bounded Squidie runs. Squid Sonar currently presents child and replay context, terminal status, timeline, graph, and anomalies for one run, but operators would not be able to follow continuation lineage or distinguish a healthy rollover from a continuation stalled between its durable fence, predecessor terminalization, and successor exposure.

Proposed Solution

After Squidie issue agentjido/jizoku#401 exposes continuation lineage and recovery diagnostics through public read models:

• Treat :continued as a terminal status in dashboard filters and summaries.
• Add a continuation card on run detail pages with linked predecessor and successor run IDs, continuation key, and definition identity.
• Provide a bounded, paginated chain view that does not recursively load an unbounded history.
• Surface an operator-safe warning when public diagnostics report a continuation awaiting predecessor or successor repair, or a conflicting continuation identity.
• Keep raw dispatch facts and hidden input out of the UI; use Squidie visibility-redacted inspection, explanation, and timeline data.
• Add fixtures and LiveView coverage for healthy chains, missing neighbors, long chains, visibility redaction, and conflict diagnostics.
• Exercise the feature through a recurring workflow in the sample host application.

Alternatives Considered

• Rely only on the existing timeline and anomaly list. This makes navigation across fresh run histories difficult and does not explain a stalled rollover.
• Load the complete chain recursively on every run detail request. This is unsafe for indefinite workflows and conflicts with Squidie's bounded-inspection requirement.
• Read journal or dispatch storage directly. This would couple Squid Sonar to internal persistence contracts and bypass Squidie's visibility boundary.

Additional Context

This follows agentjido/jizoku#401. Implementation should wait for Squidie's public continuation lineage and recovery-diagnostic shape rather than depending on the internal :run_continuation_fenced fact.