@akanjs/cli 3.0.0-alpha.56 → 3.0.0-alpha.57
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/.build-stamp
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
5ed385877dec10031dfbaab1aae02c9019d7cdc3d536cc04ae64386c2d423949
|
|
@@ -139,6 +139,14 @@ apps and libs never import it directly (`no-import-external-library`) — everyt
|
|
|
139
139
|
declaring a hook tool of the same name works at the root and **not inside a zone**, where the hook entry is
|
|
140
140
|
registered under its scope-prefixed name and never collides — `builtins` is the zone's answer. A tool the screen
|
|
141
141
|
declares under a built-in name is the screen's, not the runtime's, so `builtins={false}` leaves it standing.
|
|
142
|
+
- **`<Agent.History load save clear onCompact />` backs a zone's transcript from a leaf inside it**, instead of
|
|
143
|
+
through `persist` on whoever builds the session. A function cannot cross the server/client boundary as a prop,
|
|
144
|
+
so `persist={myStore}` makes every ancestor up to the zone a client component; mounted this way the only client
|
|
145
|
+
module is the leaf, and `Agent.Zone` and the chat inside it stay server-assembled. Same shape as `Agent.Guide`,
|
|
146
|
+
and it renders nothing. Restoring follows the session's one rule — it lands only while nothing has happened to
|
|
147
|
+
the conversation yet — so mounting with the zone restores and mounting later saves from there on, with the
|
|
148
|
+
store never asked for a transcript that would be discarded. `session.setHistory` / `setOnCompact` are the same
|
|
149
|
+
thing for a session an app built itself.
|
|
142
150
|
- **A zone can be handed a session instead of building one**: `<Agent.Zone session={mine} onSession={…}>`. The app
|
|
143
151
|
then owns it, so unmounting the zone leaves it running — the opposite of a session the zone made, which it
|
|
144
152
|
aborts. `onSession` fires either way, for a page that wants to send into the conversation from outside it.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@akanjs/cli",
|
|
3
|
-
"version": "3.0.0-alpha.
|
|
3
|
+
"version": "3.0.0-alpha.57",
|
|
4
4
|
"sourceType": "module",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"publishConfig": {
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"@langchain/openai": "^1.4.6",
|
|
35
35
|
"@tailwindcss/node": "^4.3.0",
|
|
36
36
|
"@trapezedev/project": "^7.1.4",
|
|
37
|
-
"akanjs": "3.0.0-alpha.
|
|
37
|
+
"akanjs": "3.0.0-alpha.57",
|
|
38
38
|
"chalk": "^5.6.2",
|
|
39
39
|
"commander": "^14.0.3",
|
|
40
40
|
"dayjs": "^1.11.20",
|