8000 T2 — Write each box's lifecycle events where only the daemon can reach · Issue #2389 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content
8000

T2 — Write each box's lifecycle events where only the daemon can reach #2389

Closed

Description

@mitodrummer

Task

slice size difficulty model who estimated lines
Retained sessions L needs care strongest an agent 760 (380 code, 380 tests)

A box's events read back in order, and follow tails.

Covers:

  • BOX-040
  • BOX-041
  • BOX-162

Layers:

  • events:
    • crates/boxes/src/events.rs (new): event type
    • crates/boxes/src/lib.rs: mod line
    • crates/boxes/src/store.rs: per-record events file
    • cargo nextest run -p boxes events_file_appends_in_write_order
  • daemon:
    • crates/minimald/src/box_manager.rs: created event; read and follow
    • crates/minimald/src/box_manager/tests.rs: tests
    • crates/minimald/src/rpc.rs: events read handler
    • crates/minimald/src/diag.rs: copies events file
    • cargo nextest run -p minimald events_written_outside_box_filesystem_with_box_parent_ts_type
    • cargo nextest run -p minimald in_box_root_cannot_append_events
    • cargo nextest run -p minimald events_read_returns_full_retained_stream_in_order
    • cargo nextest run -p minimald events_follow_replays_then_tails_until_reaped
  • wire:
    • crates/minimald-rpc/src/lib.rs: events read request
    • cargo nextest run -p minimald-rpc read_events_request_round_trips

Waits on:

Plan block
### T2 — Write each box's lifecycle events where only the daemon can reach
  slice: S0
  kind: task
  covers: BOX-040, BOX-041, BOX-162
  size: L
  est: 380 code, 380 tests
  executor: agent
  difficulty: needs care
  model: strongest
  diagnostics: state collection copies events; daemon log names refusals
  observability: one log line per event written
  layers:
    - events:
      - crates/boxes/src/events.rs (new): event type
      - crates/boxes/src/lib.rs: mod line
      - crates/boxes/src/store.rs: per-record events file
      test: cargo nextest run -p boxes events_file_appends_in_write_order
    - daemon:
      - crates/minimald/src/box_manager.rs: created event; read and follow
      - crates/minimald/src/box_manager/tests.rs: tests
      - crates/minimald/src/rpc.rs: events read handler
      - crates/minimald/src/diag.rs: copies events file
      test: cargo nextest run -p minimald events_written_outside_box_filesystem_with_box_parent_ts_type
      test: cargo nextest run -p minimald in_box_root_cannot_append_events
      test: cargo nextest run -p minimald events_read_returns_full_retained_stream_in_order
      test: cargo nextest run -p minimald events_follow_replays_then_tails_until_reaped
    - wire:
      - crates/minimald-rpc/src/lib.rs: events read request
      test: cargo nextest run -p minimald-rpc read_events_request_round_trips
  produces:
    - crates/boxes/src/events.rs
  consumes:
    - crates/boxes/src/core/record.rs
  proof: A box's events read back in order, and follow tails.
  depends on:
    - blocked by #2387

Activity

  1. added
    kind:taskA task the plan skill rendered; the body carries ## Task
    size:L500 to 900 net lines; one PR, and the ceiling
    model:strongestThe strongest model available: unknown ground, or large work that needs care
    on Oct 19, 2026
  2. minimal-foundry commented on Oct 27, 2026

    @minimal-foundry
    Contributor

    Done. #2654 merged.

    branch agent/2389-write-each-box-s-lifecycle-events-where-only-the · epic #2236 · PR #2654

    round outcome job
    1 pushed a4b5ddef
    2 pushed 4bf78c56
    3 pushed e45ba09a
    4 pushed 06fc96c2
    5 pushed 5a466278

    Updated 2026-10-27T17:15:22.518Z.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind:taskA task the plan skill rendered; the body carries ## Taskmodel:strongestThe strongest model available: unknown ground, or large work that needs caresize:L500 to 900 net lines; one PR, and the ceiling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0