@mercury-fw/channel-google-chat 0.3.0 → 0.5.0

package/CHANGELOG.md

@@ -1,5 +1,43 @@
 # @mercury-fw/channel-google-chat
 
+## 0.5.0
+
+### Minor Changes
+
+- a7f2f13: A user directory decides who people are and what they may make Mercury do.
+
+  - An app can declare a `directory` in `mercury.config.ts`. Given whoever a channel says is talking, it returns the person with their roles. The person's key is `<directory name>:<id>`, so one person reached from several channels keeps one private area, one memory and one set of confirmations.
+  - With a directory the instance is closed. Someone it doesn't know gets a refusal and nothing runs, unless `access.unknown` is `"allow"`; `access.unknownMessage` sets what they're told. A directory that can't be reached, or fails to load, refuses everyone but the terminal. Answers are cached for five minutes, so a revoked role stops counting within that time.
+  - `mercury.act-as-self` (every plugin) or `mercury.act-as-self.<plugin>` (one) lets a person make Mercury act with its own identity.
+    - A plugin acting as Mercury, such as atlassian-admin, is offered only to those people, and on the terminal.
+    - A plugin acting as the person also gives them each tool a second time, as `<tool>AsMercury`.
+    - Every call made as Mercury for someone is logged with who asked.
+  - `access.plugins` restricts a plugin to some roles. Prompts, skills and the manifest follow what each person is offered.
+  - New package `@mercury-fw/directory-static`: people, their identities on each channel and their roles, listed in `DIRECTORY_STATIC_PEOPLE`.
+  - The channel contract is at version 5:
+    - `ChannelRuntimeContext.admit` says whether the core talks to a caller;
+    - the reads are per person and async, the manifest included;
+    - `DirectoryPlugin` is the directory contract;
+    - `Principal` no longer carries `roles`.
+  - `channel-http` answers `403` to a caller the directory doesn't know and `503` when it can't be reached, on every route.
+  - `auth-static` refuses `roles` in `AUTH_STATIC_TOKENS`: roles come from the directory.
+
+## 0.4.0
+
+### Minor Changes
+
+- 0739f77: A plugin acts as the person Mercury is talking to, who logs in to the service through Mercury.
+
+  - Plugin contract version 4: a plugin declares `actsAs: "person" | "mercury"`, and one acting as the person contributes a `login`; its tools get the turn's `person` and `requireLogin` in their context.
+  - A person is offered only the plugins acting as the person: their prompt fragments, skills and tools. A plugin acting as Mercury, or declaring nothing, is offered on the terminal only until people can be allowed to make Mercury act as itself; the startup log names it.
+  - `createCliTool` adds `--user` with the person's id to every command, staged confirmations included, and when the CLI exits with code 3 (not logged in) returns their login instead. `createCliPersonLogin` builds a plugin's `login` on a CLI's two-step remote login. A failed `runCli` carries `exitCode`.
+  - Channel contract version 4: channels get `logins` (`accept` a callback URL, `complete` a login) and `detectLoginRequired`.
+  - The HTTP channel, with `HTTP_SURFACE_PUBLIC_URL` set, streams a `login` event with the link to open and takes the person back at `GET /login/callback`, public and protected by the single-use state.
+  - `mercury.cliCredentials` can declare `userSetup`, run by `mfw credentials setup <plugin> --user-app`: the app people log in through, set up without logging anyone in.
+  - plugin-jira and plugin-bitbucket act as the person, on CLIs 2.3.0: set up their people's app with `--user-app` and register `<HTTP_SURFACE_PUBLIC_URL>/login/callback` on it. Jira's skill now says `currentUser()` is the person.
+  - plugin-atlassian-admin acts as Mercury, on CLI 0.2.0, whose `init` asks for the key without echoing it: until permissions exist it's available on the terminal only.
+  - A third-party plugin needs `apiVersion: 4` to load, and `actsAs: "person"` with a `login` to be offered to people.
+
 ## 0.3.0
 
 ### Minor Changes

package/index.ts

@@ -22,7 +22,7 @@ function require(env: ChannelRuntimeContext["env"], name: string): string {
 export const googleChatChannel: ChannelPlugin = {
   // The contract this channel is written for, as a literal: importing
   // CHANNEL_API_VERSION would report whichever contract is installed.
-  apiVersion: 3,
+  apiVersion: 5,
   name: "google-chat",
   build: (ctx) => {
     // No subscription configured ⇒ this instance simply doesn't run Google Chat.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mercury-fw/channel-google-chat",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -34,7 +34,7 @@
     "@mercury-fw/channel-types": ">=0.36.0 <1.0.0"
   },
   "devDependencies": {
-    "@mercury-fw/channel-types": "0.36.0",
+    "@mercury-fw/channel-types": "0.42.0",
     "@mercury-fw/typescript-config": "*",
     "@types/bun": "^1.4.2",
     "typescript": "^6.0.3"