@xenia-martech/mcp 1.0.0-rc.2 → 1.0.0-rc.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/README.md +8 -3
- package/dist/bin.js +55 -53
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -30,8 +30,13 @@ After you choose how to get the SDK token, the assistant does the rest without s
|
|
|
30
30
|
timeout and circuit breaker, consent from your cookie banner, and form conversions.
|
|
31
31
|
- **Each journey** you name, in your real components: server-side with `{ fallback: null }` so an
|
|
32
32
|
outage renders your default content; `track()` for event triggers.
|
|
33
|
-
- **Checks** — a type-check/build and `xenia_verify`, plus warnings about the journey itself (
|
|
34
|
-
A/B split that would show the same visitor different variants) with the
|
|
33
|
+
- **Checks** — a type-check/build and `xenia_verify`, plus warnings about the journey itself (an
|
|
34
|
+
A/B split that would show the same visitor different variants, a journey that's stopped) with the
|
|
35
|
+
dashboard fix.
|
|
36
|
+
|
|
37
|
+
One SDK token covers everything, webhook triggers that require auth included, and a minted token
|
|
38
|
+
never expires unless you ask for an expiry (it can always be revoked). Connected to a non-default
|
|
39
|
+
engine with `--base-url`? The mint tool also writes `XENIA_URL`, so your app calls that same engine.
|
|
35
40
|
|
|
36
41
|
It stops to ask only for the token choice, a production write, or — if your site has no consent
|
|
37
42
|
banner — whether analytics needs consent.
|
|
@@ -87,7 +92,7 @@ can be disconnected there at any time.
|
|
|
87
92
|
| `xenia_list_content_keys` | Every personalization key, and which journeys resolve it |
|
|
88
93
|
| `xenia_detect_stack` | Framework, SDK entry point, and which token type this project needs |
|
|
89
94
|
| `xenia_setup_project` | The one-time wiring plan for this stack: files to create or merge, consent, forms, verification |
|
|
90
|
-
| `xenia_mint_sdk_token` | Mint a token and write it to your env file |
|
|
95
|
+
| `xenia_mint_sdk_token` | Mint a token (never expires unless `expiresInDays` is given) and write it, plus the engine URL when it isn't the default, to your env file |
|
|
91
96
|
| `xenia_verify` | Read journeys, resolve a content key, optionally fire a test event |
|
|
92
97
|
| `xenia_logout` | Revoke the session and forget the local credential |
|
|
93
98
|
|