@llblab/pi-state-flow 0.2.1 → 0.2.2
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 +4 -0
- package/README.md +4 -20
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.2: README structure hotfix
|
|
4
|
+
|
|
5
|
+
- Separate installation from usage, remove the redundant quick-start section, and move architecture details after the user-facing documentation.
|
|
6
|
+
|
|
3
7
|
## 0.2.1: README banner hotfix
|
|
4
8
|
|
|
5
9
|
- Add the project banner to the README.
|
package/README.md
CHANGED
|
@@ -35,26 +35,6 @@ pi install git:github.com/llblab/pi-state-flow
|
|
|
35
35
|
|
|
36
36
|
Pi packages execute with full user permissions; review the source before installing, as with any extension.
|
|
37
37
|
|
|
38
|
-
## Quick start
|
|
39
|
-
|
|
40
|
-
Start Pi, then start an episode and send your task:
|
|
41
|
-
|
|
42
|
-
```text
|
|
43
|
-
/state-flow-start
|
|
44
|
-
```
|
|
45
|
-
|
|
46
|
-
State Flow is opt-in: installation alone does not alter model context. Confirm the active episode with `/state-flow-status`, and use `/state-flow-stop` to disable it and erase its materialized episode state.
|
|
47
|
-
|
|
48
|
-
For a one-off trial without installing the package:
|
|
49
|
-
|
|
50
|
-
```bash
|
|
51
|
-
pi -e npm:@llblab/pi-state-flow
|
|
52
|
-
```
|
|
53
|
-
|
|
54
|
-
## Architecture
|
|
55
|
-
|
|
56
|
-
`index.ts` is only the package composition and public-export boundary. Independent runtime domains live under `lib/`: `json` owns lossless JSON and patches, `state` owns the materialized state shape, `episode` owns explicit start/stop and user-run boundaries, `snapshot` owns persistence migration, `session` owns active-branch snapshot discovery and bootstrap detection, `recovery` falls back to the newest valid active-branch checkpoint, `status` owns deterministic operator-facing status rendering, `context` owns trajectory projection, private-feedback filtering, and synthetic runtime-context construction, `skills` owns Skill acquisition rules and mutable lifecycle correlation, `terminal` owns the handoff protocol, `validation` owns bounded retry decisions, `transition` owns atomic staging and compare-and-swap commits, and `extension` coordinates these domains with Pi. Every domain has a same-named test under `tests/`; lifecycle scenarios are colocated with the domain whose contract they exercise, `tests/extension.test.ts` remains focused on composition, shared setup lives in `tests/harness.ts`, and cross-domain constraints live in `tests/invariants.test.ts`.
|
|
57
|
-
|
|
58
38
|
## Usage
|
|
59
39
|
|
|
60
40
|
```text
|
|
@@ -182,6 +162,10 @@ The normative protocol remains in the system prompt throughout a tool/retry chai
|
|
|
182
162
|
- This mode remains a poor fit for auditing or outputs that require complete historical trajectories across user requests.
|
|
183
163
|
- Token, cache, latency, and success-rate advantages still require controlled Pi benchmarks.
|
|
184
164
|
|
|
165
|
+
## Architecture
|
|
166
|
+
|
|
167
|
+
`index.ts` is only the package composition and public-export boundary. Independent runtime domains live under `lib/`: `json` owns lossless JSON and patches, `state` owns the materialized state shape, `episode` owns explicit start/stop and user-run boundaries, `snapshot` owns persistence migration, `session` owns active-branch snapshot discovery and bootstrap detection, `recovery` falls back to the newest valid active-branch checkpoint, `status` owns deterministic operator-facing status rendering, `context` owns trajectory projection, private-feedback filtering, and synthetic runtime-context construction, `skills` owns Skill acquisition rules and mutable lifecycle correlation, `terminal` owns the handoff protocol, `validation` owns bounded retry decisions, `transition` owns atomic staging and compare-and-swap commits, and `extension` coordinates these domains with Pi. Every domain has a same-named test under `tests/`; lifecycle scenarios are colocated with the domain whose contract they exercise, `tests/extension.test.ts` remains focused on composition, shared setup lives in `tests/harness.ts`, and cross-domain constraints live in `tests/invariants.test.ts`.
|
|
168
|
+
|
|
185
169
|
## Validation
|
|
186
170
|
|
|
187
171
|
```bash
|