feat(bundle)!: bundle init writes every env, agent and data artifact a task uses into the folder by earakely-scale · Pull Request #259 · scaleapi/agentenv-framework

feat(bundle): write each entity a task uses into the folder, through its type's to_toml

earakely-scale

and

claude

committed

b364045

test(bundle): every core type reads back from its folder as the store held it, and what a folder can't hold

earakely-scale

and

claude

committed

252a370

bundle init pins each image's Python and global npm installs to the versions its stored image holds

earakely-scale

and

claude

committed

7c36421

agent-env run checks Docker's Compose and Buildx plugins and the model endpoint before a run starts

earakely-scale

and

claude

committed

0d52a6f

bundle init takes stored contexts holding hard links, and leaves out a field naming what it can't take

earakely-scale

and

claude

committed

470ddc4

bundle init pulls an image by the registry ref it names when its build context can't be written

earakely-scale

and

claude

committed

76e06be

bundle init gives a reference naming no version the version its task pins elsewhere

earakely-scale

and

claude

committed

73715e8

bundle init's README says a private registry is reached through the configured image store

earakely-scale

and

claude

committed

fd49826

bundle init leaves out what the OS or Python leaves in a stored artifact, and says so

earakely-scale

and

claude

committed

83a0d30

bundle init gives only an env named with no version the version its task pins elsewhere

earakely-scale

and

claude

committed

ccd85f3

bundle init's report, README and provenance move out of the importer, and the tests share their helpers

earakely-scale

and

claude

committed

23a3425

bundle init pins each image once every image is placed, and keeps on with a context the store no longer holds

earakely-scale

and

claude

committed

2180a5d

Navigation Menu

Repository navigation

feat(bundle)!: bundle init writes every env, agent and data artifact a task uses into the folder - #259

feat(bundle)!: bundle init writes every env, agent and data artifact a task uses into the folder#259
earakely-scale merged 14 commits into
mainfrom
edgararakelyan/fd-3994-pr-2-agent-env-bundle-init-write-every-env-agent-and-data

Commits on Oct 19, 2026

feat(bundle): write each entity a task uses into the folder, through its type's to_toml

test(bundle): every core type reads back from its folder as the store held it, and what a folder can't hold

bundle init pins each image's Python and global npm installs to the versions its stored image holds

agent-env run checks Docker's Compose and Buildx plugins and the model endpoint before a run starts

bundle init takes stored contexts holding hard links, and leaves out a field naming what it can't take

bundle init pulls an image by the registry ref it names when its build context can't be written

bundle init gives a reference naming no version the version its task pins elsewhere

bundle init's README says a private registry is reached through the configured image store

bundle init leaves out what the OS or Python leaves in a stored artifact, and says so

bundle init gives only an env named with no version the version its task pins elsewhere

bundle init's report, README and provenance move out of the importer, and the tests share their helpers

bundle init pins each image once every image is placed, and keeps on with a context the store no longer holds

Commits on Oct 20, 2026

bundle init pins a Dockerfile two images share only when their saved images hold the same versions

bundle init's guidance has one source each, and the importer's reference and pinning rules are named