Repository navigation
feat(bundle): record what an import wrote, so registering the folder back can tell an edit - #353
Closed
earakely-scale wants to merge 1 commit into
Closed
earakely-scale wants to merge 1 commit into
earakely-scale wants to merge 1 commit into
Conversation
…back can tell an edit provenance.json, schema 2, now also holds: - the task map, each task file with the store's task id and version, and the eval's; - a fingerprint of the configured document store's section, which tells one store from another without naming where either is; - each file the import wrote, as its content hash (+x when executable). The pinned store references move from "store" to "pinned". Nothing reads the file yet. The file hash the ledger computes moves to _fs, so both use one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
Collaborator
Author
|
Shelved together with #356, which carried this commit. The import record v2 only serves registering an imported folder back, so it waits with it. The branch is kept. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
agent-env bundle register(next PR) writes a bundle folder into the configured store. When the folder was made bybundle init, register needs four things:bundle initleft out.Today's
provenance.jsonhas the entity and image ids, but not the task map for evals, nothing about the store, and nothing about the files.What changes
provenance.jsongets"schema": 2and also holds:tasks: each task file with the store's task id and version, for task and eval imports alike.eval: the eval file with its id and version, or null.store: a sha256 of the configured document store's config section. It tells one store from another (another machine's local store, another Mongo database) without naming where either is. The file still holds no store location.files: each file the import wrote, except the README andprovenance.json, keyed by its path in the folder, as its content hash. An executable file gets+xappended; only the execute bit is kept, so git's 644/755 and a different umask don't read as edits. Register compares the folder against this to tell an edit from the stored version. Contexts are pruned and lock-pinned on import, so the stored entity's own digests can't tell that.The pinned store references move from
storetopinned. Nothing reads the file yet. The ledger's file hash moves to_fs.file_sha256, so both use one helper.Tests
+xcase is checked with a context holding an executablerun.sh. The text holds nofile://and no home path.tst/unit/bundlepasses, 928.Draft until the register PR's e2e confirms this record holds everything register reads.
🤖 Generated with Claude Code