home-hosted 0.7.2 → 0.7.3

package/AGENTS.md

@@ -135,15 +135,19 @@ a minor without one.
   `repo`/`tag`/`asset` (which release carries it, for `ui-update`) and `unix` (when it was built).
   `UiService` carries those fields into the installed `$HHOSTED_HOME/.ui/ui.json` unchanged and adds
   `uploadedAt`/`files` of its own.
-- **Bumping a UI ships a new asset, so its `ui.json` is part of the change.** Any commit that alters
-  a UI under `uis/<name>/` bumps that `ui.json`'s `version` and sets `unix` to the commit's own epoch
-  seconds: patch for a fix, minor for a feature, and **major only for a rewrite or a restyle**. The
-  number is what tells a person how big the change is — `ui-update` prints it and holds it against
-  the release it is offering. `tag` is what pairs an official UI with its panel, and it is **stamped
-  by `build-uis.mjs`**, not trusted from the source file: a UI zip is built before its release is cut,
-  so the committed value is always a release behind the asset it ends up inside. The release workflow
-  passes `HHOSTED_UI_TAG`; anywhere else the build stamps `v<package.json version>`. Do not hand-edit
-  `tag` to chase a release — a stale one makes `ui-update` re-install the same UI on every boot.
+- **Bumping a UI ships a new asset, so its `ui.json` is part of the change — and it is bumped once,
+  when the commit is made, not on every edit.** A commit that alters what a UI *ships*
+  (`uis/<name>/src`, `public`, its build inputs — not `test/`, which is not in the asset) raises that
+  `ui.json`'s `version`: patch for a fix, minor for a feature, and **major only for a rewrite or a
+  restyle**. The number is what tells a person how big the change is — `ui-update` prints it and holds
+  it against the release it is offering. `unix` is that commit's own epoch, never a leftover from
+  whenever the file was edited: `scripts/stamp-uis.mjs` runs from the pre-commit hook, stamps it, and
+  refuses a commit that changed a shipped UI without raising its version. `tag` is what pairs an
+  official UI with its panel, and it is **stamped by `build-uis.mjs`**, not trusted from the source
+  file: a UI zip is built before its release is cut, so the committed value is always a release behind
+  the asset it ends up inside. The release workflow passes `HHOSTED_UI_TAG`; anywhere else the build
+  stamps `v<package.json version>`. Do not hand-edit `tag` to chase a release — a stale one makes
+  `ui-update` re-install the same UI on every boot.
 - `bin/home-hosted.mjs` — the published bin: `dist/cli.js`, or `src/cli.ts` through tsx when the
   build is missing (a linked checkout).
 - `scripts/` — `build-uis.mjs` (build one UI, optionally zip it), `typecheck-uis.mjs`,