anymorph 0.2.4 → 0.2.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/dist/index.js
CHANGED
|
@@ -8178,7 +8178,7 @@ function printScaffoldError(prefix, err) {
|
|
|
8178
8178
|
|
|
8179
8179
|
// src/index.ts
|
|
8180
8180
|
var program2 = new Command();
|
|
8181
|
-
program2.name("anymorph").description("Check your brand's AI visibility \u2014 powered by Anymorph").version("0.2.
|
|
8181
|
+
program2.name("anymorph").description("Check your brand's AI visibility \u2014 powered by Anymorph").version("0.2.5");
|
|
8182
8182
|
program2.command("login").description("Sign in to your Anymorph account").action(loginCommand);
|
|
8183
8183
|
program2.command("check <domain>").description("Check AI visibility for a domain").option("--json", "Output as JSON").action(checkCommand);
|
|
8184
8184
|
program2.command("status").description("Show current auth status").action(statusCommand);
|
|
@@ -37,19 +37,40 @@ Read `references/orchestrator.workflow.md` before final action selection. It con
|
|
|
37
37
|
When running inside a tenant repo, this skill expects a prepared run directory.
|
|
38
38
|
Do not invent a `runId` or create fake input files.
|
|
39
39
|
|
|
40
|
-
|
|
40
|
+
Use the CLI to prepare the same filesystem contract that remote runners use.
|
|
41
41
|
|
|
42
42
|
```bash
|
|
43
|
+
anymorph --version
|
|
44
|
+
anymorph status
|
|
45
|
+
anymorph geo init --repo .
|
|
46
|
+
anymorph geo doctor --repo .
|
|
43
47
|
anymorph geo prepare <workspace-domain-or-id> --repo .
|
|
44
48
|
```
|
|
45
49
|
|
|
46
|
-
|
|
50
|
+
`geo init` installs the bundled skills and local memory scaffold. It does not
|
|
51
|
+
create a strategy run. `geo prepare` fetches the workspace run package from the
|
|
52
|
+
backend and creates the run files.
|
|
53
|
+
|
|
54
|
+
`geo prepare` creates:
|
|
47
55
|
|
|
48
|
-
- `agent/runs/{runId}/context.json`
|
|
49
56
|
- `agent/runs/{runId}/manifest.json`
|
|
57
|
+
- `agent/runs/{runId}/context.json`
|
|
50
58
|
- `agent/runs/{runId}/intents.json`
|
|
59
|
+
- `agent/runs/{runId}/crawl_logs.json`
|
|
60
|
+
- `agent/runs/{runId}/status.json`
|
|
61
|
+
|
|
62
|
+
`intents.json` comes from `signals.intents` in the backend prepare response.
|
|
63
|
+
It is the same source used by the remote GEO strategy runner.
|
|
64
|
+
|
|
65
|
+
Inspect prepared intents when needed:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
anymorph geo intents {runId} --repo .
|
|
69
|
+
```
|
|
51
70
|
|
|
52
|
-
Then run this skill against that `runId`.
|
|
71
|
+
Then run this skill against that `runId`. Use MCP tools only to enrich the
|
|
72
|
+
prepared context or inspect deeper evidence. Do not use MCP calls to replace
|
|
73
|
+
the run package.
|
|
53
74
|
|
|
54
75
|
For local CLI runs, there is no remote runtime artifact submission tool. The
|
|
55
76
|
final artifact contract is the filesystem contract:
|