@koda-sl/baker-cli 0.121.0-dev.045b11c52 → 0.121.0-dev.3a1b48e85

package/README.md

@@ -2502,6 +2502,31 @@ Rules:
 
 ---
 
+### Marketing Tags (`baker tags`)
+
+Manage the client's marketing/analytics tags (Meta pixel, GA4, Google Ads, GTM, Clarity, Hotjar, PostHog, …) as per-chat **staged** changes. Nothing touches production tags until the chat is published; discarding the chat drops the draft.
+
+`BAKER_CHAT_ID` must be set.
+
+```bash
+baker tags list                                              # effective view: production + staged, with secret status
+baker tags add clarity --set projectId=abcde12345            # client-only tag, no secrets needed
+baker tags add meta --set pixelId=123 --request-secret accessToken
+baker tags update <ref> --set pixelId=999 --clear testEventCode
+baker tags remove <ref>                                      # stage deletion (tag_temp_* ref drops the staged create)
+baker tags draft                                             # review staged ops
+baker tags draft remove <ref>                                # drop one staged op
+baker tags draft clear                                       # drop everything staged
+```
+
+Notes:
+
+- **Secrets never travel through this CLI.** Secret fields (`accessToken`, `apiSecret`, `authorizationToken`, `apiKey`, `conversionToken`, `oauthProviderId`) are rejected in `--set`. Stage with `--request-secret <field>`; the user provides values via the secure tag form in the chat (`request_tag_input`), which writes them straight into the staged draft. Responses only ever name which secret fields are set/pending.
+- Staged creates get a server-generated `tag_temp_*` ref. Use it (or a real tag id) as flow side-effect `tagIds` — the published tag keeps resolving under the temp ref.
+- `update`/`remove` with a `tag_temp_*` ref amend/drop the staged create in place.
+- Single-instance types (`code`, `posthog`, `datafast`) reject a second instance against the chat's effective view.
+- Conflicts at publish (tag deleted in the dashboard, config invalid) skip the op with a recorded reason — they never block the publish.
+
 ### Action Items (`baker actions`)
 
 Manage action items for the current chat. Most write operations stage on the chat's draft and apply atomically when the chat is published. Claim/release run live so other chats can see who's working on what.