fix(agent): bound SCADA presentation continuations

2026-11-12 12:22:07 +08:00
parent 0be30b80bb
commit f7e411c288
4 changed files with 27 additions and 2 deletions
@@ -38,6 +38,8 @@ Task chart windows are managed by the browser in one parent window containing pr

 Task open_chart requires persisted evidence references. Task set_overlay can omit data; Server resolves immutable evidence into bounded GeoJSON. Supplied data must match that resolution and never overrides the stored snapshot. Chat and Dev supply resolved data for structural validation before rendering.

+If Server rejects completion with `SCADA_PRESENTATION_INCOMPLETE`, the host may resume the same investigation up to three times within the current response to publish the missing charts. Further rejection follows the existing explicit run-failure path; heartbeats must not keep an endless sequence of extra model turns alive. Permission, transport and other completion failures do not trigger this continuation.
+
 Same-time-of-day current/history comparisons use `chart_type=time_comparison`; ordinary charts retain `line` or `bar`. The comparison axis contains shared UTC+8 `HH:mm` or `HH:mm:ss` slots, with current `line` and historical `scatter` series and aligned real `sample_times`. The Server automatically validates new task presentation and report chart publications, rejecting date-appended axes, missing timestamps, misplaced points and nonhistorical reference dates with `TIME_COMPARISON_INVALID`. Chat open_chart is checked by both the native tool and host coordinator using the same generated chart refinement as task publication; Dev commands and ui_block.Chart use it too. Ordinary line/bar charts skip comparison semantics, but a line/scatter comparison cannot be labelled line. Historical stored chart read contracts remain unchanged.

 Chat, task following and Dev previews share the frontend command dispatcher but own independent map sources, SCADA layers and chart state. Clearing or switching one owner does not clear another. Dev JSONL is an explicit local preview/import/export container, not an alternative online business protocol. Plain data records and ui_block records do not execute embedded actions. The earlier agent-ui@1 registry has no active tool mappings and is not an action entry point.