Skip to main content

max / makeover

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>
Claude-Session
https://claude.ai/code/session_01MptwXZ8k65v19rFmdGAyki
Author: Max Johnson <me@maxj.phd> · 2026-08-31 12:05 UTC
Signed with PGP, not checked
Commit: 80e1a5bedeb45425930ec734c92fa37cb0ccd9c7
Parent: 5a1fb5c
1 file changed, +1 insertion, -0 deletions
M Cargo.toml +1
@@ -5,6 +5,7 @@
5 5 description = "Shared theme loading for the make-family apps: TOML theme files parsed into intent-based color tokens, with perceptual derivations and WCAG contrast."
6 6 license = "MIT"
7 7 repository = "https://makenot.work/git/max/makeover"
8 + exclude = ["scripts/", "dist/", "bento.toml", ".githooks/"]
8 9
9 10 [dependencies]
10 11 serde = { version = "1", features = ["derive"] }