Dashboard-first config workflow

This change removes the old /config YAML upload/download/update flow in favor of the dashboard, auto-provisions a default config when a guild joins, and updates onboarding/error messaging to send users to /config. Docs and metadata were refreshed to reflect the dashboard-first setup model and default-config behavior.

Author: Clawb1t

CLAUDE.md

@@ -90,11 +90,13 @@ Two independent layers (see `docs/permissions.md`):
   stripped rather than rejecting the whole config).
 - `config/manager.ts` (`ConfigManager`, singleton `configManager`) is the only way plugins read/write guild
   config: `getGuildConfig`/`getEffectiveConfig` (cached, falls back to defaults if a guild has no stored/valid
-  config), `saveGuildConfig` (full YAML upload), and granular patch helpers (`patchPluginConfig`,
-  `setPluginEnabled`, `patchLevels`, `setPermissionGrant`) used by `/permissions`, `/plugin toggle`, etc. Two YAML
-  copies are stored per guild: the full merged snapshot (`configYaml`) and just the user's overrides
-  (`userConfigYaml`), so `/config update` can re-merge overrides onto new defaults without clobbering
-  customization.
+  config), `saveGuildConfig` (full YAML replace — called by the dashboard bridge, and once by `bot.ts`'s
+  `GuildCreate` handler to auto-provision a default config so a brand-new guild's commands work immediately), and
+  granular patch helpers (`patchPluginConfig`, `setPluginEnabled`, `patchLevels`, `setPermissionGrant`) used by
+  `/permissions`, `/plugin toggle`, etc. Two YAML copies are stored per guild: the full merged snapshot
+  (`configYaml`) and just the user's overrides (`userConfigYaml`), so future default changes can be re-merged onto
+  overrides without clobbering customization. There is no in-Discord config upload/download anymore — `/config`
+  just links to the dashboard.
 - `npm run schema:export` (also run in `prebuild`) writes `schema/guild-config.schema.json` from the zod schemas
   for the external website's config editor to consume — keep plugin config schemas in sync if you change them.
 

README.md

@@ -1,10 +1,10 @@
 # Dreamliner
 
-Moderation and ops for large Discord communities: YAML config, staff permissions, logging, automod, and a web dashboard.
+Moderation and ops for large Discord communities: web-dashboard config, staff permissions, logging, automod, and stats.
 
 Dreamliner is a Discord moderation and server-operations bot built for communities that outgrow one-size-fits-all tools. It is designed for staff teams that need clear permission boundaries, auditable configuration, and features that stay reliable as membership and moderation load grow.
 
-Configure your server with versionable YAML: download a template, edit channels, plugins, and access levels, then upload. Day-to-day work can also run through the web dashboard for live config, logs, stats, and custom commands, without giving up file-based control. Dreamliner does not require Administrator; invite with least privilege and grant only what your staff need.
+Configure your server entirely from the web dashboard: channels, plugins, and access levels, saved live with no restart. A new server gets a working default config the moment Dreamliner joins, so every command works immediately — the dashboard is only for customizing it. Dreamliner does not require Administrator; invite with least privilege and grant only what your staff need.
 
 Core capabilities include infractions and case management, automod and raid tooling, content filters, structured logging, role and onboarding systems, multilingual translation, activity stats, and visually built custom slash commands. Enable only the plugins your community uses so the bot stays focused and predictable for operators.
 
@@ -24,21 +24,20 @@ Recommended permissions are pre-selected. Dreamliner does **not** require Admini
 
 ## Why operators choose it
 
-- **Config as source of truth:** Guild YAML is portable, reviewable, and easy to back up or hand off between staff.
-- **Least privilege by design:** Level-based access plus per-command `can_*` overrides so senior mods, trial staff, and helpers stay in their lane.
+- **Works on invite:** A default config is provisioned the instant Dreamliner joins — no setup step blocks day-one use.
+- **Least privilege by design:** Dreamliner Roles plus per-command `can_*` grants so senior mods, trial staff, and helpers stay in their lane.
 - **Ops without noise:** Enable only the plugins your community needs; leave the rest off.
 - **Slash-first management:** Staff workflows and custom commands stay in Discord’s command surface.
-- **Dashboard when you want it:** Live config, logs, stats, and building custom commands without abandoning file-based control.
+- **Dashboard-first config:** Live config, logs, stats, and building custom commands, all from one web dashboard.
 
 ---
 
 ## Quick start
 
 1. Invite Dreamliner with the link above.
-2. Run `/config template` (requires **Manage Server**).
-3. Edit the YAML: channels, plugins, and permission levels (levels can also be adjusted later with `/permissions`).
-4. Run `/config upload` with your file.
-5. Use `/permissions` for incremental access changes and `/help` for command discovery.
+2. Run `/config` (requires **Manage Server**) to get a link to this server's dashboard.
+3. Sign in with Discord, then edit channels, plugins, and Dreamliner Roles. Click **Save** — changes apply immediately.
+4. Use `/permissions` for incremental access changes in Discord, and `/help` for command discovery.
 
 Walkthrough: [Getting started](docs/getting-started.md)
 

docs/configuration.md

@@ -1,6 +1,8 @@
 # Configuration
 
-Dreamliner server configuration is written in YAML. Each server has its own config stored in the database after upload.
+Dreamliner server configuration is edited entirely from the **web dashboard** and stored as YAML in the database
+under the hood — there is no in-Discord upload/download workflow anymore. The YAML shape below documents that
+underlying format (and what a fork's `config/default.server.yaml` looks like), not something you write by hand.
 
 ## File format
 
@@ -32,7 +34,7 @@ Dreamliner Role instead. See [Permissions](permissions.md).
 
 The icons used on command response embed titles (success, error, neutral, warning, unchecked) and on log card
 titles (`logging.emojis`) are **fixed bot-wide and not configurable** — every server sees the same set, and
-neither the dashboard nor a `/config upload` can change them. The `emojis`/`logging.emojis` keys are no longer
+the dashboard cannot change them. The `emojis`/`logging.emojis` keys are no longer
 part of guild config; an uploaded YAML with either block simply has it ignored (they fail schema validation and
 get repaired away). See `src/core/embeds.ts` (`DEFAULT_EMOJIS`) and `src/core/logging/emojis.ts` (`LOG_EMOJI`) if
 you're maintaining a fork and want to change the defaults in code.
@@ -97,37 +99,28 @@ Each plugin is configured under `plugins.<name>`:
 
 ## Merge behavior
 
-On upload, your YAML is **deep-merged** with `config/default.server.yaml`. You only need to include keys you want to change.
+Whatever you save on the dashboard is **deep-merged** with `config/default.server.yaml` — you only ever customize the fields you touch, and new Dreamliner defaults apply automatically to anything you haven't.
 
 See also: [Autorole](plugins/autorole.md), [Member identity](plugins/member_identity.md), [Translation](plugins/translation.md), [Logs](plugins/logs.md), [Starboard](plugins/starboard.md).
 
 ## Config commands
 
-| Command            | Description                                                     |
-| ------------------ | --------------------------------------------------------------- |
-| `/config template` | Default template from bot operator                              |
-| `/config download` | Current effective config for this server                        |
-| `/config upload`   | Validate and save a config file                                 |
-| `/config validate` | Dry-run validation                                              |
-| `/config update`   | Apply new Dreamliner defaults while keeping your customizations |
-| `/permissions role ...` | Manage Dreamliner Roles without re-uploading YAML           |
-| `/plugin toggle`   | Enable or disable a plugin (`plugin` + `state`: Enable / Disable) |
-| `/plugin list`     | Show which plugins are enabled or disabled                      |
+| Command                 | Description                                                       |
+| ------------------------ | ------------------------------------------------------------------ |
+| `/config`               | Posts a link to open this server's dashboard                       |
+| `/permissions role ...` | Manage Dreamliner Roles without leaving Discord                    |
+| `/plugin toggle`        | Enable or disable a plugin (`plugin` + `state`: Enable / Disable)  |
+| `/plugin list`          | Show which plugins are enabled or disabled                         |
 
 ### Workflow
 
-1. Run `/config template` (new server) or `/config download` (existing server).
-2. Edit the YAML file locally, or use the website **config editor** (loads the schema from this repo).
-3. Run `/config validate` to check for errors (optional).
-4. Run `/config upload` to apply.
+1. Run `/config` (or open the dashboard link from the join message) and sign in with Discord.
+2. Pick this server, edit plugins and fields (channels/roles/members have search autocomplete).
+3. Click **Save** — Dreamliner applies the config immediately, no restart or re-upload needed.
 
-Machine-readable schema for the editor is generated with `npm run schema:export` into `schema/guild-config.schema.json` (also run during `prebuild`).
-
-### `/config update`
-
-When Dreamliner ships new default settings, run `/config update` to pick up changes you did not customize. Your overrides are preserved using the raw YAML from your last upload.
-
-If your config was saved before this feature existed, the bot uses diff detection against the stored defaults snapshot. Re-uploading via `/config upload` improves future updates.
+A new server already has a working default config the moment Dreamliner joins, so every command works
+immediately; the dashboard is only for customizing it. Machine-readable schema for the editor is generated with
+`npm run schema:export` into `schema/guild-config.schema.json` (also run during `prebuild`).
 
 ## Reloading
 
@@ -151,4 +144,4 @@ Dreamliner is organized into plugins under the `plugins:` key. Each plugin has i
 | Utilities         | utility, stats, bot\_customisation, logs                                                         |
 | Feedback          | reviews, suggestions                                                                             |
 
-See [Documentation index](/broken/pages/ScBf0pRjbQl3XDFHSAMa) for setup guides per plugin. The default template (`/config template`) includes all configurable fields.
+See [Documentation index](/broken/pages/ScBf0pRjbQl3XDFHSAMa) for setup guides per plugin. The dashboard exposes every configurable field for every plugin.

docs/getting-started.md

@@ -1,6 +1,8 @@
 # Getting started
 
-Dreamliner uses a **download → edit → upload** workflow for server configuration. After the first upload, you can also manage Dreamliner Roles and command access in Discord with `/permissions role ...` (no re-upload needed).
+Dreamliner is configured entirely from the **web dashboard** — there is no download/upload YAML workflow. You can
+also manage Dreamliner Roles and command access in Discord with `/permissions role ...` without ever opening the
+dashboard.
 
 ## 1. Invite the bot
 
@@ -19,23 +21,23 @@ At minimum you will need:
 
 The bot also needs standard read/send message permissions in channels where commands are used.
 
-## 2. Download the template
+As soon as Dreamliner joins, it provisions a working default config for the server — every command works
+immediately, before anyone touches the dashboard.
+
+## 2. Open the dashboard
 
 A server administrator runs:
 
 ```
-/config template
+/config
 ```
 
-This sends `dreamliner-template.yaml` - the default configuration maintained by the bot operator. It includes emoji settings and utility plugin defaults.
-
-## 3. Edit the configuration
+This posts a link to this server's dashboard. Open it and sign in with Discord — this server is already selected.
 
-Open the YAML file in any text editor. Common first steps:
+## 3. Configure
 
 1. Set up Dreamliner Roles - assign your mod/admin Discord roles or users to the built-in **Moderator**/**Admin** roles (dashboard **Roles** page, or `/permissions role assign`).
-2. Adjust `emojis` if you want custom success/error/neutral/warning/unchecked prefixes.
-3. Enable and configure plugins under `plugins` - see [plugin documentation](/broken/pages/ScBf0pRjbQl3XDFHSAMa#plugins) for categories:
+2. Enable and configure plugins - see [plugin documentation](/broken/pages/ScBf0pRjbQl3XDFHSAMa#plugins) for categories:
    * **Moderation** - infractions, lockdown, slowmode
    * **Protection** - automod, scam protect, persist, autodelete
    * **Role management** - staff role assign, templates, autorole, pingables
@@ -47,39 +49,18 @@ Open the YAML file in any text editor. Common first steps:
    * **Customization** - custom events, aliases, custom commands
    * **Utilities** - utility commands, stats, bot customisation, logs
    * **Feedback** - reviews and suggestions
-4. Grant `plugins.utility`'s `can_*` permissions to your Dreamliner Roles.
-
-See [Permissions setup](permissions.md) for a full walkthrough and examples. See [Configuration](configuration.md) for the full YAML format.
-
-## 4. Upload your configuration
-
-```
-/config upload file:<your-edited.yaml>
-```
-
-Dreamliner validates the file, merges it with defaults, saves it to the database, and applies it immediately.
-
-Use `/config validate` to check a file without saving.
-
-## 5. Download your current config
-
-To edit an existing setup:
-
-```
-/config download
-```
+3. Grant `plugins.utility`'s `can_*` permissions to your Dreamliner Roles.
+4. Click **Save**. Dreamliner applies the config immediately - no restart, no re-upload.
 
-This returns the effective configuration currently stored for your server.
+See [Permissions setup](permissions.md) for a full walkthrough and examples. See [Configuration](configuration.md) for the underlying config format.
 
-## 6. Use utility commands
+## 4. Use utility commands
 
-Once a configuration is uploaded, moderators can use commands like `/search`, `/user`, `/clean`, and `/help`. Permission is controlled by Dreamliner Roles, not just Discord roles.
+Moderators can use commands like `/search`, `/user`, `/clean`, and `/help` right away. Permission is controlled by Dreamliner Roles, not just Discord roles.
 
 ## Troubleshooting
 
 | Problem                      | Solution                                                |
-| ---------------------------- | ------------------------------------------------------- |
-| "No configuration yet"       | Run `/config template` → edit → `/config upload`        |
+| ----------------------------- | ------------------------------------------------------- |
 | "You do not have permission" | See [Permissions setup](permissions.md#troubleshooting) |
-| Upload validation errors     | Run `/config validate` to see specific field errors     |
 | Commands not appearing       | Ask the bot operator to run `pnpm register-commands`    |

docs/permissions.md

@@ -18,7 +18,7 @@ When inviting Dreamliner, grant at least these **bot permissions**:
 | View Channels          | See channels and run commands                             |
 | Send Messages          | Reply to slash commands                                   |
 | Embed Links            | Link previews in some outputs                              |
-| Attach Files           | `/config download`, `/source`, `/avatar`                   |
+| Attach Files           | `/source`, `/avatar`                                       |
 | Read Message History   | `/message`, `/context`, `/clean`, `/source`                |
 | Manage Messages        | `/clean` bulk delete                                        |
 | Ban Members            | `/bansearch`, `/ban`, `/unban`, `/softban`                  |
@@ -41,15 +41,13 @@ If commands fail in specific channels, check channel permission overwrites for t
 
 ***
 
-## Step 2: Upload a server configuration
+## Step 2: Open the dashboard
 
-Utility commands are disabled until a server admin uploads a config:
+A default config is provisioned automatically the moment Dreamliner joins, so every command already works. To
+customize it:
 
-1. `/config template`
-2. Edit the YAML file
-3. `/config upload`
-
-Only members with Discord **Manage Server** can use `/config` commands.
+1. Run `/config` (requires Discord **Manage Server**) for a link to this server's dashboard.
+2. Sign in with Discord, edit plugins/fields, then **Save** — it applies immediately.
 
 ***
 
@@ -184,10 +182,9 @@ Voice, moderation, and nickname commands also use Discord's own **role hierarchy
 
 | Action                                                                 | Requirement                                                                       |
 | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
-| Upload / download / validate config                                     | Discord **Manage Server**                                                          |
+| Edit server config on the dashboard                                     | Discord **Manage Server**                                                          |
 | Create/rename/delete Dreamliner Roles, assign targets, grant commands   | Discord **Manage Server** (dashboard **Roles** page or `/permissions role ...`)      |
 | Hot-reload config (`/reload`)                                            | `can_reload_guild` granted via a Dreamliner Role the member belongs to               |
-| Edit full YAML                                                           | `/config download` → edit → `/config upload`                                        |
 
 ### In-Discord permission editor
 
@@ -208,17 +205,16 @@ Use `/permissions role ...` (requires **Manage Server**) instead of the dashboar
 
 `role` and `command` options support autocomplete. Changes are saved immediately (same store the dashboard's Roles page uses).
 
-`/config download` → edit → `/config upload` still covers everything else in the config, but `can_*` grants are not among them anymore — always use Dreamliner Roles for those.
+The dashboard still covers everything else in the config, but `can_*` grants are not among them anymore — always use Dreamliner Roles for those.
 
 ***
 
 ## Troubleshooting
 
 | Symptom                               | Likely cause                                                | Fix                                                                          |
 | --------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------------------------------------- |
-| "No configuration yet"                | No YAML uploaded                                              | `/config template` → edit → `/config upload`                                 |
 | "You do not have permission"          | No Dreamliner Role the member belongs to grants that flag     | Assign them to a role that has it, or grant it on their existing role         |
-| "You need Manage Server"              | User lacks Discord perm                                        | Grant Manage Server or have an admin upload config                            |
+| "You need Manage Server"              | User lacks Discord perm                                        | Grant Manage Server or have an admin configure it on the dashboard            |
 | "You need Manage Messages"            | `can_clean` ok but Discord perm missing                        | Add Manage Messages to mod role                                               |
 | Command works for admins but not mods | Mod's Discord role/user isn't assigned to a Dreamliner Role with that flag | Assign it on the dashboard **Roles** page or `/permissions role assign` + `role grant` |
 | Bot does not respond in a channel     | Channel overwrite                                              | Allow bot View Channel + Send Messages                                        |