@mmmbuto/nexuscrew 0.9.10 → 0.9.12
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 +41 -0
- package/frontend/dist/assets/{index-DBGNS4gP.js → index-CBoobbt_.js} +32 -32
- package/frontend/dist/assets/index-CWMKoCx-.css +32 -0
- package/frontend/dist/index.html +2 -2
- package/frontend/dist/version.json +1 -1
- package/lib/fleet/managed.js +131 -3
- package/lib/fleet/runtime.js +14 -0
- package/lib/mcp/server.js +4 -0
- package/package.json +1 -1
- package/frontend/dist/assets/index-CIJoChF1.css +0 -32
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,47 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to NexusCrew are tracked here.
|
|
4
4
|
|
|
5
|
+
## 0.9.12 — 2026-08-22 — "Build After The Bump"
|
|
6
|
+
|
|
7
|
+
- **Fixes 0.9.11, which would not start.** `frontend/dist/version.json` said
|
|
8
|
+
`0.9.10` while the server said `0.9.11`, so the UI refused with «incomplete
|
|
9
|
+
installation: frontend and server do not match». Everything else in that
|
|
10
|
+
package was consistent; that one byte was enough. The cause is ordering:
|
|
11
|
+
`vite.config.js` writes that file from `pkg.version` **at build time**, and
|
|
12
|
+
the bundle had been built before the version was raised. **Use 0.9.12; 0.9.11
|
|
13
|
+
is deprecated.**
|
|
14
|
+
|
|
15
|
+
- **A test now asserts what a checklist used to.** The frontend/package version
|
|
16
|
+
match had been verified by hand at every release since 0.8.2 — and a check
|
|
17
|
+
that lives only in a list is skipped the day someone is in a hurry. It now
|
|
18
|
+
fails on its own, and it was seen failing on a wrong value before it was
|
|
19
|
+
trusted on the right one.
|
|
20
|
+
|
|
21
|
+
## 0.9.11 — 2026-08-22 — "The Cell Gets Its Own Words"
|
|
22
|
+
|
|
23
|
+
- **A `vl` cell now starts with its own prompt and the model you picked in the
|
|
24
|
+
UI.** It was the only engine that came up bare: the runtime had a branch for
|
|
25
|
+
it that did nothing, and the code path that hands a cell its prompt skipped
|
|
26
|
+
`vl` explicitly. The prompt is now written to a private per-cell file
|
|
27
|
+
(`0600`, atomic replace, symlinks refused, credentials never written there)
|
|
28
|
+
and passed by path, and the model/provider/base-url travel as environment.
|
|
29
|
+
A version gate compares the binary FIELD BY FIELD, so an older `vl` degrades
|
|
30
|
+
to the previous behaviour instead of being handed a flag it cannot parse —
|
|
31
|
+
and when it degrades it says so in the `/fleet/up` payload rather than
|
|
32
|
+
failing quietly.
|
|
33
|
+
|
|
34
|
+
- **"Inbox" in the paperclip menu: upload a file without the cell reading it.**
|
|
35
|
+
File/Camera/Gallery upload the attachment AND put its path in the composer,
|
|
36
|
+
so the next Send makes the model read it — and a model that cannot take
|
|
37
|
+
images errors out and forces a restart. The new item keeps the file in the
|
|
38
|
+
inbox, reachable from `nc_inbox` and the Files panel, and leaves the composer
|
|
39
|
+
untouched: the operator decides when, and whether, it gets read. Contributed
|
|
40
|
+
by @sadoc1184-droid; the bundle shipped here was rebuilt from source on our
|
|
41
|
+
side rather than taken from the pull request.
|
|
42
|
+
|
|
43
|
+
- Terminal selection: xterm's EXCLUSIVE end is converted at the boundary, so
|
|
44
|
+
consumers no longer see it as inclusive.
|
|
45
|
+
|
|
5
46
|
## 0.9.10 — 2026-08-19 — "What The Hand Expects"
|
|
6
47
|
|
|
7
48
|
- **Selecting text now behaves the way a hand expects it to.** 0.9.9 made the
|