@sjawhar/pi-legion 19.29.4 → 19.29.5

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/legion.js CHANGED
@@ -29763,7 +29763,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
29763
29763
  // package.json
29764
29764
  var package_default = {
29765
29765
  name: "@sjawhar/pi-legion",
29766
- version: "19.29.4",
29766
+ version: "19.29.5",
29767
29767
  license: "Apache-2.0",
29768
29768
  type: "module",
29769
29769
  omp: {
@@ -62,10 +62,11 @@ itself, whoever parked it (`admission: queued a person's handover`, `source=appr
62
62
  approvals of a root's spec are not that handover and still come as notices: a carried approval,
63
63
  which Dispatch writes in the person's name with a reason that begins
64
64
  `Carried forward from the approval of version`, when their answer to a decision block was the
65
- whole change since the version they approved or when a later version's text is the text of the
66
- version they approved, and an approval on a root that keeps a Dispatch parent, as a child a linger
67
- handed to Legion does. The other spec notices are a request for changes and an approval of a
68
- document that is not the root's primary one.
65
+ whole change since the version they approved, when a later version's text is the text of the
66
+ version they approved, or when a later version's text is that text with the questions a reopen
67
+ opened again, and an approval on a root that keeps a Dispatch parent, as a child a linger handed
68
+ to Legion does. The other spec notices are a request for changes and an approval of a document
69
+ that is not the root's primary one.
69
70
 
70
71
  ## Deciding
71
72
 
@@ -3,9 +3,8 @@
3
3
  A person who mentions the Legion Slack app in one of the project's Slack channels is talking to
4
4
  you, and you answer in that thread. The `Slack channels:` line of your system prompt names each
5
5
  channel `legion.yaml` gives the project (`projects.<KEY>.slack_channels`). Only the controller the
6
- daemon launches has one: the Slack bot token is the Legion daemon service's, which the secrets
7
- broker grants to that service's own pods alone. With no such line the project has no channel, and
8
- nothing here applies.
6
+ daemon launches has one, because the daemon names a project's channels to that controller alone.
7
+ With no such line the project has no channel, and nothing here applies.
9
8
 
10
9
  ## Your session subscribes for you
11
10
 
@@ -101,7 +100,8 @@ a thread read, `channels:history` in a public channel or `groups:history` in a p
101
100
  person in the workspace can fix either, so say so in the next daily report rather than retrying.
102
101
  When it answers that the secrets broker has not granted `LEGION_SLACK_BOT_TOKEN` (its request waits
103
102
  for approval, or was denied), nothing was posted and no reply can be until the operator stores the
104
- token with owner `legion-daemon` and tier `agent`: name the error in the next daily report.
103
+ token as a shared agent secret, owner `shared` and tier `agent`: name the error in the next daily
104
+ report.
105
105
 
106
106
  ## Decide what the person wants
107
107
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.29.4",
3
+ "version": "19.29.5",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {