Document installing plugins from the catalog Covers the Available tab, what the host verifies before it will install, staging and the restart, and why a plugin can read Not compatible or Not verifiable. Adds a publishing section: what belongs in a release zip and what does not, the sync tool rather than hand-editing the catalog, why every check it makes is unauthenticated, and when a release should name a platform. Also fills two older gaps - IBreakMusicProvider was a scanned extension point the page never listed, and the on-disk layout named neither plugins folder.
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.
Document the search rework and the tables as SQLite has them Search changed shape: folded columns, a single-column FTS index over folded text, notes out of the index, uniqueness on the folded name, and local-first provider search. The old sections described .NET-side matching that no longer exists. The schema tables are generated from a database built by running every migration, so they show what is on disk rather than what the model says.
Document login, permissions, the settings overlay, and password recovery
Describe the provider-driven search dropdown The split button now reflects the provider registry instead of hardcoded names, so the Plugins page can state how a provider surfaces in the UI as fact.
Populate the wiki from the current state of the solution
Initial Home page