Repository navigation
Add export-all for resumable bulk recipe generation - #30
Merged
Merged
Conversation
jordanlegare
marked this pull request as ready for review
September 8, 2026 02:47
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
1 participant
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.
The combination tool could export only manually selected component IDs. This adds
export-allto materialize the entire combination space into runnable recipe files.Run
python tools/build_recipe_combinations.py export-allto export the 397,811 canonical combinations intorecipes/combinations/generated/<N>-components/<hash-prefix>/combination-<id>.json. Use--all-ordersfor all 48,534,764 component orders,--dry-runto count without writing,--max-componentsto bound depth, or--outputto select another recipe root.Each recipe is validated and compiled before atomic file replacement. Reruns skip byte-identical outputs; different existing files require
--overwrite. Progress prints every 1,000 recipes. Generated output is ignored by Git and remains separate from the compound evidence catalog.Validation: 35 targeted tests passed; a full two-component export wrote 1,711 recipes and its rerun skipped all 1,711 unchanged files. Canonical and all-order dry runs returned the expected totals. Independent review found no important issues. Uploaded tree exactly matches the tested local tree.
This adds the bulk-export capability; it does not commit hundreds of thousands of generated files.