The roadmap deepens the accepted Scoped Evidence Workspace. It does not recreate separate feature destinations, and it does not promise dates.
Next
Normalized JSON Evidence console
Present each retained row as one deterministic normalized Workbench Evidence object while preserving retained order, bounded rendering, Find, Filter, selection, and semantic Context.
Contextual narrowing and value inspection
Add click-to-narrow facets and make changed fields, Update Deliveries, provenance, JSON Patch evidence, and value ambiguity easier to inspect without opening raw capture.
Runtime diagnosis that reaches conclusions
Correlate connection recovery, Session epochs, snapshot bootstrap, subscription configuration, server errors, keepalives, loss signals, and evidence-based linting inside the existing Context and diagnostic boundaries.
Captured Client Messages and deliberate Server Injection
Capture LightstreamerClient.sendMessage calls and listener outcomes as outbound Evidence. A reviewed Server Injection will send once through the inspected client's normal message path. It will not directly create an inbound Item Update, prove a downstream business effect, or retry an unknown outcome automatically.
Deterministic multi-event Local Injection Scenarios
The explicit-membership, single-target, immutable-Run Scenario workflow is implemented and package-verified in the source tree. Public availability follows the maintainer-controlled Chrome Web Store release process; package verification does not mean the candidate is published.
Exploring
- Capture import, offline investigation, fixture generation, and cross-capture comparison.
- Listener performance, client-log, protocol, frequency, bandwidth, buffer, and loss diagnostics.
- Broader frame, worker, transport, and bundled-client observation coverage.
- Guarded live tuning and specialized Mobile Push Notification tooling.
These are product opportunities, not release commitments. Scope and ordering may change as real investigation evidence accumulates.