Fix Netlify build by restoring dist build script and config

- Restore `scripts/build-dist.mjs` to clean `dist/`, build CSS, and copy assets.
- Update `package.json` to use the new build script and serve `dist`.
- Update `netlify.toml` to publish the `dist` directory.
- Update `dist/` artifacts to match current source.

Co-authored-by: PR0M3TH3AN <[email protected]>

dist/docs/logging.md

@@ -59,23 +59,10 @@ The source of truth lives in `config/instance-config.js`:
 
 - Set `IS_DEV_MODE = true` while developing locally so the dev logger and other
   diagnostics are available.
-- Keep `IS_DEV_MODE = false` for production builds. This value propagates to
-  `isDevMode` (the module export), `window.__BITVID_DEV_MODE__`, and
-  `logger.dev`, silencing development-only messages.
+- Flip `IS_DEV_MODE = false` before shipping a production build. This change
+  propagates to `isDevMode` (the module export), `window.__BITVID_DEV_MODE__`,
+  and `logger.dev`, silencing development-only messages.
 
 Always commit the flag change alongside deployment-ready configuration tweaks.
 Forgetting to update the flag leaves verbose traces in user consoles and can
 expose experimental behavior intended only for QA environments.
-
-If you need to enable dev logging without editing `config/instance-config.js`,
-inject a runtime override before `js/config.js` loads:
-
-```html
-<script>
-  window.__BITVID_DEV_MODE_OVERRIDE__ = true;
-  window.__BITVID_VERBOSE_DEV_MODE_OVERRIDE__ = true;
-</script>
-```
-
-Overrides accept boolean values or the strings `"true"` / `"false"` so they can
-be injected by a build pipeline.