Add Warp UI adapter for observability endpoints

[alob-mtc]

Summary

Add support for Warp as an alternative HTTP framework for the observability UI endpoints.

Context

The observability UI module has been refactored to be framework-agnostic (see src/observability/ui/). Currently, only Axum is supported via the axum-ui feature flag. This issue tracks adding Warp support.

Requirements

• Create src/observability/ui/warp.rs with Warp filters
• Add warp-ui feature flag in Cargo.toml
• Update src/observability/ui/mod.rs to conditionally export Warp routes
• Implement the following endpoints:
  • GET / - Serve console HTML
  • GET /stats - Queue statistics
  • GET /activities/:key - List activities by status or get by ID
  • GET /activities/:id/events - Activity event history
  • GET /activities/:id/result - Activity result
  • GET /dead-letter - Dead letter queue listing
  • GET /stream - SSE event stream
• Add example demonstrating Warp usage
• Update documentation

Technical Notes

• Use warp crate
• SSE can be implemented using Warp's built-in warp::sse module
• Follow the same pattern as src/observability/ui/axum.rs
• All data operations should go through QueueInspector

Feature Flag

[features]
warp-ui = ["dep:warp"]

Related

• Axum implementation: src/observability/ui/axum.rs
• Static HTML: src/observability/ui/html.rs

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Add Actix-web UI adapter for observability endpoints #61

👤 Suggested Assignees

• alob-mtc

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!