Docs: say plainly that only the bot is open source; the dashboard and API are proprietary

- README, license section and architecture no longer point to the dashboard repositories
- schema.sql is the schema for contributors; database changes only need schema.sql and a note in the PR
- self-hosting: settings without a dashboard (SQL for security thresholds, beta settings, opted-in servers)
- beta features, deployment and troubleshooting reworded for people who don't have the dashboard

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

docs/deployment.md

@@ -27,15 +27,9 @@ Compose does not include Lavalink. Run it separately (or add a service) if you w
 
 Change the default database password (`velox_pwd`) before exposing PostgreSQL to anything other than your own machine, and remove the published `5432` port if only the bot needs it.
 
-## Running next to the dashboard
+## Database changes
 
-If you also run `velox-dashboard-api` and `velox-dashboard-web`:
-
-1. They all use the **same database**. Give each the same PostgreSQL, and point `DB_HOST` (bot) and the API's `DB_ADDR` at it.
-2. The API runs the migrations when it starts. The bot does not run migrations.
-3. **Deploy order for changes that touch the database:** API first (it applies the migration), then the bot and the dashboard.
-
-Some changes need the API, the bot and the dashboard to go out together. For example, when a table the dashboard writes changes shape, an old dashboard talking to a new API fails. The release notes for such a change say so.
+The bot does not run migrations. When a release adds tables, load `schema.sql` again before restarting the bot (it only creates what is missing, and is safe to repeat). A release that changes an existing table says so in its notes.
 
 ## Updating