create-orcha 0.4.1 → 0.4.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/package.json +1 -1
- package/template/AGENTS.md +8 -2
- package/template/orcha/AGENTS.md +22 -0
- package/template/package.json +6 -0
package/package.json
CHANGED
package/template/AGENTS.md
CHANGED
|
@@ -9,8 +9,14 @@ frontend or server code is not required.
|
|
|
9
9
|
- `.orcha/sessions/` is the default Node JSONL storage directory and must not
|
|
10
10
|
be committed.
|
|
11
11
|
- `npm run dev` starts `orcha playground`, which watches `orcha/**`.
|
|
12
|
-
- `npm run build` creates
|
|
13
|
-
the playground React
|
|
12
|
+
- `npm run build` creates `.orcha/dist/bundle.js` and
|
|
13
|
+
`.orcha/dist/manifest.json`; it does not include the playground React
|
|
14
|
+
application.
|
|
15
|
+
|
|
16
|
+
When another tool packages an unbundled production application, explicitly
|
|
17
|
+
include `.orcha/dist/**`. A successful `orcha build` does not guarantee that a
|
|
18
|
+
later packager copied generated files. Inspect the final ZIP or container and
|
|
19
|
+
confirm that `.orcha/dist/manifest.json` is present.
|
|
14
20
|
|
|
15
21
|
Use the complete Orcha `AGENTS.md` generated by `orcha init` as the source of
|
|
16
22
|
truth for agent configuration, actions, skills, tests, evaluations, and JSONL
|
package/template/orcha/AGENTS.md
CHANGED
|
@@ -28,6 +28,28 @@ credentials. `dev` and `build` are offline. Sessions use JSONL by default
|
|
|
28
28
|
under `.orcha/sessions/<agentName>/`; opt-in SQLite stores all agents in
|
|
29
29
|
`.orcha/sessions/orcha-sqlite.db`.
|
|
30
30
|
|
|
31
|
+
## Production deployment
|
|
32
|
+
|
|
33
|
+
`orcha build` writes `.orcha/dist/bundle.js` for bundler integrations and
|
|
34
|
+
`.orcha/dist/manifest.json` for unbundled production runtimes. If deployment
|
|
35
|
+
uses plain `tsc`, `serverless-plugin-typescript`, or another packager that
|
|
36
|
+
does not use `orchajs/esbuild`, explicitly include `.orcha/dist/**` in the
|
|
37
|
+
deployment artifact. AWS Lambda loads the manifest automatically; other
|
|
38
|
+
unbundled environments require `NODE_ENV=production` or
|
|
39
|
+
`ORCHA_USE_BUILD=1`.
|
|
40
|
+
|
|
41
|
+
For Serverless Framework manual builds:
|
|
42
|
+
|
|
43
|
+
```yaml
|
|
44
|
+
package:
|
|
45
|
+
patterns:
|
|
46
|
+
- ".orcha/dist/**"
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Do not assume that a successful `orcha build` means the generated files were
|
|
50
|
+
copied by a later packaging tool. Inspect the final ZIP or container image and
|
|
51
|
+
confirm that `.orcha/dist/manifest.json` is present.
|
|
52
|
+
|
|
31
53
|
## Registry
|
|
32
54
|
|
|
33
55
|
`orcha/index.ts` initializes providers and explicitly registers agents:
|
package/template/package.json
CHANGED