@gpambrozio/paseo-herald 0.2.2 → 0.2.4

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 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.4] — 2026-09-19
11
+
12
+ ### Fixed
13
+
14
+ - **Installs from npm — verified this time.** 0.2.3 fixed one missing dependency and left a second
15
+ one behind, so the install still failed the same way. Both are gone, and the published package was
16
+ installed on a real daemon to prove it rather than reasoned about.
17
+
18
+ ## [0.2.3] — 2026-09-19
19
+
20
+ ### Fixed
21
+
22
+ - **Installs from npm.** The npm install added in 0.2.1 never actually worked for Herald: it
23
+ failed while being built, complaining about a missing dependency, and the plugin did not
24
+ install at all. Installing from the repository was unaffected, and so was every version
25
+ already running.
26
+
10
27
  ## [0.2.2] — 2026-09-19
11
28
 
12
29
  ### Fixed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gpambrozio/paseo-herald",
3
- "version": "0.2.2",
3
+ "version": "0.2.4",
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/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 "@getpaseo/client";
8
+ import type { PaseoApi } from "./host-types";
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 "@getpaseo/client";
18
+ import type { PaseoApi } from "./host-types";
19
19
  import type {
20
20
  PluginHookAgent,
21
21
  PluginHookContext,
@@ -0,0 +1,28 @@
1
+ /**
2
+ * Paseo's types, taken from the one package the host actually provides.
3
+ *
4
+ * A running plugin is given `@getpaseo/plugin`. It is not given
5
+ * `@getpaseo/client` or `@getpaseo/protocol`, which are devDependencies here —
6
+ * and an npm install runs `--omit=dev`, so neither is on disk. The daemon's
7
+ * runtime-boundary plugin resolves every import reachable from an entry, type
8
+ * imports included, and fails the *install* when one is missing. A directory or
9
+ * Git install never shows this, because `npm install` in the folder has put the
10
+ * whole SDK there; `server/sdk-types.ts` gets away with importing
11
+ * `@getpaseo/client` only because nothing imports *it*.
12
+ *
13
+ * So every Paseo type this plugin needs is projected out of `@getpaseo/plugin`,
14
+ * which re-declares them structurally. Same types, no dependency. Add to this
15
+ * file rather than reaching for the upstream package.
16
+ */
17
+ import type {
18
+ PluginHandlerContext,
19
+ PluginLifecycleEvents,
20
+ } from "@getpaseo/plugin/server";
21
+
22
+ export type PaseoApi = PluginHandlerContext["paseo"];
23
+
24
+ export type AgentTimelineItem =
25
+ PluginLifecycleEvents["agent.turn_ended"]["timeline"][number];
26
+
27
+ export type AgentPermissionRequest =
28
+ PluginLifecycleEvents["agent.permission_requested"]["request"];
@@ -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 "@getpaseo/client";
23
+ import type { PaseoApi } from "./host-types";
24
24
 
25
25
  import type { AttentionEntry } from "../shared/herald";
26
26
  import type { AttentionStore } from "./store";
@@ -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 "@getpaseo/client";
12
+ import type { PaseoApi } from "./host-types";
13
13
  import { DEFAULT_SUMMARY_PROMPT, type AttentionReason, type PromptPlaceholder } from "../shared/herald";
14
14
  import { displayName, firstWords, plainText } from "./timeline";
15
15
 
@@ -4,7 +4,7 @@
4
4
  * here touches the network or a model, which is what makes it the part with
5
5
  * tests.
6
6
  */
7
- import type { AgentPermissionRequest, AgentTimelineItem } from "@getpaseo/protocol/agent-types";
7
+ import type { AgentPermissionRequest, AgentTimelineItem } from "./host-types";
8
8
 
9
9
  import type { AttentionReason } from "../shared/herald";
10
10
 
@@ -4,7 +4,7 @@
4
4
  * change rarely and every event would otherwise page through the workspace
5
5
  * list.
6
6
  */
7
- import type { PaseoApi } from "@getpaseo/client";
7
+ import type { PaseoApi } from "./host-types";
8
8
 
9
9
  export const WORKSPACE_TITLE_TTL_MS = 5 * 60 * 1000;
10
10