@sjawhar/pi-envoy 16.36.2 → 16.37.0

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/dist/envoy.js CHANGED
@@ -42661,7 +42661,7 @@ var import_nats2 = __toESM(require_mod4(), 1);
42661
42661
 
42662
42662
  // package.json
42663
42663
  var name = "@sjawhar/pi-envoy";
42664
- var version2 = "16.36.2";
42664
+ var version2 = "16.37.0";
42665
42665
  var package_default = {
42666
42666
  name,
42667
42667
  version: version2,
@@ -21,8 +21,8 @@ agent-secrets NAME... [--reason TEXT] [--wait DURATION] [--ttl DURATION] -- <com
21
21
  with some of its secrets missing (`cmdExec`, `packages/envoy/cmd/agent-secrets/main.go`).
22
22
  - `--reason` is necessary wherever a person approves: a request that names a secret someone must
23
23
  decide, and carries none, is denied whole. Say what the credential is for, in a sentence the
24
- approver can decide on. A request every name of which is granted at once reaches nobody and
25
- needs none.
24
+ approver can decide on, and name in it the issue you work on, by its key (below). A request
25
+ every name of which is granted at once reaches nobody and needs none.
26
26
  - `agent-secrets --help` holds the rest: the flags that narrow a GitHub App token
27
27
  (`--github-owner`, `--github-repo`, `--github-read-only`), and how long a grant lasts.
28
28
  - A narrowing and the airlock do not go together. Ask for a narrowing in a run whose grant holds
@@ -151,6 +151,24 @@ refusal that is permanent; 126 and 127 from `agent-secrets register --exec`, who
151
151
  run or was not found; and 129, 130, 131 and 143 from a signal at the value prompt of
152
152
  `agent-secrets secret create` or `secret set`. `agent-secrets --help` lists them all.
153
153
 
154
+ ## Asking so a model judge can decide it
155
+
156
+ Your deployment may run a model judge over a narrow class of the requests that would otherwise
157
+ wait for a person. Three things in your own command decide whether a request can fall in that
158
+ class:
159
+
160
+ - One secret. A request that names two is outside it.
161
+ - `--ttl 15m`, or less. A longer one is outside it. With no `--ttl`, the judge reads the lifetime
162
+ the broker gives instead: 15 minutes for a human-tier secret, which is inside it, and the whole
163
+ session for a secret tagged `default-grant=session`, which is outside it. Pass `--ttl 15m`.
164
+ - The key of the issue you work on in `--reason`, for an issue that is not done.
165
+
166
+ The rules of your deployment decide which secrets the judge may take, and you are told none of
167
+ them, so ask this way and wait as you would anyway. One class is never judged, whatever those
168
+ rules say: a secret tagged as an administrator's, of which a person approves every release. The
169
+ judge approves a request in its class or leaves it for the person who approves it today, and it
170
+ never denies. Every other request waits for that person, as it does now.
171
+
154
172
  ## Waiting, and a grant you already hold
155
173
 
156
174
  - `--wait` waits 30 minutes by default. A session that must not block passes `--wait 0s`, reads the
@@ -169,7 +187,8 @@ The broker tells a session no names. A name comes from your deployment instructi
169
187
  prompt, a skill, or the issue you work on. There is no list to browse and nothing to guess.
170
188
 
171
189
  - Request a secret only to use it for the work in front of you. A request made to learn whether a
172
- secret exists reaches a person's Inbox.
190
+ secret exists is recorded against your session with the reason you signed, and it reaches a
191
+ person's Inbox unless the model judge decides it first.
173
192
  - `UNKNOWN_SECRET` and a denial are final. Do not ask again, and do not try a name of your own.
174
193
  - A secret that a service owns, such as `LEGION_SLACK_BOT_TOKEN`, goes to that service's own pods
175
194
  and VMs and to nothing else: `Evaluate` in `packages/envoy/internal/broker/policy/policy.go`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-envoy",
3
- "version": "16.36.2",
3
+ "version": "16.37.0",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {