Console playground

The console playground mirrors the stitched split-pane concept: source dashboard on the left and bridge output on the right.

Layout model

• Left pane: target dashboard context for selector interactions.
• Right pane: structured logs, payload preview, and send status.

Recommended workflow

1. Pick a candidate selector in the source pane.
2. Inspect extracted raw value in event logs.
3. Verify transform output in JSON preview.
4. Send payload to MCP endpoint.
5. Confirm success or inspect error trace.

Typical event stream

[14:02:01] INFO: bridge initialized
[14:02:05] EXTRACT: #revenue .value -> "$45,289.00"
[14:02:05] TRANSFORM: revenue_metric -> 45289.00
[14:02:06] SENT: payload delivered to ws://localhost:8080/mcp

Failure modes and fixes

• Empty extraction:
  • Re-validate selector against current DOM state.
• Transform mismatch:
  • Check numeric, date, and currency parsers.
• Delivery failure:
  • Confirm endpoint availability and token scope.

Operational tips

• Keep one stable baseline payload for regression checks.
• Save representative logs for change reviews.
• Run dry mode before enabling write-side automations.