toki
bebd95f909
validate-agent-ui 규칙이 요구하는 상태값 스키마에 맞춰 기존 code-first agent-ui 문서의 legacy 상태 표기를 정규화한다.
70 lines
1.6 KiB
Markdown
70 lines
1.6 KiB
Markdown
---
|
|
ui_doc_type: component
|
|
component_id: event-log-entry
|
|
status: 구현됨
|
|
source_evidence:
|
|
- type: code
|
|
path: apps/client/lib/widgets/execution_logs_panel.dart
|
|
notes: ExecutionLogsPanel renders event entries with type color/icon, reason, node/source, and timestamp.
|
|
- type: docs
|
|
path: README.md
|
|
notes: Edge aggregates execution history and lifecycle events.
|
|
- type: user
|
|
path: null
|
|
notes: Initial scaffold requested by user.
|
|
---
|
|
|
|
# Event Log Entry
|
|
|
|
Component ID: `event-log-entry`
|
|
|
|
Status: `구현됨`
|
|
|
|
## Source Evidence
|
|
|
|
| Type | Path | Notes |
|
|
|------|------|-------|
|
|
| code | `apps/client/lib/widgets/execution_logs_panel.dart` | event list builder, `_getEventColor`, `_getEventIcon`이 entry pattern을 구현한다. |
|
|
| docs | `README.md` | Edge lifecycle event aggregation 방향을 설명한다. |
|
|
| user | 없음 | 초기 agent-ui 생성을 요청했다. |
|
|
|
|
## Purpose
|
|
|
|
단일 lifecycle event를 severity, reason, source, time 기준으로 읽기 쉽게 보여준다.
|
|
|
|
## Used By
|
|
|
|
- `execution-logs`: `execution-logs.event-list`, `execution-logs.event-entry`
|
|
|
|
## Anatomy
|
|
|
|
- severity icon
|
|
- event type label
|
|
- timestamp
|
|
- reason text
|
|
- node alias/id or Edge System
|
|
- optional source
|
|
|
|
## Variants
|
|
|
|
- error/failed
|
|
- warning/warn
|
|
- success/connected/online
|
|
- info/default
|
|
|
|
## States
|
|
|
|
- default
|
|
- loading: view-level state
|
|
- empty: view-level state
|
|
- error: view-level state
|
|
- disabled: 없음
|
|
|
|
## Rules
|
|
|
|
- event type drives color and icon.
|
|
- node identity falls back to `Edge System` when node id and alias are empty.
|
|
|
|
## Decision History
|
|
|
|
- 2026-06-25: `ExecutionLogsPanel`의 event entry pattern을 component로 정의했다.
|