what's changed.

Commands without `global: true`, like /media, were only registered in DISCORD_GUILD_ID, so people in other servers and in DMs couldn't see them. Register everything globally and clear the old guild-only list so the home server doesn't show each command twice.

Limit /anime-request-update to servers, since Discord doesn't apply member permissions in DMs.

npm install leaves native modules alone when Node itself is upgraded or swapped, which left better-sqlite3 linked against a missing libnode.so.115 and broke the /anime.db export. update.sh now records the Node binary and version in node_modules/.node-runtime and rebuilds better-sqlite3 whenever they differ.

Right-click a message → Apps → Save quote stores its text in data/quotes.json; /quote random shows one (filterable by text or person) and /quote remove takes one down. The bot now loads message context menus alongside slash commands.

/schedule-message is split into create, list and cancel, and the staff check moves to utils/staff.ts so both commands share it.

Staff (Manage Messages, or STAFF_ROLE_ID) give it a unix time and a message, and the bot posts it then. Queued messages live in data/scheduled-messages.json so they survive restarts.

Rework the layout and styles of every page while keeping all content and features. The home page gets a dial hero, an analog clock card, a featured project, a bigger VRChat card, a new quote and a sunset contact section. Subpages share one frame: a full-width header bar, consistent section headings and spacing, and tidier layouts for uses, changelog, colophon, stats, anime requests and the error pages.

Also scope the home page section padding so nested sections on subpages no longer get huge gaps, and show petals and the side rail on the home page only.

Page visits with utm_* tags are saved to data/utm.json (tags, page, referrer hostname, time; no IPs). Bots and 404s are skipped and only the latest 5,000 are kept.

It was the repo's only LFS file. A server without git-lfs would pull a pointer instead of the image and the /stats cat wouldn't draw. At 2 KB it's fine as a plain file.

/status now attaches a still of the cat in its current mood, with this moment's LEDs and the down container's name on the mug, and ends with the same caption as /stats. The image is drawn on the server from the same grids by services/cat-render.ts; the scene setup moved from the build script into content/cat/parts.ts so both share it.

A grey tabby with a notched ear sleeps on a little server rack with one LED per Docker container. Its mood follows the homelab: content, grumpy (CPU over 85% for 2 minutes), hot, guilty (a container is down, so it knocks a mug labelled with the container's name off the shelf), asleep (at night or when idle) and happy (after an outage). A new mood has to hold for 30 s before the cat switches. The thresholds are CAT_* env vars.

The art is hand-drawn text grids in src/content/cat, built into one sprite sheet plus frame timings by `pnpm build:cat`. getSiteStats() gains a homelab block (CPU %, temperature, containers via DOCKER_HOST, with an opt-in read-only socket proxy in docker-compose.yml), so the cat rides on the existing /api/stats poll. /stats/cat-preview shows every state, transition and color.

Explains what each Discord status means, whether to message, and a "no hello" section based on nohello.net.

Messages with STARBOARD_THRESHOLD stars (default 3, not counting the author or bots) are reposted to STARBOARD_CHANNEL_ID, with the count kept up to date. Needs the GuildMessageReactions intent and Reaction partials.

/status reuses the status channel site check, plus the public site's /healthz through the tunnel and the bot's gateway ping.

+reload re-registers the slash commands from Discord; it shares the registration code with deploy-commands, now in services/command-registry. +announce posts an embed to a channel with an optional role, @everyone or @here ping and an attached image.

Bot-owner only. Covers the server's settings, roles (position, colour, member count, permissions), channels in sidebar order with their permission overwrites, active threads, emojis and stickers, attached as {server_name}-dump.json.

Opens a modal for a title and suggestion, then sends it to the guild owner as an embed. Five-minute cooldown per user.

/guestbook: visitors leave a name, message and optional website. Notes are saved to data/guestbook.json as pending and only shown once approved on the unlisted /guestbook/review page (same ANIME_ACCEPT_KEY as /anime-accept). Protected by Turnstile, a honeypot and a 5-per-hour rate limit; GUESTBOOK_DISCORD_WEBHOOK_URL optionally pings Discord. The review-page sign-in helpers move to utils/admin-auth.ts, shared with /anime-accept (existing sessions stay valid).

/stats: live server, Discord bot, Jellyfin and site numbers, refreshed every 30s from /api/stats. /changelog: site history from the git log, grouped by month with trailers stripped. /colophon: how the site is built and served. /sitemap: every page, from the palette data.

The pages are added to the palette ("this site" group), nav menu, footer, sitemap.xml and robots.txt. The privacy policy, cookie policy and terms cover the guestbook.

The palette's contents move to content/palette.ts (projects and links come from the existing site content) and render client-side from JSON.

Search is fuzzy with highlighted matches and also matches keywords, group names and hints, ranked best-first. With no query it shows grouped sections plus the last few pages opened from it. Items show an icon, a one-line hint, "you are here" and external-link badges.

Adds actions (switch theme, copy email, copy page link, open the support dialog, back to top) with toast feedback, Tab/PageUp/PageDown and Ctrl/Cmd+Enter for a new tab, Esc clearing the query before closing, Ctrl+K toggling, and scroll lock while open. The nav button becomes a search pill showing the shortcut (Cmd on Mac); the palette goes full-screen on phones.

Trust cloudflared for the visitor IP and https scheme, so canonical and Open Graph URLs are https and rate limits see real IPs. Canonical URLs now always use SITE_URL.

Caching: pages add stale-while-revalidate and stale-if-error so Cloudflare can keep serving them during an outage, and a Cache-Control a route already set (like no-store on a 503) is no longer overwritten with the 1-hour default. CSS/JS links carry a content hash and are served as immutable.

Anime requests get optional Cloudflare Turnstile and per-IP rate limits (searches too). Also adds security headers, /healthz, /.well-known/security.txt, optional Cloudflare Web Analytics, graceful SIGTERM shutdown, palette arrow-key navigation, a skip link and home page JSON-LD.

Adds a README with deploy notes and recommended Cloudflare settings, .env.example, a cloudflared config example and a systemd unit. Compose drops the unused PASSWD, binds to localhost, persists data/ and can run cloudflared under the "tunnel" profile. Policies mention Cloudflare.

Tick several requests, pick one status and an optional note, and update them in a single write. A blank batch note keeps each request's existing note. Update embeds are grouped up to 10 per webhook message.

+send <user id or mention> sends the target an info embed with the Jellyfin server address, the request/downloads site and the setup guide. Only the bot application's owner (or team members) can use it.

A leftover untracked lockfile from an earlier npm install goes stale once package.json changes, and npm ci then refuses to install.

The Jellyfin anime library is written to data/ as CSV, plain text and SQLite on startup and every 12 hours, and /anime.{ext} serves those files. Adds better-sqlite3 (v12, which still supports Node 20).

Take three samples per check and judge on the median so a cold connection or one dropped request doesn't decide the status, time the site's own response instead of following redirects, and require two slow checks in a row before leaving Online. Sites can set their own slowMs threshold.

Keeps a locked voice channel per site in the STATUS_CAT category, renamed to Online/Slow/Down as checks change every 5 minutes.

- Switch the remote to the SSH URL if it isn't already - Run git and the build as the repo owner so their SSH key is used - cd to the script's directory so it works from anywhere (e.g. cron) - Use pnpm with the frozen lockfile when pnpm-lock.yaml exists - Build before restarting so a failed build doesn't take the site down