Module recipes 

Plan C t-004: change-intent recipes.

Recipes are structured outputs that replace raw symbol lists for known task families. Where a query like “migrate stale tests” today returns a flat list of candidate symbols that the LLM has to classify itself, a recipe returns a per-file action plan (move / delete / run / gate / keep-as-covered) with a one-line reason for each action.

The schema is intentionally minimal so additional recipes (Plan C+) can land without re-litigating the shape.

Structs

Recipe

RecipeAction

Enums

ActionKind

Action kinds emitted by recipes. Each value corresponds to a branch in some recipe’s pick_action-style decision tree. Variants are added only when at least one decision tree actually emits them.

Functions

classify_test_migration

First concrete recipe: classify the test-tier symbols matching a query by their migration story. Walks test files in scope, reads the ledger for each symbol, and picks an ActionKind per the role tags

migrate_stale_tests

Plan F t-002 — migrate-stale-tests recipe. Extends classify_test_migration with a Move action: when a Mapping entry’s body carries move_to: "<destination/path>", the test file is emitted as Move with that path in command. Otherwise falls back to the same decision tree as classify_test_migration so callers get one unified plan.