@llblab/pi-state-flow 0.27.2 → 0.27.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/CHANGELOG.md +5 -0
- package/dist/lib/telegram.js +2 -6
- package/dist/package.json +1 -1
- package/docs/architecture.md +1 -1
- package/docs/usage.md +2 -2
- package/lib/telegram.ts +2 -6
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,11 @@
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 0.27.3: Minimal Telegram inspection menu
|
|
8
|
+
|
|
9
|
+
- `Single participating-owner list`: Removes the duplicated Participating scopes summary and the Session-exclusion notice from the Telegram section. The Inspect participating memory list and its buttons are now the only statement of participating owners, so no line can disagree with the available actions.
|
|
10
|
+
- `Selection-independent Effective line`: Replaces the generated `global → cwd → session` enumeration and its three-owner variant with one fixed sentence about overlay order. A single selected owner shows only that owner, without an Effective line, button or explanatory tail.
|
|
11
|
+
|
|
7
12
|
## 0.27.2: Consistency & Simplification
|
|
8
13
|
|
|
9
14
|
- `Documentation reconciliation`: Correct current release/public-module status to the published 0.27.0/0.27.1 behavior, including metadata v4 retention and external-root tools/context/producers. Distinguish the six-plane internal seam from public registration and mark M4/M5 deferrals as historical without upgrading their review verdicts. No production behavior or compatibility policy changed.
|
package/dist/lib/telegram.js
CHANGED
|
@@ -57,7 +57,6 @@ export function buildStateFlowSectionView(snapshot, callbackData) {
|
|
|
57
57
|
inspectionRows.push([]);
|
|
58
58
|
inspectionRows.at(-1).push({ text: STATE_FLOW_SCOPE_LABELS[scope], callback_data: callbackData("inspect", scope) });
|
|
59
59
|
}
|
|
60
|
-
const named = scopes.map(scope => `<code>${scope}</code>`).join(" → ");
|
|
61
60
|
const modes = STATE_FLOW_MODES.map((mode) => ({
|
|
62
61
|
text: `${mode === snapshot.mode ? STATE_FLOW_SELECTED_MARKERS[mode] : "⚫️"} ${STATE_FLOW_MODE_LABELS[mode]}`,
|
|
63
62
|
callback_data: callbackData(mode),
|
|
@@ -76,15 +75,12 @@ export function buildStateFlowSectionView(snapshot, callbackData) {
|
|
|
76
75
|
`<code>-</code> <code>passive</code>: regular chat with memory tools; available memory from the selected ${scopes.length === 1 ? "scope" : "scopes"} enters the agent's context.`,
|
|
77
76
|
"<code>-</code> <code>active</code>: same memory access; each completed answer closes a cycle, and the next request starts from saved state, not the full chat.",
|
|
78
77
|
"",
|
|
79
|
-
`<b>Participating scopes:</b> ${named}`,
|
|
80
|
-
...(!scopes.includes("session") ? ["New answers are delivered, not stored: Session is excluded."] : []),
|
|
81
|
-
"",
|
|
82
78
|
"<b>Inspect participating memory</b> — view available stored state even in Off:",
|
|
83
79
|
"",
|
|
84
80
|
...scopes.map(scope => `<code>-</code> <code>${scope}</code>: ${STATE_FLOW_SCOPE_DESCRIPTIONS[scope]}`),
|
|
85
81
|
...(scopes.length > 1
|
|
86
|
-
? [
|
|
87
|
-
: [
|
|
82
|
+
? ["<code>-</code> <code>effective</code>: merged state of the selected scopes in order from the general to the specific."]
|
|
83
|
+
: []),
|
|
88
84
|
].join("\n"),
|
|
89
85
|
parseMode: "html",
|
|
90
86
|
replyMarkup: { inline_keyboard: [
|
package/dist/package.json
CHANGED
package/docs/architecture.md
CHANGED
|
@@ -840,7 +840,7 @@ Status is a projection of the selected runtime and semantic view, not a second s
|
|
|
840
840
|
**Telegram menu layout.** The optional Telegram leaf adapter shows, in order:
|
|
841
841
|
|
|
842
842
|
1. the current mode as a monospace value in the submenu heading;
|
|
843
|
-
2. matching Mode and Inspect participating memory headings (a long-dash-separated description ending in a colon), with
|
|
843
|
+
2. matching Mode and Inspect participating memory headings (a long-dash-separated description ending in a colon), with selection-aware settings-style descriptions; the captured participating owners are named only by that Inspect list, with no separate scope-summary or Session-exclusion line;
|
|
844
844
|
3. one radio row `Off | Passive | Active`, where selected Off uses 🟣, Passive 🟡 or Active 🟢, and inactive choices use ⚫️;
|
|
845
845
|
4. only captured participating owner-inspection buttons, plus Effective for two or three owners. A sole owner is already effective. Inspection stays explicit and available in all three modes; unavailable memory is not invented.
|
|
846
846
|
|
package/docs/usage.md
CHANGED
|
@@ -236,9 +236,9 @@ When `pi-telegram` is available, its main-menu section shows `State Flow: active
|
|
|
236
236
|
- The submenu heading shows the current value in monospace.
|
|
237
237
|
- The bold Mode heading uses a long dash, a description ending in a colon, and a blank line before its settings-style list. Each line has a monospaced minus and lowercase monospaced mode value, then a plain colon and description.
|
|
238
238
|
- The descriptions progress from regular chat with no memory (Off, the new-session default), to ordinary chat with memory tools and an available combined memory view (Passive), to the same memory access with completed answers followed by memory-first continuation (Active). They do not claim a new physical Pi session or disabled native compaction.
|
|
239
|
-
-
|
|
239
|
+
- The captured participating owners are named by the Inspect participating memory list below, not a separate line; later default edits do not replace an existing session choice. Mode/help text describes only that set.
|
|
240
240
|
- The bold Inspect participating memory heading follows the same long-dash, description, colon and blank-line pattern. Only selected owners get a monospaced description and direct button; this is not a scope chooser.
|
|
241
|
-
- With one selected owner
|
|
241
|
+
- With one selected owner there is no separate effective state: the agent reads that owner directly, so neither an Effective line nor button appears. With two or three, Effective shows the validated available overlay of those selected owners only, in Global→CWD→Session order. Excluded owners do not contribute or gain an inspection action. The Effective description is a fixed sentence, not an owner enumeration: the list above already names the selected owners.
|
|
242
242
|
|
|
243
243
|
**Memory inspection:**
|
|
244
244
|
|
package/lib/telegram.ts
CHANGED
|
@@ -179,7 +179,6 @@ export function buildStateFlowSectionView(
|
|
|
179
179
|
if (index % 2 === 0) inspectionRows.push([]);
|
|
180
180
|
inspectionRows.at(-1)!.push({ text: STATE_FLOW_SCOPE_LABELS[scope], callback_data: callbackData("inspect", scope) });
|
|
181
181
|
}
|
|
182
|
-
const named = scopes.map(scope => `<code>${scope}</code>`).join(" → ");
|
|
183
182
|
const modes: StateFlowTelegramButton[] = STATE_FLOW_MODES.map((mode) => ({
|
|
184
183
|
text: `${mode === snapshot.mode ? STATE_FLOW_SELECTED_MARKERS[mode] : "⚫️"} ${STATE_FLOW_MODE_LABELS[mode]}`,
|
|
185
184
|
callback_data: callbackData(mode),
|
|
@@ -198,15 +197,12 @@ export function buildStateFlowSectionView(
|
|
|
198
197
|
`<code>-</code> <code>passive</code>: regular chat with memory tools; available memory from the selected ${scopes.length === 1 ? "scope" : "scopes"} enters the agent's context.`,
|
|
199
198
|
"<code>-</code> <code>active</code>: same memory access; each completed answer closes a cycle, and the next request starts from saved state, not the full chat.",
|
|
200
199
|
"",
|
|
201
|
-
`<b>Participating scopes:</b> ${named}`,
|
|
202
|
-
...(!scopes.includes("session") ? ["New answers are delivered, not stored: Session is excluded."] : []),
|
|
203
|
-
"",
|
|
204
200
|
"<b>Inspect participating memory</b> — view available stored state even in Off:",
|
|
205
201
|
"",
|
|
206
202
|
...scopes.map(scope => `<code>-</code> <code>${scope}</code>: ${STATE_FLOW_SCOPE_DESCRIPTIONS[scope]}`),
|
|
207
203
|
...(scopes.length > 1
|
|
208
|
-
? [
|
|
209
|
-
: [
|
|
204
|
+
? ["<code>-</code> <code>effective</code>: merged state of the selected scopes in order from the general to the specific."]
|
|
205
|
+
: []),
|
|
210
206
|
].join("\n"),
|
|
211
207
|
parseMode: "html",
|
|
212
208
|
replyMarkup: { inline_keyboard: [
|