@ctliz/agent-intercom-pi 0.14.1 → 0.14.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/README.md +18 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
|
|
20
20
|
## Pi 1.1 compatibility and codemode
|
|
21
21
|
|
|
22
|
-
Version 0.14.
|
|
22
|
+
Version 0.14.3 is tested with Pi 1.1.0. Version 0.14.0 was tested with Pi 1.0.0, and 0.13.0 with Pi 0.99.1. The development test baseline now uses Pi 1.1.0; host-provided Pi modules remain peer dependencies, not runtime dependencies. The existing protocol v4 broker, durable queues, acknowledgements, and cross-harness routing are unchanged.
|
|
23
23
|
|
|
24
24
|
Pi 1.0 defaults to fullscreen; set `tuiMode` to `"regular"` or launch with `--tui-mode regular` to retain terminal scrollback. Codemode's shorter declarations preserve Intercom's structured `{ ok, text, data }` results and team guidelines. To check tool existence in a script, use `"intercom_send" in tools`, not `typeof tools.intercom_send`, because unknown members now throw. Restart existing Pi processes to use a newly installed Pi version; `/reload` only reloads resources inside the running version.
|
|
25
25
|
|
|
@@ -41,7 +41,7 @@ Concurrent sends and independent asks are supported; do not create two unresolve
|
|
|
41
41
|
The package includes an `intercom-send` executable. Install the alias globally for a shell command, or run it without relying on Pi's private installation path:
|
|
42
42
|
|
|
43
43
|
```bash
|
|
44
|
-
npm exec --yes --package=@ctliz/
|
|
44
|
+
npm exec --yes --package=@ctliz/agent-intercom-pi@0.14.3 -- intercom-send worker 'Tests passed.'
|
|
45
45
|
```
|
|
46
46
|
|
|
47
47
|
It prints one JSON result with `accepted`, `delivered`, `messageId`, and optional failure `code`/`reason`. Exit status is zero only for acknowledged delivery. It inherits the routing scope, but never inherits `PI_INTERCOM_SESSION_ID` or `AGENT_INTERCOM_SESSION_ID`: every invocation registers an independent sender, leaves running Pi sessions intact, and disconnects after sending. It is send-only; use the session tools for reply-tracked asks.
|
|
@@ -163,7 +163,18 @@ Each pi session that has `pi-intercom` loaded and enabled connects to a tiny loc
|
|
|
163
163
|
## Install
|
|
164
164
|
|
|
165
165
|
```bash
|
|
166
|
-
pi install npm:@ctliz/
|
|
166
|
+
pi install npm:@ctliz/agent-intercom-pi
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
Starting with 0.14.3, `@ctliz/agent-intercom-pi` is the only npm release name. The legacy `@ctliz/pi-intercom` alias receives no new versions; its published history remains available. The 0.14.2 rename candidate was not published to npm. The GitHub repository and existing Git sources remain unchanged.
|
|
170
|
+
|
|
171
|
+
Existing `@ctliz/agent-intercom-pi` users do not need to switch packages. Update with `pi update npm:@ctliz/agent-intercom-pi`, then run `/reload` in open Pi sessions. If the configured source is pinned to a version, reinstall the unpinned source above to receive future update notifications.
|
|
172
|
+
|
|
173
|
+
If you installed the legacy alias, remove it before installing the supported name to avoid loading the same extension twice:
|
|
174
|
+
|
|
175
|
+
```bash
|
|
176
|
+
pi remove npm:@ctliz/pi-intercom
|
|
177
|
+
pi install npm:@ctliz/agent-intercom-pi
|
|
167
178
|
```
|
|
168
179
|
|
|
169
180
|
If you are coming from `connect.1`, read [Upgrading from `connect.1`](#upgrading-from-connect1-to-connect2) first — the package namespace changed and the two versions must not be installed side by side.
|
|
@@ -916,7 +927,7 @@ Use pi-messenger for multi-agent swarms working on a shared task. Use pi-interco
|
|
|
916
927
|
|
|
917
928
|
The `connect.1` tags, source commits, and published release assets are immutable and are not modified by this migration. Release notes may carry an explicit erratum, which corrects the description only and never moves a tag or replaces an asset.
|
|
918
929
|
|
|
919
|
-
|
|
930
|
+
The historical `connect.*` Git tags shown above remain available. For current Pi installations, use the npm package in [Install](#install).
|
|
920
931
|
|
|
921
932
|
## Limitations
|
|
922
933
|
|
|
@@ -939,10 +950,9 @@ git tag -a vX.Y.Z -m "vX.Y.Z"
|
|
|
939
950
|
git push origin vX.Y.Z
|
|
940
951
|
```
|
|
941
952
|
|
|
942
|
-
The release workflow verifies that the tag points into `main`, runs typecheck and
|
|
943
|
-
|
|
944
|
-
|
|
945
|
-
when a workflow is rerun.
|
|
953
|
+
The release workflow verifies that the tag points into `main` and the manifest name is `@ctliz/agent-intercom-pi`, runs typecheck and tests, publishes that one npm package with trusted OIDC provenance, and creates the GitHub Release. It does not publish or rewrite a second alias. Existing npm versions and GitHub Releases are skipped safely when a workflow is rerun.
|
|
954
|
+
|
|
955
|
+
The npm trusted publisher is configured on **`@ctliz/agent-intercom-pi`** for GitHub owner `ctliz`, repository `agent-intercom-pi`, workflow filename `release.yml`, with no environment name (this workflow does not use one). Authorization is package-specific. Changing this account-side setting requires npm package-owner access; a repository commit alone cannot grant it. The workflow uses OIDC without a placeholder registry token.
|
|
946
956
|
|
|
947
957
|
## License
|
|
948
958
|
|
package/package.json
CHANGED