create-orcha 0.1.4 → 0.1.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/package.json +1 -1
- package/template/README.md +2 -1
- package/template/orcha/AGENTS.md +3 -3
package/package.json
CHANGED
package/template/README.md
CHANGED
|
@@ -47,7 +47,8 @@ npm run orcha:dev # validate and watch the Orcha registry
|
|
|
47
47
|
npm run orcha:test # run registered agent tests
|
|
48
48
|
```
|
|
49
49
|
|
|
50
|
-
The default Node configuration stores sessions in
|
|
50
|
+
The default Node configuration stores sessions in
|
|
51
|
+
`.orcha/sessions/<agentName>/ses_<timestamp>_<uuid>.jsonl`. The
|
|
51
52
|
playground accesses parent sessions through `agent.list()`, `agent.get()`, and
|
|
52
53
|
`agent.events()`, and child sessions through `agent.subagentHistory()`, so
|
|
53
54
|
changing the storage adapter does not require UI or server changes.
|
package/template/orcha/AGENTS.md
CHANGED
|
@@ -20,7 +20,7 @@ files under `.orcha/`.
|
|
|
20
20
|
|
|
21
21
|
`run` and `test` use real providers and require credentials. `dev` and
|
|
22
22
|
`build` are offline. Session logs are JSONL files under
|
|
23
|
-
`.orcha/sessions/<
|
|
23
|
+
`.orcha/sessions/<agentName>/ses_<timestamp>_<uuid>.jsonl`.
|
|
24
24
|
|
|
25
25
|
## Registry
|
|
26
26
|
|
|
@@ -512,7 +512,7 @@ real actions. The mocked action set must exactly match the compiled action set.
|
|
|
512
512
|
}
|
|
513
513
|
```
|
|
514
514
|
|
|
515
|
-
Test sessions use the `ses_test_
|
|
515
|
+
Test sessions use the `ses_test_<timestamp>_<uuid>` format and end with a `test.completed`
|
|
516
516
|
event. Prefer semantic output assertions; verify exact identifiers and values
|
|
517
517
|
through action-argument assertions.
|
|
518
518
|
|
|
@@ -964,7 +964,7 @@ offline production compilation. Neither command invokes a provider.
|
|
|
964
964
|
|
|
965
965
|
### Run lifecycle
|
|
966
966
|
|
|
967
|
-
1. `run()` creates a `ses_<uuid>`, acquires the per-session execution lock,
|
|
967
|
+
1. `run()` creates a `ses_<timestamp>_<uuid>`, acquires the per-session execution lock,
|
|
968
968
|
appends `session.created`, then starts run 1.
|
|
969
969
|
2. `resume()` reads and validates the existing session. Message continuation
|
|
970
970
|
starts a new run; submitted client results continue the paused run.
|