@llblab/pi-state-flow 0.27.4 → 0.27.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/CHANGELOG.md +5 -0
- package/dist/lib/telegram.js +0 -2
- package/dist/package.json +1 -1
- package/docs/usage.md +2 -0
- package/lib/telegram.ts +0 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,11 @@
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 0.27.5: Compact Telegram Help and Migration Guidance
|
|
8
|
+
|
|
9
|
+
- `Telegram help spacing`: Removes the empty lines between the Mode and Inspect participating memory headings and their lists. The canonical source now preserves the compact layout in rebuilt packages; controls, scope selection and inspection behavior are unchanged.
|
|
10
|
+
- `Migration guidance`: Explains why legacy `contract`/`working` files can remain after an update, when owned acceptance converts them to `strategy`/`tactics`, and why untouched owners/sessions are not upgraded by inspection. Documents quiescing old writers and accepting current memory through upgraded Active/Start; migration behavior and storage formats are unchanged.
|
|
11
|
+
|
|
7
12
|
## 0.27.4: TypeScript Declaration Hotfix
|
|
8
13
|
|
|
9
14
|
- `Package type discovery`: Adds the top-level `types` entry pointing to `dist/index.d.ts` so TypeScript consumers and tools that do not read conditional exports can discover the built declarations. Existing conditional type exports remain unchanged. The tracked distribution manifest is rebuilt with matching metadata.
|
package/dist/lib/telegram.js
CHANGED
|
@@ -70,13 +70,11 @@ export function buildStateFlowSectionView(snapshot, callbackData) {
|
|
|
70
70
|
] : []),
|
|
71
71
|
"",
|
|
72
72
|
"<b>Mode</b> — choose a workflow (switching modes never erases stored memory):",
|
|
73
|
-
"",
|
|
74
73
|
"<code>-</code> <code>off</code> (default): regular chat without State Flow memory tools or context.",
|
|
75
74
|
`<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.`,
|
|
76
75
|
"<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.",
|
|
77
76
|
"",
|
|
78
77
|
"<b>Inspect participating memory</b> — view available stored state even in Off:",
|
|
79
|
-
"",
|
|
80
78
|
...scopes.map(scope => `<code>-</code> <code>${scope}</code>: ${STATE_FLOW_SCOPE_DESCRIPTIONS[scope]}`),
|
|
81
79
|
...(scopes.length > 1
|
|
82
80
|
? ["<code>-</code> <code>effective</code>: merged state of the selected scopes in order from the general to the specific."]
|
package/dist/package.json
CHANGED
package/docs/usage.md
CHANGED
|
@@ -351,6 +351,8 @@ Commit or push failure is diagnostic-only; repeated push failures warn once per
|
|
|
351
351
|
|
|
352
352
|
**Supported formats.** State Flow accepts only canonical checkpoint/tail files, temporal metadata and the separate session config/runtime contract.
|
|
353
353
|
|
|
354
|
+
**Why files can still contain `contract`/`working` after an update.** Installing or reloading the package is not a whole-store migration. Legacy reads translate those roots to `strategy`/`tactics` in memory; disk conversion occurs only when an owned semantic transaction accepts the participating cohort. Off, inspection and runtime-only mode persistence do not perform it. Unselected owners and untouched historical sessions remain in their supported legacy format until their own acceptance; accepting one session never scans or upgrades every project/session. To convert an existing cohort, first quiesce old writers, then explicitly accept its current memory with Active/Start using the upgraded code. Keep the verified migration backup; do not rename JSON keys manually or reopen old writers against converted files.
|
|
355
|
+
|
|
354
356
|
- Scope metadata versions 1/2 remain readable through explicit `contract → strategy`, `working → tactics` translation before field filtering. Current/historical tools expose only the target dialect; retired root writes reject rather than becoming aliases. Legacy missing revisions credit only retained tail records.
|
|
355
357
|
- Core-only writes use scope metadata v3; retained external-module descriptors select v4. Both use Strategy/Tactics. On owned semantic acceptance, supported legacy/descriptor upgrades use the same backup, lock/CAS and rollback checks without advancing revisions/causal identities for representation alone. Ordinary inspection and runtime-only mode persistence do not convert files. Upgrade/quiesce all writers before enabling the new code: already-deployed low-level readers cannot be universally fenced by a format number.
|
|
356
358
|
- Unsupported checkpoint envelopes, combined session metadata, `state.json`, hashed layouts and semantic Pi checkpoint envelopes fail as unsupported, without rewriting existing bytes.
|
package/lib/telegram.ts
CHANGED
|
@@ -192,13 +192,11 @@ export function buildStateFlowSectionView(
|
|
|
192
192
|
] : []),
|
|
193
193
|
"",
|
|
194
194
|
"<b>Mode</b> — choose a workflow (switching modes never erases stored memory):",
|
|
195
|
-
"",
|
|
196
195
|
"<code>-</code> <code>off</code> (default): regular chat without State Flow memory tools or context.",
|
|
197
196
|
`<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.`,
|
|
198
197
|
"<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.",
|
|
199
198
|
"",
|
|
200
199
|
"<b>Inspect participating memory</b> — view available stored state even in Off:",
|
|
201
|
-
"",
|
|
202
200
|
...scopes.map(scope => `<code>-</code> <code>${scope}</code>: ${STATE_FLOW_SCOPE_DESCRIPTIONS[scope]}`),
|
|
203
201
|
...(scopes.length > 1
|
|
204
202
|
? ["<code>-</code> <code>effective</code>: merged state of the selected scopes in order from the general to the specific."]
|