Exclude repo infrastructure from the published package
scripts/githooks, dist/recipes and bento.toml were package content, so a
git-hook edit or a recipe change moved the published-content verdict for
every crate at once while changing nothing a consumer compiles. A
staleness signal that fires on things no consumer can observe is one
nobody reads.
examples/ stays: it is legitimate published content a reader may want.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
description = "Build-script support for the make-family design system: materialise makeover's themes and makeover-webview's stylesheet into a Tauri app's frontend, once, instead of copying the same twenty lines into every consumer's build.rs."