ompchamber 1.2.1 → 2.0.0

package/README.md

@@ -1,88 +1,103 @@
 <p align="center">
-  <img src="public/icon-512x512.png" alt="OMPChamber" width="180" height="180">
+  <img src="public/icon-512x512.png" alt="OMPChamber" width="140" height="140">
 </p>
 
 <h1 align="center">OMPChamber</h1>
 
 <p align="center">
-  Developer web console and diagnostic chamber for <b>AI Oh-My-Pi</b>.<br>
+  Browser console and diagnostic chamber for <a href="https://github.com/can1357/oh-my-pi">Oh-My-Pi</a> (<code>omp</code>) agent sessions.<br>
   Watch, steer and audit autonomous coding sessions from one paper-flat dashboard.
 </p>
 
 <p align="center">
-  <a href="https://bun.sh"><img alt="Runtime: Bun 1.4" src="https://img.shields.io/badge/runtime-Bun%201.4-000000?logo=bun&logoColor=white"></a>
-  <a href="https://elysiajs.com"><img alt="Server: Elysia 1.4" src="https://img.shields.io/badge/server-Elysia%201.4-6f42c1"></a>
-  <a href="https://preactjs.com"><img alt="UI: Preact 10" src="https://img.shields.io/badge/UI-Preact%2010-673ab7?logo=preact&logoColor=white"></a>
-  <a href="https://rsbuild.dev"><img alt="Build: Rsbuild 2" src="https://img.shields.io/badge/build-Rsbuild%202-eab308"></a>
-  <a href="package.json"><img alt="Version: 0.5.0" src="https://img.shields.io/badge/version-0.5.0-3f3f46"></a>
+  <a href="https://www.npmjs.com/package/ompchamber"><img alt="npm version" src="https://img.shields.io/npm/v/ompchamber?logo=npm&logoColor=white&color=cb3837"></a>
+  <a href="https://bun.sh"><img alt="Bun &ge; 1.4" src="https://img.shields.io/badge/Bun-%E2%89%A51.4-000000?logo=bun&logoColor=white"></a>
+  <a href="https://elysiajs.com"><img alt="Elysia" src="https://img.shields.io/github/package-json/dependency-version/rajebdev/ompchamber/elysia?color=6f42c1"></a>
+  <a href="https://preactjs.com"><img alt="Preact" src="https://img.shields.io/github/package-json/dependency-version/rajebdev/ompchamber/preact?logo=preact&logoColor=white&color=673ab7"></a>
+  <a href="https://shiki.style"><img alt="Shiki" src="https://img.shields.io/github/package-json/dependency-version/rajebdev/ompchamber/shiki?color=3f3f46"></a>
+  <a href="package.json"><img alt="Version" src="https://img.shields.io/github/package-json/v/rajebdev/ompchamber?label=version&color=3f3f46"></a>
 </p>
 
 <p align="center">
   <a href="AGENTS.md">Architecture</a> ·
-  <a href="docs/MIGRATION-elysia-preact-rsbuild-bun.md">Migration guide</a> ·
-  <a href="DESIGN.md">Design spec</a> ·
+  <a href="DESIGN.md">Design</a> ·
   <a href="CHANGELOG.md">Changelog</a> ·
   <a href="https://github.com/rajebdev/ompchamber/issues">Issues</a>
 </p>
 
----
+![OMPChamber — session sidebar, streaming timeline and the Files panel](docs/assets/hero-dark.png)
 
-### [Read the docs →](AGENTS.md)
+## What it is
 
-## What is OMPChamber?
-
-OMPChamber is the browser console for [Oh-My-Pi](https://github.com/rajebdev/ompchamber) (`omp`) agent
-sessions. It is not a wrapper around a terminal — it reads omp's own session JSONL, project
-registry, config and subagent transcripts, then folds them into one live view.
-
-One Elysia process serves the API and the client bundle. The agent event stream is a first-class
-WebSocket route on that same listener (SSE as fallback), so there is no second server to run and
-no proxy to configure.
+The browser view onto a live `omp` install. It is not a terminal wrapper: the chamber reads
+omp's own session JSONL, project registry, config and subagent transcripts, folds them into one
+live view, and writes back through omp's RPC mode.
 
 ```bash
-bun run src/server/index.ts          # API + WebSocket + static client on :3000
+bun run src/server/index.ts    # API + WebSocket + static client on :3000
 ```
 
-Every developer surface is a switchable right-hand panel — files, search, git, terminal, context
-telemetry, browser (headless and your own), usage — and each one remembers its own width.
+- **One process.** Elysia serves the API and the client bundle, and the agent event stream is a
+  first-class WebSocket route on that same listener (SSE as fallback) — no second server, no proxy.
+- **Two data modes.** `MOCK=false` (the default, also when unset) runs on the real SQLite database
+  and your real workspace; `MOCK=true` swaps in bundled demo datasets. Every screenshot and
+  recording on this page was captured in `MOCK=true`.
+- **Bun only.** The server imports `bun:sqlite`, and sessions, config and updates shell out to the
+  `omp` binary.
 
-```bash
-ompchamber                           # start the server (default command)
-ompchamber serve --lan --prod        # expose on 0.0.0.0, serve the production build
-ompchamber logs -f -n 200            # follow the server log
-```
+## Feature tour
+
+![Feature tour — panels, search, terminal, telemetry](docs/assets/tour.gif)
 
-## Features
-
-- **Live session timeline** — streaming thinking blocks, tool-call cards with structured
-  renderers, provider/model metadata, stick-to-bottom scroll and a persistent message queue.
-- **In-place undo** — rewind an omp session by truncating its JSONL, guarded by a confirmation
-  step and reflected in the sidebar immediately.
-- **Workspace sidebar** — folder → session tree backed by omp's project registry, with
-  server-authoritative per-session stream status, search, sort and archive.
-- **Editor + diff** — tabbed file editing and git diffs highlighted by Shiki with the
-  `one-light` / `one-dark-pro` pair across 26+ extra languages.
-- **Eight developer panels** — files, search (ripgrep-backed, streaming), git source control,
-  Bun terminal, context & token telemetry, your browser, headless browser, usage.
-- **Full omp settings surface** — OMP Engine config keys, providers, agents, behavior
-  (`AGENTS.md` / `RULES.md`), slash commands, MCP servers with live connection tests, skills and
-  the skills catalog, token usage and notifications.
-- **Two data modes** — `MOCK=false` (the default, also when unset) runs purely on the real SQLite
-  database and real workspace files; `MOCK=true` opts into demo datasets for previews.
-- **Self-update** — `ompchamber update` installs the latest GitHub release (bun global or git
-  checkout) and restarts the instance it started; **About → Updates** does the same from the console,
-  restart included.
+<sub>Full-quality recording (MP4, 27s): [docs/assets/tour.mp4](docs/assets/tour.mp4) · theme cycle in motion: [docs/assets/themes.gif](docs/assets/themes.gif)</sub>
+
+| | |
+|---|---|
+| ![Files panel](docs/assets/panel-files.png)<br>**Files** — project tree, opened-file tabs, one repo picker shared with the other panels | ![Search panel](docs/assets/panel-search.png)<br>**Search** — ripgrep-backed streaming results, scoped to the picked repo |
+| ![Source control](docs/assets/panel-git.png)<br>**Source control** — staged/unstaged changes, commits, branches, tracking state | ![Editor and diff](docs/assets/panel-diff.png)<br>**Editor &amp; diff** — split or unified diffs, Shiki highlighting, images as pictures |
+| ![Terminal](docs/assets/panel-terminal.png)<br>**Terminal** — a real PTY (one shell per terminal id, scrollback replayed on reload) | ![Context and telemetry](docs/assets/panel-context.png)<br>**Context &amp; telemetry** — context window use, cache hit rate, cost, per-turn breakdown |
+| ![Usage](docs/assets/panel-usage.png)<br>**Usage** — provider balance, plan windows, per-model token spend | ![Appearance settings](docs/assets/settings-themes.png)<br>**Settings** — appearance, chats, OMP engine, providers, agents, commands, MCP, skills |
+| ![Mobile view — chat, sessions drawer and the panel rail on a phone](docs/assets/mobile.png)<br>**Mobile view** — the same session on a phone: chat, sessions drawer, the full panel rail | ![Light theme](docs/assets/hero-light.png)<br>**Any palette** — 45 light and dark themes, applied to the whole console |
+
+- **Chat timeline** — streaming thinking blocks, tool-call cards with a structured renderer per tool
+  (bash, LSP, AST edit, hub tasks, mermaid diagrams you can zoom), usage footers, a persistent
+  follow-up queue, a jump rail that reaches any user turn, drag-and-drop attachments, one-shot
+  auto-titling, and in-place undo that rewinds a session by truncating its JSONL behind a
+  confirmation step.
+- **Side questions** (`/btw [question]`) — replaces the composer with a panel that answers from a
+  private copy of the session file, so the parent transcript is never written; a topic can be
+  promoted into a session of its own, and it runs the same tool cards, thinking and usage rows as
+  the chat.
+- **Workspace sidebar** — folder → session tree off omp's project registry, with search, sort,
+  archive, per-session stream status and subagent rows.
+- **Eight right-panel views** — files, search, git, terminal, context &amp; telemetry, your browser,
+  the agent browser and usage, each remembering its own width per session.
+- **Full omp settings surface** — engine config keys, providers, agents, `AGENTS.md` / `RULES.md`,
+  slash commands, MCP servers with live connection tests, skills and the skills catalog, token
+  usage and notifications.
+- **Self-update** — `ompchamber update` installs the latest GitHub release, and **About → Updates**
+  does the same from the console, restart included.
+
+## Themes
+
+![Six of the 45 palettes](docs/assets/theme-grid.png)
+
+45 palettes in one catalog (`src/shared/lib/theme/`): the chamber's own three (`paper`, `contrast`,
+`one-dark-pro-soft`) and 21 light/dark pairs — Catppuccin, Gruvbox, Tokyo Night, Nord, Dracula,
+Solarized, Kanagawa, Vesper and more. Switching repaints everything, syntax highlighting and
+Mermaid diagrams included, through one writer (`applyDocumentTheme`) that sets `data-theme` and
+announces it.
 
 ## Install
 
-OMPChamber is published to npm. It needs a Bun runtime, not Node:
+OMPChamber is published to npm and runs on Bun, not Node:
 
-> **Bun only** — the server imports `bun:sqlite` and `Bun.YAML`, both of which Node cannot load.
-> `bun` 1.4 or newer is required.
+> **Bun only** — the server imports `bun:sqlite` and `Bun.YAML`, neither of which Node can load.
+> Bun 1.4 or newer is required.
 
 > **omp required** — every live capability (agent sessions, omp config, session state, updates)
-> shells out to the `omp` binary, so `serve` refuses to start when it cannot be resolved on `PATH`
-> (or via `OMPCHAMBER_OMP_BIN`). `MOCK=true` is the only mode that runs without a real omp install.
+> shells out to the `omp` binary, so `serve` refuses to start when it is not on `PATH` (or set via
+> `OMPCHAMBER_OMP_BIN`). `MOCK=true` is the only mode that runs without a real omp install.
 
 ```bash
 bun add -g ompchamber     # puts the `ompchamber` command on your PATH
@@ -90,8 +105,8 @@ ompchamber serve --prod   # start the server on :3000
 ```
 
 The published tarball carries the source, the CLI and the prebuilt client bundle, so there is no
-build step after install — `serve` runs immediately. `npm install -g ompchamber` works too, because
-the `ompchamber` bin is a Bun script: Bun still has to be on `PATH`.
+build step after install. `npm install -g ompchamber` works too — the `ompchamber` bin is a Bun
+script, so Bun still has to be on `PATH`.
 
 ### From source
 
@@ -103,39 +118,28 @@ bun run build                        # dist/client — the only build artifact
 
 bun run start                        # NODE_ENV=production bun run src/server/index.ts
 bun link                             # then: ompchamber status
-bun run src/cli/ompchamber.js status
 ```
 
-> **Serve before you build?** Without `dist/client` the server answers `503` and prints the exact
-> command to run — it never fails with a bare `500`.
+> Without `dist/client` the server answers `503` with the exact command to run — never a bare `500`.
 
 ### Updating
 
-`ompchamber update` resolves the newest GitHub release, compares it with the version in
-`package.json` and replaces the install in place:
-
 ```bash
 ompchamber update --check        # report only: current version, latest release
 ompchamber update                # install it, then restart a running instance
 ompchamber update --force        # reinstall even when already up to date
 ```
 
-How the install is replaced depends on how it was made. A **bun global** install is refreshed with
-`bun add -g ompchamber@<version>`. A **git checkout** of this repository is fast-forwarded to the
-release tag and rebuilt (`bun install`, `bun run build`). Uncommitted work is never merged over:
-the update refuses and asks you to commit or stash first. An install owned by another package
-manager is not touched — the command prints the exact command to run instead.
+A **bun global** install is refreshed with `bun add -g ompchamber@<version>`; a **git checkout** is
+fast-forwarded to the release tag and rebuilt. Uncommitted work is never merged over (the update asks
+you to commit or stash first), and an install owned by another package manager is left alone and told
+which command to run.
 
-The same check runs from the console — **About → Updates**. Its Update button performs the same
-install and then restarts the instance serving that console, exactly as `ompchamber update` restarts
-the instance it finds: a detached `ompchamber restart --port <port>` is armed a moment after the
-response, so the server that answered is replaced without losing the reply, and the console
-reconnects on its own.
-
-A server OMPChamber did not start is never restarted. `bun run dev`, `bun run start`, a manual
-`bun src/server/index.ts` and an instance owned by a supervisor (systemd, pm2, a container) all
-record themselves as `direct`, so the update leaves them running and says so — their own launcher is
-what picks up the new files. `--no-restart` turns the restart off entirely.
+A server OMPChamber did not start is never restarted: `bun run dev`, `bun run start`, a manual
+`bun src/server/index.ts` and instances owned by a supervisor (systemd, pm2, a container) all record
+themselves as `direct`, so the update leaves them running and says so. `--no-restart` turns the
+restart off entirely. The console's **About → Updates** runs the same install and restarts the
+instance serving that console.
 
 ## CLI
 
@@ -152,11 +156,11 @@ what picks up the new files. `--no-restart` turns the restart off entirely.
 
 | Option | Purpose |
 |---|---|
-| `-p, --port <port>` | Web server port (default `3000`) |
-| `--host <address>` | Bind address (default `127.0.0.1`) |
+| `-p, --port <port>` | Web server port (default `3000`); scopes `status`/`stop`/`restart`/`logs` |
+| `--host <address>` (`--hostname`) | Bind address (default `127.0.0.1`) |
 | `--lan` | Bind to `0.0.0.0` for LAN access |
 | `--prod` | Serve the production build instead of the dev server |
-| `--foreground` | Run in the foreground (no daemon) |
+| `--foreground` (`--no-daemon`) | Run in the foreground (no daemon) |
 | `--all` | Apply the command to every running instance |
 | `-c, --check` | Report whether a newer release exists without installing it |
 | `--force` | Reinstall even when already up to date |
@@ -167,9 +171,8 @@ what picks up the new files. `--no-restart` turns the restart off entirely.
 ### Ports and multiple instances
 
 One port is served by exactly one process, and `bun run dev`, `ompchamber serve` and the production
-server all default to `3000`. **A starting instance never stops another one** — not a CLI server
-and not a dev run. If the port is taken by OMPChamber, the newcomer reports who holds it and exits
-non-zero so you can pick another port and re-run:
+server all default to `3000`. **A starting instance never stops another one** — if the port is taken
+by OMPChamber, the newcomer reports who holds it and exits non-zero so you can pick another port:
 
 ```bash
 ompchamber serve --port 3001        # CLI flag
@@ -177,40 +180,19 @@ OMPCHAMBER_PORT=3001 ompchamber serve
 PORT=3001 bun run dev              # or: PORT=3001 bun run start
 ```
 
-- Nothing is ever signalled to free a port. `ompchamber stop --port 3000` is the deliberate way to
-  free one, and it is per port.
-- A process that is **not** OMPChamber is never signalled either: the server exits with an error
-  naming the port and the `lsof -nP -iTCP:<port> -sTCP:LISTEN` command to identify it.
-- The refusal exists because a second bind would *succeed*: Elysia's Bun adapter hardcodes
-  `reusePort: true`, so two servers would share a port and only the first-bound socket would receive
-  connections — the newcomer would look healthy while the browser kept talking to the old build.
-- `bun run dev` hot reload is unaffected: `--hot` re-evaluates the server entry *inside the running
-  process*, and a port held by that same process is recognized as its own, so Bun swaps the handler
-  on the next `listen`. Saving a file neither trips the guard nor resets the reported uptime.
-
-Running several ports at once is supported. `status`, `stop`, `restart` and `logs` act on **every**
-live instance by default, and `--port <port>` narrows them to one. `restart` is the one exception to
-"every": an instance started from source is reported and left running, exactly as `ompchamber update`
-leaves it — `status`/`stop`/`logs` still see it, and `stop` still ends it:
-
-```bash
-ompchamber status                  # every instance: port, pid, mode, launch mode, health, log
-ompchamber status --port 3001      # just that one
-ompchamber logs -n 200             # one header per instance, sources included
-ompchamber logs --port 3001 -f     # follow one instance's log
-ompchamber stop                    # stop them all (--all is the explicit spelling)
-ompchamber stop --port 3001        # stop just that one
-ompchamber restart                 # restart the CLI-started ones, skip a `bun run dev`
-```
+- Nothing is ever signalled to free a port; `ompchamber stop --port 3000` is the deliberate way.
+- A process that is **not** OMPChamber is never signalled either: the server names the port and
+  prints the `lsof -nP -iTCP:<port> -sTCP:LISTEN` command to identify it.
+- `bun run dev` hot reload is unaffected: `--hot` re-evaluates the entry inside the running
+  process, and a port held by that process is recognized as its own.
+- `status`, `stop`, `restart` and `logs` act on **every** live instance by default; `--port <port>`
+  narrows them to one. `restart` skips instances started from source, as `update` does.
 
-The server writes `~/.ompchamber/run/<port>.json` (`pid`, `host`, `mode`, `launchMode`,
-`startedAt`) once it owns the port, which is why `status`/`stop`/`logs` also see servers started by
-`bun run dev` or `--foreground` — not just daemon-spawned ones. `launchMode` is `daemon` or
-`foreground` for a server the CLI spawned and `direct` for every other launch, and it is derived from
-the process's **argv**, never from an environment variable: env is inherited, so a `bun run dev`
-started inside an OMPChamber shell would otherwise be mislabelled and replaced by an update. Records
-left by a killed server are pruned as soon as their PID stops answering, so a recycled PID is never
-reported as an instance.
+The server writes `~/.ompchamber/run/<port>.json` (`pid`, `host`, `mode`, `launchMode`, `startedAt`)
+once it owns the port, which is how `status`/`stop`/`logs` also see servers started by `bun run dev`
+or `--foreground`. `launchMode` is derived from the process's **argv**, never from an environment
+variable — env is inherited, so a `bun run dev` started inside an OMPChamber shell would otherwise be
+replaced by an update. Records left by a killed server are pruned once their PID stops answering.
 
 ## Configuration
 
@@ -232,8 +214,8 @@ Environment variables, read from `.env` (see [`.env.example`](.env.example)):
 | `SKILLS_API_URL` | `https://skills.sh` | Skills catalog source |
 | `GITHUB_TOKEN` / `GH_TOKEN` | — | Raise the GitHub API rate limit for update checks |
 
-Runtime state, sessions and settings live in SQLite (`~/.ompchamber/db.sqlite`), which is the
-single source of truth for persisted settings.
+Runtime state, sessions and settings live in SQLite (`~/.ompchamber/db.sqlite`), the single source
+of truth for persisted settings.
 
 ## Architecture
 
@@ -256,12 +238,13 @@ Non-obvious invariants worth reading before you edit:
 
 - **`src/shared/**` must never import a `node:` builtin or `bun:sqlite`** — it also runs in the
   browser. Server-only helpers belong in `src/server/lib/**`.
-- **Route modules keep the ported Remix shape** (`loader` for GET, `action` for mutations) so
-  status codes stay identical; `action` owns method dispatch and returns its own `405`.
+- **Route modules keep the ported Remix shape** (`loader` for GET, `action` for mutations) so status
+  codes stay identical; `action` owns method dispatch and returns its own `405`.
 - **Every internal import uses the `@/` alias**, folders mirror component names in kebab-case, and
   every `.ts`/`.tsx` file stays under 350 lines.
 
-[`AGENTS.md`](AGENTS.md) is the normative reference for all of the above.
+[`AGENTS.md`](AGENTS.md) is the normative reference for all of the above — the invariants behind the
+panels, the BTW subsystem, the PTY terminal and the build/dev loop.
 
 ## Development
 
@@ -273,12 +256,8 @@ bun run dev:client     # client only (rsbuild build --watch)
 ```
 
 There is no HMR: the server reloads on save, the client bundle rebuilds, refresh the page.
-`dist/client/index.html` is the shell for both dev and prod, so run `dev:client` at least once
-after a clean checkout.
-
-Dev and prod share the default port `3000`: a second starter on an occupied port refuses and exits
-with the port options to re-run ([Ports and multiple instances](#ports-and-multiple-instances));
-nothing is stopped for you.
+`dist/client/index.html` is the shell for both dev and prod, so run `dev:client` at least once after
+a clean checkout.
 
 Verification gates, all mandatory:
 
@@ -289,29 +268,34 @@ bun run build                                                 # production bundl
 bun test                                                      # bun test
 ```
 
-## Releasing
-
-Publishing is driven by **GitHub releases**, never by a push
-([`.github/workflows/publish.yml`](.github/workflows/publish.yml)):
-
-```bash
-bun pm version minor -m "chore(release): v%s"   # bump + commit + tag v0.5.0
-git push origin main --tags
-# then publish the release on GitHub → the workflow publishes to npm
-```
-
-The workflow checks out the released tag, installs, verifies the tag against the `package.json`
-version, typechecks, runs `bun test`, builds `dist/client`, packs a dry run, then runs `bun publish`.
-One thing to set up once:
+The screenshots, GIFs and the MP4 in [`docs/assets`](docs/assets) are captured from a scratch
+checkout running `MOCK=true` (`PORT=3123`) with Playwright, so they contain demo data only — never a
+real workspace.
 
-- GitHub environment **`NPM_TOKEN`** with a secret of the same name — a granular npm access token
-  with read/write on `ompchamber`, 2FA bypass enabled, and the `publish and stage` action (a
-  stage-only token is rejected: Bun has no `npm stage publish`). The job declares that environment,
-  so the token is readable only by the publish workflow; add required reviewers there to gate a
-  publish behind an approval.
+## Releasing
 
-A failed publish is retried from **Actions → Publish → Run workflow**, which leaves the release
-itself untouched.
+A push to `main` cuts the release — there is no manual version bump
+([`.github/workflows/release.yml`](.github/workflows/release.yml)):
+
+1. `semantic-release` reads the Conventional Commits since the last tag, decides the next
+   version, writes it into `package.json` and a `## [x.y.z]` section of `CHANGELOG.md`, commits
+   both, then creates the tag and the GitHub Release. Only `feat`, `fix`, `perf`, `refactor`, `docs`
+   and `revert` can move a version (`bumpStrict` in [`release.config.mjs`](release.config.mjs));
+   `chore`, `style`, `test`, `build` and `ci` are hidden and bump nothing on their own.
+2. The same run dispatches [`publish.yml`](.github/workflows/publish.yml), which checks out the tag,
+   verifies it against `package.json`, typechecks, runs `bun test`, builds `dist/client`, packs a
+   dry run, and runs `bun publish` behind the **`npm` environment** approval gate.
+
+Two things to set up once and one to never do:
+
+- GitHub environment **`npm`** with a secret `NPM_TOKEN`: a granular npm token with read/write on
+  `ompchamber`, 2FA bypass enabled and the `publish and stage` action (a stage-only token is
+  rejected — Bun has no `npm stage publish`). Add required reviewers there to gate a publish.
+- A failed publish is retried with `gh workflow run publish.yml -f tag=vX.Y.Z`, which leaves the
+  release itself untouched.
+- **Never** write a skip marker (`[skip ci]`, `[ci skip]`, `[no ci]`) into a message pushed to
+  `main` — it scans the whole message and silently skips the release run. Only the bot's release
+  commit carries one, so that it does not re-trigger the workflow.
 
 ## License
 

package/dist/client/index.html

@@ -1,8 +1,10 @@
 <!doctype html>
-<html lang="en" data-theme="paper">
+<html lang="en" data-theme="paper" data-theme-variant="light">
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
+    <!-- The theme's canvas color. The SSR shell rewrites this tag in place;
+         a second tag would be ignored, since Chrome reads the first. -->
     <meta name="theme-color" content="#faf8f3" />
     <meta name="mobile-web-app-capable" content="yes" />
     <meta name="apple-mobile-web-app-capable" content="yes" />
@@ -24,7 +26,7 @@
       href="https://fonts.googleapis.com/css2?family=Inter:ital,opsz,wght@0,14..32,100..900;1,14..32,100..900&display=swap"
     />
     <!--app-head-->
-  <script defer src="/static/js/markdown-vendor.71e43278b3.js"></script><script defer src="/static/js/shiki-vendor.cb8452ddcd.js"></script><script defer src="/static/js/77.8022a800b5.js"></script><script defer src="/static/js/index.5fe7a2cb64.js"></script><link href="/static/css/index.b938f4a693.css" rel="stylesheet"></head>
+  <script defer src="/static/js/markdown-vendor.71e43278b3.js"></script><script defer src="/static/js/shiki-vendor.cb8452ddcd.js"></script><script defer src="/static/js/77.0d81c74cf0.js"></script><script defer src="/static/js/index.c05535dbde.js"></script><link href="/static/css/index.5f630421b7.css" rel="stylesheet"></head>
   <body>
     <div id="app"></div>
     <!--app-bootstrap-->