Skip to content

Cloud Dev: JSONL event persistence #124

@gHashTag

Description

@gHashTag

Event stream as source of truth.

Tasks

  1. cloud_monitor.zig: restore state from .trinity/cloud_events.jsonl on restart
  2. Add tri cloud history --format=json for machine consumption
  3. Add event deduplication (skip if same status within 5s)

Files

  • tools/mcp/trinity_mcp/cloud_monitor.zig
  • src/tri/tri_cloud.zig

Verification

  • tri cloud history 42 shows events after monitor restart
  • No duplicate events within 5s window

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions