anymorph 0.2.3 → 0.2.4
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.4");
|
|
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);
|
|
@@ -28,10 +28,46 @@ Read `references/orchestrator.workflow.md` before final action selection. It con
|
|
|
28
28
|
3. Invoke or apply the three channel diagnosis skills.
|
|
29
29
|
4. Read channel outputs and reject weak, duplicate, or conflicting proposals.
|
|
30
30
|
5. Prefer no action over low-evidence action.
|
|
31
|
-
6.
|
|
31
|
+
6. In local CLI mode, write `agent/runs/{runId}/actions.json` directly.
|
|
32
32
|
7. Write rationale and status files only under the current run path.
|
|
33
33
|
8. Update durable tenant memory only when the run changes stable strategy or repeated learnings.
|
|
34
34
|
|
|
35
|
+
## Local CLI Mode
|
|
36
|
+
|
|
37
|
+
When running inside a tenant repo, this skill expects a prepared run directory.
|
|
38
|
+
Do not invent a `runId` or create fake input files.
|
|
39
|
+
|
|
40
|
+
Before using this skill locally, run:
|
|
41
|
+
|
|
42
|
+
```bash
|
|
43
|
+
anymorph geo prepare <workspace-domain-or-id> --repo .
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
That command creates:
|
|
47
|
+
|
|
48
|
+
- `agent/runs/{runId}/context.json`
|
|
49
|
+
- `agent/runs/{runId}/manifest.json`
|
|
50
|
+
- `agent/runs/{runId}/intents.json`
|
|
51
|
+
|
|
52
|
+
Then run this skill against that `runId`.
|
|
53
|
+
|
|
54
|
+
For local CLI runs, there is no remote runtime artifact submission tool. The
|
|
55
|
+
final artifact contract is the filesystem contract:
|
|
56
|
+
|
|
57
|
+
- write `agent/runs/{runId}/actions.json`
|
|
58
|
+
- write `agent/runs/{runId}/rationale.md`
|
|
59
|
+
- update `agent/runs/{runId}/status.json`
|
|
60
|
+
|
|
61
|
+
After writing artifacts, validate them with:
|
|
62
|
+
|
|
63
|
+
```bash
|
|
64
|
+
anymorph geo validate {runId} --repo .
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Only use runtime artifact tools when the host environment explicitly provides
|
|
68
|
+
them. In ordinary local tenant repo work, the filesystem artifacts above are the
|
|
69
|
+
source of truth.
|
|
70
|
+
|
|
35
71
|
## Final Decision Rules
|
|
36
72
|
|
|
37
73
|
- Emit at most 20 actions.
|