@zerwiz/ymir 0.1.12 → 0.1.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +24 -0
- package/README.md +27 -0
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,4 +1,28 @@
|
|
|
1
1
|
|
|
2
|
+
## 2026-09-17 — 0.1.14: the panels reach the gate, and the fourth window ships
|
|
3
|
+
|
|
4
|
+
- **`@zerwiz/hlidskjalf` 0.1.1** — the package now declares its own `name`, `files` and the absence of `private`, and ships **`vite.config.ts`**. Without that config a packaged SPA is served by `vite preview` with **no `/api` proxy**, so every panel answered `index.html` and died on `Unexpected token '<'<`. That was the whole panel fault.
|
|
5
|
+
- **`@zerwiz/odrerir` 0.1.1** — ships its **`electron/`** half, so the fourth hall can have a window; its name is `@zerwiz/odrerir` and it is no longer marked private (npm refuses those, EPRIVATE).
|
|
6
|
+
- Both apps declared what ships **in their own repos**, instead of a manifest rewritten at publish time — which is how the wrong things shipped in the first place.
|
|
7
|
+
|
|
8
|
+
## 2026-09-17 — 0.1.13: the re-voiced seat arrives, and the packages are listed
|
|
9
|
+
|
|
10
|
+
- **`@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.
|
|
11
|
+
- **The README lists every package** on npm, and why the smithy is `@zerwiz/smidja-factory`.
|
|
12
|
+
|
|
13
|
+
## 2026-09-17 — the README lists the packages, and the pin moves to the re-voiced seat
|
|
14
|
+
|
|
15
|
+
- **The README says what is on npm.** Five packages serve — `@zerwiz/ymir` (the
|
|
16
|
+
distro) and the four surfaces it depends on — and the section says so with a
|
|
17
|
+
table, plus the one line that matters to a reader: *why the smithy is not
|
|
18
|
+
`@zerwiz/smiddja`*. That name was accepted twice and served never (package
|
|
19
|
+
document 404, website 403, republish refused as already published); it was
|
|
20
|
+
renamed to `@zerwiz/smidja-factory`, which resolves.
|
|
21
|
+
- **The distro's pin moves to `@zerwiz/sessrumnir@0.1.9`** — the seat that speaks
|
|
22
|
+
its own name rather than the fork's. A fresh install was still receiving the
|
|
23
|
+
old voice through the `0.1.8-alpha` pin.
|
|
24
|
+
- **`@zerwiz/ymir@0.1.13`** is the packet that carries them.
|
|
25
|
+
|
|
2
26
|
## 2026-09-17 — 0.1.12: the icons reach the live tree, and a missing surface is a failure
|
|
3
27
|
|
|
4
28
|
- **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
CHANGED
|
@@ -700,6 +700,33 @@ when the work will take a while, tells you plainly:
|
|
|
700
700
|
Your patience is noted, and it is earned.
|
|
701
701
|
```
|
|
702
702
|
|
|
703
|
+
### The packages — what is on npm
|
|
704
|
+
|
|
705
|
+
Six names were published; five serve. The distro **depends on the four
|
|
706
|
+
surfaces**, so one command brings the whole platform — and each can be installed
|
|
707
|
+
alone if you want only that hall.
|
|
708
|
+
|
|
709
|
+
```
|
|
710
|
+
packages[5]{package,what,live}:
|
|
711
|
+
"@zerwiz/ymir","the distro — the runtime, the doors, the installer, the plan","0.1.12"
|
|
712
|
+
"@zerwiz/hlidskjalf","the high seat — the control plane, the gate and the landing","0.1.0"
|
|
713
|
+
"@zerwiz/odrerir","the live hall — the board on :4322","0.1.0"
|
|
714
|
+
"@zerwiz/smidja-factory","the smithy — the agent factory, its skills and the visualizer on :8437","0.1.1"
|
|
715
|
+
"@zerwiz/sessrumnir","the seat-hall — the desktop where you speak with Brokk","0.1.9"
|
|
716
|
+
```
|
|
717
|
+
|
|
718
|
+
```bash
|
|
719
|
+
npm install -g @zerwiz/ymir # the distro AND the four surfaces (dependencies)
|
|
720
|
+
npm install -g @zerwiz/hlidskjalf # or one hall on its own
|
|
721
|
+
```
|
|
722
|
+
|
|
723
|
+
**Why the smithy's name is not `@zerwiz/smidja`.** It was published under that
|
|
724
|
+
name and the registry accepted it twice — `0.1.0`, then `0.1.1` — while serving
|
|
725
|
+
neither: the package document answered 404, the website 403, and a republish was
|
|
726
|
+
refused as *already published*. The name was retired and the smithy ships as
|
|
727
|
+
**`@zerwiz/smidja-factory`**, which resolves. A second look before publishing
|
|
728
|
+
costs less than explaining a name that never worked.
|
|
729
|
+
|
|
703
730
|
### Both shapes — a clone and a package are one tree
|
|
704
731
|
|
|
705
732
|
Ymir runs the same whether you **cloned** it or **installed** it from npm. The
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@zerwiz/ymir",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.14",
|
|
4
4
|
"description": "Ymir \u2014 the single-tenant agent operating system. Omarchy-first, host-aware, self-healing.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"homepage": "https://github.com/zerwiz/ymir",
|
|
@@ -60,9 +60,9 @@
|
|
|
60
60
|
"compliance": "bash .agents/skills/galdr-ymirsystem/scripts/compliance-check.sh"
|
|
61
61
|
},
|
|
62
62
|
"optionalDependencies": {
|
|
63
|
-
"@zerwiz/hlidskjalf": "
|
|
64
|
-
"@zerwiz/odrerir": "
|
|
65
|
-
"@zerwiz/sessrumnir": "0.1.
|
|
63
|
+
"@zerwiz/hlidskjalf": "0.1.1",
|
|
64
|
+
"@zerwiz/odrerir": "0.1.1",
|
|
65
|
+
"@zerwiz/sessrumnir": "0.1.9",
|
|
66
66
|
"@zerwiz/smidja-factory": "^0.1.0"
|
|
67
67
|
}
|
|
68
68
|
}
|