8000 T11 — Override network, ingress and loadouts at start · Issue #2903 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

T11 — Override network, ingress and loadouts at start #2903

Closed

Description

@mitodrummer

Task

slice size difficulty model who estimated lines
Start, attach and resume M routine standard an agent 400 (220 code, 180 tests)

A box started with --network, --ingress or --loadout stores those values, and min box show --network shows them.

Scope narrowed by the owner on 2026-11-09. #3159 (norrietaylor) merges first. It adds --network and the egress flags through a shared EgressArgs / flag_egress, used by min session activate, min box create and min task run. List flags add to the file's list (arch#166), --allow-protocols replaces its list, and --deny-all-egress empties both allow lists. Build on that shared path. Do not add a parallel flag path. This task covers what #3159 does not: --ingress, --loadout (BCLI-073), the egress flags on min box start / min session start, and min box spec <entry> taking the same overrides. No interim hints, fallbacks or compatibility shims: file a residual for anything not built.

Covers:

  • BCLI-024
  • BCLI-073
  • BCLI-025

Layers:

  • client:
    • crates/minimal/src/cli.rs: the verb's arguments and help in the one command model
    • crates/minimal/src/cmd/boxes/create.rs: passes --network, --ingress and --loadout to the command-line override layer
    • crates/minimal/src/cmd/boxes/show.rs: min box show --network renders the stored network section
    • crates/minimal/src/cmd/boxes/policy.rs: shares the effective-network rendering
    • crates/minimal/src/tests.rs: the in-process minimald test harness gains this layer's tests
    • cargo nextest run -p minimal network_flags_override_stored_spec_and_projection
    • cargo nextest run -p minimal start_loadout_flag_selects_loadouts_layer
    • cargo nextest run -p minimal box_show_network_renders_effective
  • docs:
    • docs/reference/cli-min.md: documents --network and --ingress as overrides of the entry's network keys

Waits on:

Plan block
### T11 — Override network, ingress and loadouts at start
  slice: S3
  kind: task
  covers: BCLI-024, BCLI-073, BCLI-025
  size: M
  est: 220 code, 180 tests
  executor: agent
  difficulty: routine
  model: standard
  diagnostics: `min box show <box> --network` prints the box's effective network section as it was stored, overrides included, pinned by box_show_network_renders_effective
  observability: the command's existing tracing span records the verb, the box id it resolved and the outcome
  layers:
    - client:
      - crates/minimal/src/cli.rs: the verb's arguments and help in the one command model
      - crates/minimal/src/cmd/boxes/create.rs: passes `--network`, `--ingress` and `--loadout` to the command-line override layer
      - crates/minimal/src/cmd/boxes/show.rs: `min box show --network` renders the stored network section
      - crates/minimal/src/cmd/boxes/policy.rs: shares the effective-network rendering
      - crates/minimal/src/tests.rs: the in-process minimald test harness gains this layer's tests
      test: cargo nextest run -p minimal network_flags_override_stored_spec_and_projection
      test: cargo nextest run -p minimal start_loadout_flag_selects_loadouts_layer
      test: cargo nextest run -p minimal box_show_network_renders_effective
    - docs:
      - docs/reference/cli-min.md: documents `--network` and `--ingress` as overrides of the entry's network keys
  produces: none
  consumes: none
  proof: A box started with `--network`, `--ingress` or `--loadout` stores those values, and `min box show --network` shows them.
  depends on:
    - blocked by #2898
    - blocked by #3159

Activity

  1. added
    kind:taskA task the plan skill rendered; the body carries ## Task
    size:M200 to 500 net lines; one PR
    model:standardA standard model: work that needs care, or routine work that is large
    on Nov 3, 2026
  2. minimal-foundry commented on Nov 10, 2026

    @minimal-foundry
    Contributor

    Done. #3235 merged.

    branch agent/2903-override-network-ingress-and-loadouts-at-start · epic #2879 · PR #3235

    round outcome job
    1 pushed 90647159
    2 pushed 55855df5
    3 pushed 892b022b
    3 pushed 366f13fc

    Updated 2026-11-10T21:32:14.963Z.

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:standardA standard model: work that needs care, or routine work that is largesize:M200 to 500 net lines; one PR

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0