anymorph 0.6.0 → 0.9.0

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.
Files changed (3) hide show
  1. package/README.md +6 -16
  2. package/dist/index.js +32362 -2860
  3. package/package.json +2 -1
package/README.md CHANGED
@@ -30,7 +30,9 @@ anymorph workspaces
30
30
  anymorph init
31
31
  anymorph prepare ws_abc123
32
32
  anymorph validate 20260517T074200Z
33
- anymorph submit 20260517T074200Z
33
+ git add agent/runs content
34
+ git commit -m "chore(geo): publish run 20260517T074200Z"
35
+ git push
34
36
  ```
35
37
 
36
38
  ## Commands
@@ -187,21 +189,9 @@ anymorph validate 20260517T074200Z
187
189
  ```
188
190
 
189
191
  Validation does not update the backend. Backend sync happens from the tenant
190
- submission command after local artifacts pass validation.
191
-
192
- ### `anymorph submit <runId>`
193
-
194
- Submit validated local GEO run artifacts to Anymorph.
195
-
196
- ```bash
197
- anymorph submit 20260517T074200Z
198
- anymorph submit 20260517T074200Z --json
199
- ```
200
-
201
- The CLI reads `agent/runs/{runId}/manifest.json`, submits the manifest-declared
202
- artifact paths, and includes the current git commit SHA when available. Use
203
- `--workspace <workspaceId>` only when the workspace cannot be inferred from the
204
- run package.
192
+ repo GitHub webhook after `agent/runs/{runId}/actions.json` is pushed to
193
+ `main`. Any generated `content/*.mdx` files are materialized as CMS pages from
194
+ the same webhook path.
205
195
 
206
196
  ## How It Works
207
197