convex-monitor

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Watch for the next thing to react to

监控下一个需要响应的事件

Block on the next typed event instead of polling. Races local error logs, deployment subscriptions, and Sentinel prod-error rows; returns the first to fire (or a quiet heartbeat).

阻塞等待下一个类型化事件，而非轮询。同时监听本地错误日志、部署订阅和Sentinel生产环境错误记录；返回第一个触发的事件（或静默心跳）。

Workflow

工作流程

Call
```
wait_for_event
```
with {project_dir, event_kinds, timeout_ms}.
On kind=convex_error/next_error: decode and fix it. On kind=prod_error: triage (see sentinel) and fix. On kind=feature_request: build it. On kind=quiet: loop.
Where a harness has no blocking MCP (e.g. Copilot cloud), the pack runs a poll loop with the SAME event contract — same behavior, different mechanism.

使用参数 {project_dir, event_kinds, timeout_ms} 调用
```
wait_for_event
```
。
当类型为convex_error/next_error时：解码并修复错误。当类型为prod_error时：分类处理（参考Sentinel）并修复。当类型为feature_request时：开发该功能。当类型为quiet时：循环执行。
若工具没有阻塞式MCP（例如Copilot云），则该套件会运行一个轮询循环，遵循相同的事件约定——行为一致，机制不同。

Rules

规则

Prefer the blocking tool; fall back to a poll loop only where blocking MCP is weak.
The event schema is fixed and versioned — the same trigger yields the same typed event.
Prod events (kind=prod_error) require a deployed cloud app plus Sentinel.

优先使用阻塞工具；仅当阻塞式MCP不可用时才回退到轮询循环。
事件模式是固定且版本化的——相同的触发器会生成相同的类型化事件。
生产环境事件（类型为prod_error）需要已部署的云应用及Sentinel。