@gpambrozio/paseo-herald 0.2.1 → 0.2.3
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 +17 -0
- package/package.json +1 -1
- package/paseo-plugin.json +0 -1
- package/server/card.ts +1 -1
- package/server/hooks.ts +1 -1
- package/server/liveness.ts +1 -1
- package/server/paseo-api.ts +17 -0
- package/server/summarize.ts +1 -1
- package/server/workspaces.ts +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,23 @@ follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Every version
|
|
|
7
7
|
as `@gpambrozio/paseo-herald` and tagged here, so a version is something to install and a line to
|
|
8
8
|
read before you move.
|
|
9
9
|
|
|
10
|
+
## [0.2.3] — 2026-09-19
|
|
11
|
+
|
|
12
|
+
### Fixed
|
|
13
|
+
|
|
14
|
+
- **Installs from npm.** The npm install added in 0.2.1 never actually worked for Herald: it
|
|
15
|
+
failed while being built, complaining about a missing dependency, and the plugin did not
|
|
16
|
+
install at all. Installing from the repository was unaffected, and so was every version
|
|
17
|
+
already running.
|
|
18
|
+
|
|
19
|
+
## [0.2.2] — 2026-09-19
|
|
20
|
+
|
|
21
|
+
### Fixed
|
|
22
|
+
|
|
23
|
+
- **Loads on Paseo 0.8 again.** 0.8 rejects any manifest key it does not recognise, and the
|
|
24
|
+
previous release added one, so the plugin refused to load there at all. On 0.9 and newer nothing
|
|
25
|
+
was wrong and nothing changes now.
|
|
26
|
+
|
|
10
27
|
## [0.2.1] — 2026-09-19
|
|
11
28
|
|
|
12
29
|
### Added
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gpambrozio/paseo-herald",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.3",
|
|
4
4
|
"description": "Paseo plugin: speaks one sentence when an agent needs you, and lists everything waiting in a sidebar panel",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://github.com/gpambrozio/paseo-plugins/tree/main/herald",
|
package/paseo-plugin.json
CHANGED
package/server/card.ts
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
* failed — the daemon replaces the row live and on refetch. Rows live in the
|
|
6
6
|
* daemon's memory: they survive scroll and reconnect, not a daemon restart.
|
|
7
7
|
*/
|
|
8
|
-
import type { PaseoApi } from "
|
|
8
|
+
import type { PaseoApi } from "./paseo-api";
|
|
9
9
|
|
|
10
10
|
import type { AttentionEntry } from "../shared/herald";
|
|
11
11
|
import { HERALD_CARD_KIND, HERALD_CARD_VERSION, type HeraldCard } from "../shared/timeline";
|
package/server/hooks.ts
CHANGED
|
@@ -15,7 +15,7 @@
|
|
|
15
15
|
* the agent move on: a new turn, the permission answered, the agent
|
|
16
16
|
* archived. Paseo's own attention flag decides what the panel *lists*.
|
|
17
17
|
*/
|
|
18
|
-
import type { PaseoApi } from "
|
|
18
|
+
import type { PaseoApi } from "./paseo-api";
|
|
19
19
|
import type {
|
|
20
20
|
PluginHookAgent,
|
|
21
21
|
PluginHookContext,
|
package/server/liveness.ts
CHANGED
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
* Answers are cached for a short while so the clients' polling does not turn
|
|
21
21
|
* into one daemon fetch per entry per poll.
|
|
22
22
|
*/
|
|
23
|
-
import type { PaseoApi } from "
|
|
23
|
+
import type { PaseoApi } from "./paseo-api";
|
|
24
24
|
|
|
25
25
|
import type { AttentionEntry } from "../shared/herald";
|
|
26
26
|
import type { AttentionStore } from "./store";
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* `PaseoApi` without importing `@getpaseo/client`.
|
|
3
|
+
*
|
|
4
|
+
* The host provides `@getpaseo/plugin` to a running plugin; it does not provide
|
|
5
|
+
* `@getpaseo/client`. That distinction is invisible to a plugin installed from a
|
|
6
|
+
* directory or from Git, where `npm install` has already put the whole SDK on
|
|
7
|
+
* disk — but an npm install runs `--omit=dev`, so a devDependency is simply not
|
|
8
|
+
* there, and the daemon's runtime-boundary plugin fails the build for any
|
|
9
|
+
* *reachable* module that imports one. `server/sdk-types.ts` gets away with it
|
|
10
|
+
* only because nothing imports it.
|
|
11
|
+
*
|
|
12
|
+
* So the type is taken from where it is already re-exported, through a context
|
|
13
|
+
* the host hands every handler. Same type, no dependency.
|
|
14
|
+
*/
|
|
15
|
+
import type { PluginHandlerContext } from "@getpaseo/plugin/server";
|
|
16
|
+
|
|
17
|
+
export type PaseoApi = PluginHandlerContext["paseo"];
|
package/server/summarize.ts
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
* `server/hooks.ts` uses to recognise and ignore it; the id reported through
|
|
10
10
|
* `onHelperCreated` is the other.
|
|
11
11
|
*/
|
|
12
|
-
import type { PaseoApi } from "
|
|
12
|
+
import type { PaseoApi } from "./paseo-api";
|
|
13
13
|
import { DEFAULT_SUMMARY_PROMPT, type AttentionReason, type PromptPlaceholder } from "../shared/herald";
|
|
14
14
|
import { displayName, firstWords, plainText } from "./timeline";
|
|
15
15
|
|
package/server/workspaces.ts
CHANGED