Repository navigation
feat: thicken sauces with a roux cooked from flour in a buttered frying pan - #118
Merged
Merged
Conversation
…ng pan The saucepan's Thick tag counted category "flour", but milled flour is minted as category "grain" and canAdd never admitted it, so sauce_thickness thick was unreachable. - Flour in a frying pan turns into a roux (types.yml cooking-option output); without butter it burns into a burnt roux. - A roux (category thickener, naming.yml categories) takes one of the saucepan's two ingredient places; a second or burnt roux is refused with a reason, raw flour with a hint. - Scooping a sauce with a roux makes it Thick. sauce_thickness is a prefix track, so the sauce is named "Thick Garlic Sauce" and dishes it is ladled onto list it that way. Sauces without a roux get no thickness tag (no "Thin"). - A thickener doesn't name the dish; it is an extra in the sauce's stars. - roux, roux_burnt, roux_rotten and flour_heap(_rotten) IA items; flour shows as a flat heap in the pan. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
github-actions
Bot
added
the
size:L
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
The Main review (K2) found the saucepan's Thick tag unreachable.
SauceReference.scoopcounted slots of categoryflour, but milled flour is minted as categorygrain(MillingStoneHandler.buildFlour).canAdddoesn't admitgraineither: it isn't a seasoning, sweetener, add-on, alcohol or bottling ingredient. So no sauce could ever be Thick.What
types.ymlflourcooking-options.frying_pan.output, the pan-foods pattern). The butter goes into its stars, as in any frying. Without butter the pan burns it, which gives a burnt roux.thickener,naming.ymlcategories.thickener) takes one of the two ingredient places, so the other is still free for a seasoning, sugar or garnish. A second roux or a burnt one is refused with a message. Raw flour is refused with a hint to cook it first.sauce_thicknessthick (+5% food and nutrition).sauce_thicknessis now anaming.ymlprefix track, so the sauce is named e.g. Thick Garlic Sauce. A dish it's ladled onto shows that name on its sauce line, and its food includes the bonus. Sauces without a roux get no thickness tag, so names don't start with "Thin".composition.ymlSAUCE_SCOOP).roux,roux_burnt,roux_rotten, plusflour_heap(_rotten)so flour lies in the pan as a flat heap. Both lie flat at 45%, placed like popcorn.SauceThickeningTest; the old flour scoop test now uses a roux).mvn clean verify: 1439 tests, coverage checks met.Server config outside this repo
The frying pan's InteractibleFurniture slot whitelist must let flour in:
c.grain(type=flour).🤖 Generated with Claude Code