1@README.md
2
3- **A new crate with a `build.rs` needs a folder here** when buckify warns
4  that its fixup "does not say what to do". Read the build script, then
5  write `buildscript.run = true` or `false` in `<crate>/fixups.toml`; most
6  only probe rustc features and need `true`. Re-run buckify (`../README.md`).
7- **A build script that emits `cargo:rustc-link-lib` or
8  `rustc-link-search` needs them kept explicitly** (`alsa-sys` does), or the
9  final link fails with undefined symbols.
10- **`subsecond/fixups.toml`'s `-Cdebug-assertions=yes` is load-bearing.**
11  Removing it makes every hot patch a silent no-op (`apps/hotdemo/CLAUDE.md`
12  has the measurement).
13- Name a folder exactly as the crate: reindeer loads `fixups/<name>` only
14  when a package of that name is in the graph. A folder left behind after a
15  crate leaves the graph is never read and nothing reports it; delete it with
16  the crate.
17- Only `README.md` and `CLAUDE.md` may sit directly in this folder besides
18  the crate folders; reindeer never looks a crate named either of those up,
19  so they are inert.