Implementation Plan: Standardize recipe_version Field Across Recipe YAMLs#3904
Merged
Trecek merged 6 commits intoJun 8, 2026
Merged
Conversation
…AMLs Quote unquoted `recipe_version` values in implementation.yaml, merge-prs.yaml, and remediation.yaml for consistency with all other recipes. Promote planner.yaml's bare integer "2" to "2.0.0" semver. Add `recipe_version: "1.0.0"` to sub-recipes/research.yaml (was missing). Standardize `schema_version: "1.0"` to `"1.0.0"` (three-component semver) across all 12 experiment-type and 14 methodology-tradition YAMLs. Regenerate compiled JSON siblings via `task regen-contracts && task compile-recipes`. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Bump the compatibility check target version in: - experiment_type_registry.py (lines 140, 145) - methodology_tradition_registry.py (lines 246, 251) - cli/_validate.py EXPECTED_SCHEMA_VERSION constant (line 22) These three locations previously compared against the two-component "1.0" string; they now match the three-component "1.0.0" semver used in the bundled YAML data files. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Update existing test fixtures and assertions to use the new three-component "1.0.0" schema_version in: - tests/recipe/test_experiment_type_registry.py - tests/recipe/test_methodology_tradition_registry.py - tests/cli/test_validate_registries.py Add test_all_bundled_recipes_have_semver_recipe_version to TestRecipeVersionField in tests/recipe/test_io_schema_fields.py. The new test enforces X.Y.Z semver format on every bundled recipe's recipe_version field, including sub-recipes in builtin_sub_recipes_dir(). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ms from 1.0 to 1.0.0
…ils to avoid inline "1.0.0" duplication Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ver_recipe_version to module level Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
Standardize the
recipe_versionfield across all bundled recipe YAML files to use quoted semver format ("X.Y.Z"), fixschema_versionvalues in experiment-type and methodology-tradition YAMLs from"1.0"to"1.0.0"(three-component semver), update all three registry/validation modules that compare against the expected version, update the CLIvalidate registriescommand constant, regenerate compiled JSON siblings, and add a structural test enforcing semver consistency going forward.The
schema_versionkey name is intentionally preserved for experiment-type and methodology-tradition files — these are not recipes (they'reExperimentTypeSpecandMethodologyTraditionSpecparsed by separate registries) and renaming torecipe_versionwould be semantically misleading.Implementation Plan
Plan file:
/home/talon/projects/autoskillit-runs/impl-20260608-005324-730329/.autoskillit/temp/make-plan/standardize_recipe_version_plan_2026-06-08_010500.mdCloses #3772
🤖 Generated with Claude Code via AutoSkillit
Token Usage Summary
* Step used a non-Anthropic provider; caching behavior may differ.
Token Efficiency
Model Usage Breakdown