@llblab/pi-state-flow 0.9.0 → 0.9.1
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/BACKLOG.md +4 -1
- package/CHANGELOG.md +5 -0
- package/README.md +1 -1
- package/docs/architecture.md +1 -1
- package/lib/telegram.ts +5 -6
- package/package.json +1 -1
package/BACKLOG.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# BACKLOG
|
|
2
2
|
|
|
3
|
-
Completed release work belongs in [CHANGELOG.md](CHANGELOG.md). No implementation item remains open for 0.
|
|
3
|
+
Completed release work belongs in [CHANGELOG.md](CHANGELOG.md). No implementation item remains open for 0.9.0.
|
|
4
4
|
|
|
5
5
|
## Candidate evolution
|
|
6
6
|
|
|
@@ -8,6 +8,9 @@ Completed release work belongs in [CHANGELOG.md](CHANGELOG.md). No implementatio
|
|
|
8
8
|
- Boundary: project the existing durable global materialization only. No writes, transitions, patches, barriers, session/CWD initialization, or temporal-history changes. Model tools and the full protocol remain opt-in behind explicit start, and the bootstrap adds no second semantic mode.
|
|
9
9
|
- Open questions: whether deferred Markdown freshness discovery must run ahead of the first inference, token cost of a stable global prefix, behavior under untrusted project contexts, and naming distinct from the existing bootstrap-run concept.
|
|
10
10
|
- Status: candidate, not scheduled. Do not start without a dedicated release contract.
|
|
11
|
+
- [ ] **Telegram submenu state analyzer:** Extend the State Flow Telegram section with a read-only analyzer view over the same diagnostics `/state-flow-status` already reports (branch mode, temporal head and hot depth, scope keys, retained tails, artifact freshness, publication). The operator deliberately deferred this beyond the 0.9.0 control surface.
|
|
12
|
+
- Boundary: presentation only. Reuse existing status diagnostics; no new semantic mode, and never mutate state from the analyzer view.
|
|
13
|
+
- Status: candidate, not scheduled. Do not start without a dedicated release contract.
|
|
11
14
|
|
|
12
15
|
## Deferred host integration
|
|
13
16
|
|
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
> Each release keeps at most 8 outcome records of at most 512 characters.
|
|
4
4
|
|
|
5
|
+
## 0.9.1: Status text mirrors the terminal line
|
|
6
|
+
|
|
7
|
+
- `Interop`: The `pi-telegram` surfaces now copy the compact terminal status instead of decorating it. The Status screen shows the terminal value itself (`State Flow: #N`) and hides entirely while State Flow is off; the main-menu button shows `🌀 State Flow: #N` or a plain `⚫️ State Flow` without on/off, starting, bootstrap, or separator text.
|
|
8
|
+
- `Testing`: The shared test harness removes its temporary fixture repositories at process exit; runaway fixtures previously exhausted the `/tmp` inode table and made later runs fail with ENOSPC.
|
|
9
|
+
|
|
5
10
|
## 0.9.0: Telegram status surface
|
|
6
11
|
|
|
7
12
|
- `Interop`: Added an optional fail-open `pi-telegram` presentation adapter. With the transport installed, the status screen shows `State Flow: on · step #N` while enabled, and the inline main menu places a `🌀 State Flow: #N` or `⚫️ State Flow: off` section button directly before Settings.
|
package/README.md
CHANGED
|
@@ -66,7 +66,7 @@ Stopping changes the current session/branch configuration, preserves semantic ch
|
|
|
66
66
|
|
|
67
67
|
The compact status is an accent `state-flow` and dim `#<step>`. Detailed status distinguishes runtime config/meta from semantic materialization, reports scope keys, the selected temporal head and runtime revision, available hot offsets, per-scope retained patch tails, artifact counts, stale Markdown reasons, and pending publication. Retained tails may include inherited pre-origin records, so their counts are not active history depth. It labels global/CWD/session/effective state without dumping source bodies. Failed inspection means unavailable evidence, never a falsely clean count.
|
|
68
68
|
|
|
69
|
-
When the optional `pi-telegram` extension is installed, State Flow mirrors the same identity there: the Status screen shows `State Flow:
|
|
69
|
+
When the optional `pi-telegram` extension is installed, State Flow mirrors the same identity there: the Status screen shows `State Flow: #N` while enabled and hides the row while off, and the inline main menu places a `🌀 State Flow: #N` or `⚫️ State Flow` section button directly before Settings. The button opens a compact control submenu for the current session branch: `Start` or `Stop`, `Refresh`, and `Cancel start` while a start deferred behind an active run is pending. Starting while a run is active waits for that run to settle; stopping applies immediately. Registration fails open when the transport is absent, retries when the section registry becomes ready, and disposes on session shutdown; the `/state-flow-*` commands remain the authority and nothing changes for hosts without `pi-telegram`.
|
|
70
70
|
|
|
71
71
|
## State, scope, and time
|
|
72
72
|
|
package/docs/architecture.md
CHANGED
|
@@ -199,7 +199,7 @@ Unknown keys fail loading. State Flow memory ownership and global availability a
|
|
|
199
199
|
|
|
200
200
|
`/state-flow-status` reports branch mode, runtime revision, temporal head/history depth, scope keys, patch tails, artifact freshness, memory-bearing scopes, external-promotion summaries, remote policy/queue state, and pending publication. Unavailable materialization is reported as unavailable, never fabricated as empty. Artifact source bodies are not read for status.
|
|
201
201
|
|
|
202
|
-
With `pi-telegram` installed, the optional `telegram` adapter mirrors the same identity in Telegram: the Status screen row shows `State Flow:
|
|
202
|
+
With `pi-telegram` installed, the optional `telegram` adapter mirrors the same identity in Telegram: the Status screen row shows `State Flow: #N` while enabled and hides while off, and the main-menu section button before Settings opens the branch start/stop submenu. Registration is fail-open and retried on session start, disposal happens on session shutdown, the adapter reads the same snapshot as the compact terminal status, and its start/stop actions call the same functions as the commands.
|
|
203
203
|
|
|
204
204
|
Opt-in `logging` appends local JSONL diagnostics for rejected `patch_state` calls and preserved drafts plus fallback turns while turn resolution is pending. A rejected call retains its exact attempted arguments, the precise error, and, when available, tool identity, call id, resolution attempt, and terminal-eligibility state; accepted patches are never logged. Records preserve useful exact text blocks and reduce other blocks to structural identity without duplicating reasoning. They are never semantic state, scope `meta.json`, Pi checkpoints, or repository input. Write failure changes no resolution, enablement, or accepted state and reports at most one bounded local warning.
|
|
205
205
|
|
package/lib/telegram.ts
CHANGED
|
@@ -90,16 +90,15 @@ export interface StateFlowTelegramAdapter {
|
|
|
90
90
|
dispose(): void;
|
|
91
91
|
}
|
|
92
92
|
|
|
93
|
-
/** The Status screen mirrors the terminal status
|
|
93
|
+
/** The Status screen mirrors the terminal status line: key plus step value, hidden while State Flow is off. */
|
|
94
94
|
export function formatStateFlowStatusLine(snapshot: StateFlowTelegramSnapshot): StateFlowTelegramStatusLine | undefined {
|
|
95
|
-
if (!snapshot.enabled) return
|
|
96
|
-
return { label: "State Flow", value:
|
|
95
|
+
if (!snapshot.enabled) return undefined;
|
|
96
|
+
return { label: "State Flow", value: `#${snapshot.step}` };
|
|
97
97
|
}
|
|
98
98
|
|
|
99
|
-
/** Main-menu section label doubles as the live status text. */
|
|
99
|
+
/** Main-menu section label doubles as the live status value; the disabled row carries no status text. */
|
|
100
100
|
export function formatStateFlowSectionLabel(snapshot: StateFlowTelegramSnapshot): string {
|
|
101
|
-
|
|
102
|
-
return snapshot.bootstrap ? "🌀 State Flow: bootstrap" : `🌀 State Flow: #${snapshot.step}`;
|
|
101
|
+
return snapshot.enabled ? `🌀 State Flow: #${snapshot.step}` : "⚫️ State Flow";
|
|
103
102
|
}
|
|
104
103
|
|
|
105
104
|
export function buildStateFlowSectionView(
|