8000 T46 — Name a new box from its entry, refuse a held name, number a fresh one · Issue #2400 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

T46 — Name a ne 8000 w box from its entry, refuse a held name, number a fresh one #2400

Closed

Description

@mitodrummer

Task

slice size difficulty model who estimated lines
Names follow the id L needs care strongest an agent 620 (260 code, 360 tests)

A second dev is refused; a fresh run gets dev-1.

Covers:

  • BOX-163

Layers:

  • spec:
    • crates/mfile/src/spec.rs: box name, else entry
    • cargo nextest run -p mfile spec_names_box_from_box_name_else_entry
  • daemon:
    • crates/minimald/src/box_manager.rs: held-name refusal; fresh suffix
    • crates/minimald/src/box_manager/tests.rs: tests
    • cargo nextest run -p minimald create_names_box_from_box_name_else_entry
    • cargo nextest run -p minimald create_with_name_held_by_running_box_refused_exit2_names_holder
    • cargo nextest run -p minimald fresh_instance_creation_named_smallest_unused_suffix
  • vm-host:
    • crates/minvmd/src/box_registry.rs: reuse takes over hold
    • cargo nextest run -p minvmd reuse_of_a_stopped_name_takes_over_its_hold

Split by the maintainer (2026-10-30): the client half of BOX-163 lives in files outside this task's layers (create.rs, task.rs, dash/rpc.rs, box_registration.rs and more), so it moved to T58 #2762, which waits on this task. This task delivers BOX-163 inside the daemon, the VM host and the spec.

Waits on:

Plan block
### T46 — Name a new box from its entry, refuse a held name, number a fresh one
  slice: S3
  kind: task
  covers: BOX-163
  size: L
  est: 260 code, 360 tests
  executor: agent
  difficulty: needs care
  model: strongest
  diagnostics: daemon log names holder or suffix
  observability: create span carries name given
  layers:
    - spec:
      - crates/mfile/src/spec.rs: box name, else entry
      test: cargo nextest run -p mfile spec_names_box_from_box_name_else_entry
    - daemon:
      - crates/minimald/src/box_manager.rs: held-name refusal; fresh suffix
      - crates/minimald/src/box_manager/tests.rs: tests
      test: cargo nextest run -p minimald create_names_box_from_box_name_else_entry
      test: cargo nextest run -p minimald create_with_name_held_by_running_box_refused_exit2_names_holder
      test: cargo nextest run -p minimald fresh_instance_creation_named_smallest_unused_suffix
    - vm-host:
      - crates/minvmd/src/box_registry.rs: reuse takes over hold
      test: cargo nextest run -p minvmd reuse_of_a_stopped_name_takes_over_its_hold
  produces: none
  consumes:
    - crates/mfile/src/spec.rs
  proof: A second dev is refused; a fresh run gets dev-1.
  depends on:
    - blocked by #2396
    - blocked by #2388

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 30, 2026

    @minimal-foundry
    Contributor

    Done. #2760 merged.

    branch agent/2400-name-a-new-box-from-its-entry-refuse-a-held-name · epic #2236 · PR #2760

    round outcome job
    1 changed nothing: Revise round 1: this round changed no code. I judged the one thread as invalid (see threads). Client layer not done: BOX-163 asks the client to stop inventing a '-' name. crates/minimal-clie 2d108f59
    2 pushed 8137bbd5
    3 pushed 4cd1077b
    4 pushed 38e27f57
    5 pushed 60c76a7c
    6 pushed 91bf1d6c

    Updated 2026-10-30T22:41:26.504Z.

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