@zerwiz/ymir 0.1.12 → 0.1.13

package/CHANGELOG.md

@@ -1,4 +1,22 @@
 
+## 2026-09-17 — 0.1.13: the re-voiced seat arrives, and the packages are listed
+
+- **`@zerwiz/sessrumnir` 0.1.9** — the seat that says Sessrúmnir and "Brokk is working", with the fork`s name gone from its source, its bundles, its installer and its package identity. Pinned so a fresh install receives it.
+- **The README lists every package** on npm, and why the smithy is `@zerwiz/smidja-factory`.
+
+## 2026-09-17 — the README lists the packages, and the pin moves to the re-voiced seat
+
+- **The README says what is on npm.** Five packages serve — `@zerwiz/ymir` (the
+  distro) and the four surfaces it depends on — and the section says so with a
+  table, plus the one line that matters to a reader: *why the smithy is not
+  `@zerwiz/smiddja`*. That name was accepted twice and served never (package
+  document 404, website 403, republish refused as already published); it was
+  renamed to `@zerwiz/smidja-factory`, which resolves.
+- **The distro's pin moves to `@zerwiz/sessrumnir@0.1.9`** — the seat that speaks
+  its own name rather than the fork's. A fresh install was still receiving the
+  old voice through the `0.1.8-alpha` pin.
+- **`@zerwiz/ymir@0.1.13`** is the packet that carries them.
+
 ## 2026-09-17 — 0.1.12: the icons reach the live tree, and a missing surface is a failure
 
 - **The launcher entries name the door** (`Exec=ymir hlidskjalf`, …) instead of an absolute path into whichever tree minted them — the fault that made every icon do nothing.

package/README.md

@@ -700,6 +700,33 @@ when the work will take a while, tells you plainly:
       Your patience is noted, and it is earned.
 ```
 
+### The packages — what is on npm
+
+Six names were published; five serve. The distro **depends on the four
+surfaces**, so one command brings the whole platform — and each can be installed
+alone if you want only that hall.
+
+```
+packages[5]{package,what,live}:
+  "@zerwiz/ymir","the distro — the runtime, the doors, the installer, the plan","0.1.12"
+  "@zerwiz/hlidskjalf","the high seat — the control plane, the gate and the landing","0.1.0"
+  "@zerwiz/odrerir","the live hall — the board on :4322","0.1.0"
+  "@zerwiz/smidja-factory","the smithy — the agent factory, its skills and the visualizer on :8437","0.1.1"
+  "@zerwiz/sessrumnir","the seat-hall — the desktop where you speak with Brokk","0.1.9"
+```
+
+```bash
+npm install -g @zerwiz/ymir          # the distro AND the four surfaces (dependencies)
+npm install -g @zerwiz/hlidskjalf    # or one hall on its own
+```
+
+**Why the smithy's name is not `@zerwiz/smidja`.** It was published under that
+name and the registry accepted it twice — `0.1.0`, then `0.1.1` — while serving
+neither: the package document answered 404, the website 403, and a republish was
+refused as *already published*. The name was retired and the smithy ships as
+**`@zerwiz/smidja-factory`**, which resolves. A second look before publishing
+costs less than explaining a name that never worked.
+
 ### Both shapes — a clone and a package are one tree
 
 Ymir runs the same whether you **cloned** it or **installed** it from npm. The

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerwiz/ymir",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "Ymir \u2014 the single-tenant agent operating system. Omarchy-first, host-aware, self-healing.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/zerwiz/ymir",
@@ -62,7 +62,7 @@
   "optionalDependencies": {
     "@zerwiz/hlidskjalf": "^0.1.0",
     "@zerwiz/odrerir": "^0.1.0",
-    "@zerwiz/sessrumnir": "0.1.8-alpha",
+    "@zerwiz/sessrumnir": "0.1.9",
     "@zerwiz/smidja-factory": "^0.1.0"
   }
 }