Stop pointing at a migration the collapse removed
Document break music, ads, and the message broker
Cover the cents change, the appliance shell and narrow layouts Tips are whole cents now, so the schema tables and the "stored as text" note were both wrong. Groups carry a not-a-singer flag. The window in a Release build is an appliance rather than a browser, including the honest limitation that reload and back cannot be fully closed from application code. Development gains what narrow layouts key off, and the scoped-CSS boundary that makes a rule match nothing without saying so.
Point at the run-khost skill and its cache-backup rule The clear-on-exit behaviour eats the local queue on every test run that stops the app, which is worth knowing before the first one, not after.
Add migrations by default, regenerate on purpose The procedure described regenerating the whole chain for any schema change, which costs the local database and a hand re-authoring of the FTS5 migration — too much for adding an index, and not what the repo now shows.
Populate the wiki from the current state of the solution