diff --git a/context/agents/error-tracking/credentials.md b/context/agents/error-tracking/credentials.md index 0a1e8fb6..d748955b 100644 --- a/context/agents/error-tracking/credentials.md +++ b/context/agents/error-tracking/credentials.md @@ -24,7 +24,7 @@ mint one — never call the PostHog API or any tool to create it. Get it and write it in this one task (the key never survives across tasks): 1. Ask with `wizard_ask`, exactly: - `{ id: "api-key", prompt: "Paste your PostHog personal API key below.\n\nDon't have one yet? Create one here:\n\n\nWhen creating the key, choose the 'Source map upload' preset, then come back and paste it here.", kind: "text", sensitive: true }` + `{ id: "api-key", prompt: "Uploading source maps needs a PostHog personal API key. Source maps let PostHog show your original code in error stack traces, not minified code.\n\nCreate a key with the right permissions here:\n/source-maps-key\n\nThen paste it below.", kind: "text", sensitive: true }` You receive `{ secretRef: "secret:..." }` — a vaulted reference, never the raw value. If `wizard_ask` is unavailable (non-interactive run), report this task with status `not needed` and say in your handoff that the user must create @@ -48,8 +48,7 @@ write it in this one task (the key never survives across tasks): same file beside you, so read it right before you change it and add your lines with `edit`; never `write` over it once it exists. -Replace ``, ``, and `` from your project -context. Do not touch the build config — the `configure` task owns that. +Replace `` and `` from your project context. Do not touch the build config — the `configure` task owns that. ## The names are a contract diff --git a/context/agents/error-tracking/report.md b/context/agents/error-tracking/report.md index 660151dd..41e0facf 100644 --- a/context/agents/error-tracking/report.md +++ b/context/agents/error-tracking/report.md @@ -38,11 +38,11 @@ Then, when the run wired source-map upload or release linking, or any follow-up has steps, add a **"What you still need to do"** section — numbered, copy-pasteable: -1. Create a personal API key with the 'Source map upload' preset at - `/settings/user-api-keys` (skip when the credentials handoff says - the key is already written and no release linking was wired). The preset - carries the error tracking write scope that both uploads and release - linking need. +1. Create a personal API key at `/source-maps-key` (skip when the + credentials handoff says the key is already written and no release linking + was wired). The link opens the key form with the 'Source map upload' preset + selected; the preset carries the error tracking write scope that both + uploads and release linking need. 2. Add it as the CI secret the wire-ci or link-releases step referenced, named exactly as in the pipeline config. When link-releases also reads a project ID variable (such as `POSTHOG_PROJECT_ID`), add it with the value