ompchamber 2.0.2 → 3.1.0

package/README.md

@@ -249,15 +249,16 @@ panels, the BTW subsystem, the PTY terminal and the build/dev loop.
 ## Development
 
 ```bash
-bun run dev            # watched server + client rebuild
+bun run dev            # watched server; the client bundle is built on demand
 bun run dev:lan        # same, bound to the LAN
-bun run dev:server     # server only (bun --hot)
-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.
+One process. Bun serves the HTML shell and bundles its assets itself, so there is no separate
+client watcher to run and no build step before the first request: saving a server file restarts the
+server, saving a client file is pushed to the browser over HMR (`import.meta.hot`, wired by Bun).
+
+`bun run build` is only needed to produce the production bundle — `scripts/build-client.ts` writes
+`dist/client`, which `serve --prod` runs.
 
 Verification gates, all mandatory:
 
@@ -279,18 +280,37 @@ A push to `main` cuts the release — there is no manual version bump
 
 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.
+   both, then creates the tag and the GitHub Release.
 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.
+   dry run, and runs `bun publish`.
+
+What a commit does to the version is one table, in
+[`release/release-rules.js`](release/release-rules.js), and `release/bump.test.js` asserts it:
+
+| Commit | Version |
+| --- | --- |
+| `feat` | minor |
+| `fix`, `perf`, `revert` | patch |
+| `feat!` / `fix!` / `perf!` / `refactor!`, or a `BREAKING CHANGE:` footer | major |
+| `docs`, `refactor`, `chore`, `style`, `test`, `build`, `ci` | no release |
+
+Two of those rows exist because the toolchain's own defaults are wrong here: a `!` on a type that
+cannot carry a breaking change (`chore!`, `docs!`, an unknown `foo!`) used to cut a major version
+through the analyzer's built-in `{ breaking: true }` fallback, and the parser's note regex is
+case-insensitive, so any body line starting with `breaking change` — colon optional — counted as a
+breaking note. The second one is not hypothetical: a `docs` commit whose body wrapped onto
+`breaking-change (!) footer` cut **v1.0.0** where the `feat`s in the range asked for v0.9.0, and the
+changelog printed that prose as its breaking note. Both are fixed in `release/release-rules.js`, and
+both are locked by `release/bump.test.js`.
+
+A `BREAKING CHANGE:` footer is therefore read only in uppercase, and only where the type allows it.
 
 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.
+  rejected — Bun has no `npm stage 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

package/bunfig.toml

@@ -0,0 +1,11 @@
+# Bun-specific configuration. `package.json` and `tsconfig.json` keep everything
+# they already own; this file only holds what has no home there.
+#
+# `[serve.static]` is what Bun.serve reads when it bundles an HTML route — the
+# dev loop and `development: false` production both go through it. The same
+# plugin file is passed explicitly to `Bun.build` by scripts/build-client.ts,
+# because the AOT CLI does NOT read this section (verified: `bun build
+# --target=bun` emitted Tailwind's `@theme` verbatim and a stylesheet with zero
+# utility classes).
+[serve.static]
+plugins = ["./src/server/lib/bundler/css.ts"]

package/dist/client/index.html

@@ -15,10 +15,17 @@
       content="A light e-ink paper developer dashboard and AI Oh-My-Pi web view chamber for CI/CD deployments."
     />
     <title>OMPChamber</title>
-    <link rel="manifest" href="/manifest.webmanifest" />
-    <link rel="icon" type="image/svg+xml" href="/icon.svg" sizes="any" />
-    <link rel="icon" type="image/png" href="/icon-192x192.png" sizes="192x192" />
-    <link rel="apple-touch-icon" href="/apple-touch-icon.png" />
+    <!-- Relative, not absolute: Bun's HTML loader resolves every local `href`
+         against this file and emits a content-hashed copy, so `./public/icon.svg`
+         becomes `/icon-<hash>.svg`. An absolute `/icon.svg` is read as a module
+         specifier and fails the whole build with "Could not resolve". The
+         manifest's OWN icon entries stay absolute — Bun does not rewrite inside
+         a copied JSON file, and `public/` is served directly, so `/icon.svg`
+         resolves there. -->
+    <link rel="manifest" href="./static/manifest-bnyy75kt.webmanifest" />
+    <link rel="icon" type="image/svg+xml" href="./static/icon-d07z9dtz.svg" sizes="any" />
+    <link rel="icon" type="image/png" href="./static/icon-192x192-6gn5cr2f.png" sizes="192x192" />
+    <link rel="apple-touch-icon" href="./static/apple-touch-icon-dskx5sr3.png" />
     <link rel="preconnect" href="https://fonts.googleapis.com" />
     <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
     <link
@@ -26,10 +33,14 @@
       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.0d81c74cf0.js"></script><script defer src="/static/js/index.e6a257402a.js"></script><link href="/static/css/index.5f630421b7.css" rel="stylesheet"></head>
+  <link rel="stylesheet" crossorigin href="./static/js/index-n4wkqj7t.css"><script type="module" crossorigin src="./static/js/index-8t70jhyj.js"></script></head>
   <body>
     <div id="app"></div>
     <!--app-bootstrap-->
+    <!-- The client entry. rsbuild injected this tag into its own output; Bun's
+         HTML loader takes it from the source, which is why the file is now a
+         bundler entry rather than only a template the server reads. -->
+    
     <script>
       if ('serviceWorker' in navigator) {
         window.addEventListener('load', () => {