feat(bundle): use an installed bundle's envs, agents and artifacts from any bundle, the default agent included by earakely-scale · Pull Request #244 · scaleapi/agentenv-framework

refactor(bundle): name each planned entry's bundle, for files and messages

earakely-scale

and

claude

committed

428ba4f

feat(entity-refs): an unset agent field means the configured default agent

earakely-scale

and

claude

committed

bc6e548

feat(bundle): a reference to an installed bundle's entity pulls it into the run

earakely-scale

and

claude

committed

5c580db

feat(bundle): one ledger row and lock per pulled entity, whichever bundle uses it

earakely-scale

and

claude

committed

53173ce

feat(agents): a step deploying an unwritten @local agent says a bundle run writes one

earakely-scale

and

claude

committed

49249a6

docs: how a bundle uses an installed bundle's entities, and what an unset agent field means

earakely-scale

and

claude

committed

a43c3ce

fix(bundle): resolve a pulled entity's references in the running bundle first, and import installed entities unpinned

earakely-scale

and

claude

committed

7b02a8c

docs: point at entity.refs, where the unset-agent rule lives now

earakely-scale

and

claude

committed

2ff405f

feat(bundle): a built image is its build context, which this machine builds for the deploys here

earakely-scale

and

claude

committed

e3108ee

refactor(entity-refs): drop default_when; every unset agent field falls back to the default

earakely-scale

and

claude

committed

64a6fcf

fix(bundle): build here only the images a deploy here runs, and save one copy per image name for VMs here

earakely-scale

and

claude

committed

ee3199d

fix(local): a local sandbox given a platform builds a context as a VM does

earakely-scale

and

claude

committed

ebafb28

fix(bundle): a bundle image records no platform, so each sandbox builds it for its own

earakely-scale

and

claude

committed

61437c2

Navigation Menu

Repository navigation

feat(bundle): use an installed bundle's envs, agents and artifacts from any bundle, the default agent included - #244

feat(bundle): use an installed bundle's envs, agents and artifacts from any bundle, the default agent included#244
earakely-scale merged 13 commits into
mainfrom
feat/installed-bundle-entities

Commits on Oct 19, 2026

refactor(bundle): name each planned entry's bundle, for files and messages

feat(entity-refs): an unset agent field means the configured default agent

feat(bundle): a reference to an installed bundle's entity pulls it into the run

feat(bundle): one ledger row and lock per pulled entity, whichever bundle uses it

feat(agents): a step deploying an unwritten @local agent says a bundle run writes one

docs: how a bundle uses an installed bundle's entities, and what an unset agent field means

fix(bundle): resolve a pulled entity's references in the running bundle first, and import installed entities unpinned

docs: point at entity.refs, where the unset-agent rule lives now

feat(bundle): a built image is its build context, which this machine builds for the deploys here

refactor(entity-refs): drop default_when; every unset agent field falls back to the default

fix(bundle): build here only the images a deploy here runs, and save one copy per image name for VMs here

fix(local): a local sandbox given a platform builds a context as a VM does

fix(bundle): a bundle image records no platform, so each sandbox builds it for its own