8000 BCLI: min box start of a task entry takes --name and refuses a held name (T10 residual, arch C1) · Issue #3196 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

BCLI: min box start of a task entry takes --name and refuses a held name (T10 residual, arch C1) #3196

Open

Description

@agent-137

Residual of BCLI T10 (#2898, PR #3185), arch ruling 1075 C1.

min box start <task-entry> always creates a fresh instance today. It goes through run_entry, which calls request_fresh_instance (crates/minimal/src/task.rs), and the daemon names the box <entry>-<n> (BOX-163). crate::task::RunEntry carries no box name, so min box start <task-entry> --name <n> is refused (StartEntryRefusal::NameUnsupported, crates/minimal/src/cmd/boxes/create.rs).

Architecture line 492 (gominimal/arch 9495216): start creates a box under its box name, which is the entry's unless [box] name or --name <n> sets one. It refuses a name that a running box holds, and --new asks for a parallel instance.

Do: let RunEntry carry a box name. Then a task-entry start without --new creates under the entry's (or --name's) name and refuses a held name. After that, remove the NameUnsupported refusal and the interim comment in plan_start.

Covers: BCLI-029, BCLI-070 (start half).

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0