Set up axonpush for this repository. axonpush adapts per installation: you decide, with me, what this app tracks, and I review it before it goes live. I should not need to copy any keys or ids from the dashboard; the MCP tools give you everything.

API: https://api.axonpush.xyz
Dashboard: https://app.axonpush.xyz
Docs: https://docs.axonpush.xyz/agent-operations
Use our own deployment URLs if these differ.

1. Connect the axonpush MCP server at https://api.axonpush.xyz/mcp if it is not connected yet (for Claude Code: `claude mcp add --transport http axonpush https://api.axonpush.xyz/mcp`). Sign-in happens in the browser; there is no token to paste. Call the workspaces_describe tool to learn the spec format, the roles, the draft ops and the setup steps. Do not guess tool names or fields; use what describe returns.

2. Use the workspace I gave you. If I did not give you one, list the workspaces and use one that is not active yet, or create one for our app with a blank spec ({"name": "..."}).

3. Read this codebase. Find the things worth tracking (for example agents, tickets, orders, runs), the events that change them, and the attributes each one needs. Prefer opaque ids and bounded labels. Leave out prompts, responses, message bodies, documents, secrets and raw URLs.

4. Propose a data dictionary, entities and events to me in plain language before writing anything. For every attribute you want to mark personal (names, emails, companies), say why it is needed. Only declare personal attributes I agree to.

5. Read the shared draft with workspaces_draft and change it with workspaces_applyDraftOps, sending the draft version each time. Make small, typed edits; never rewrite the whole spec. Check workspaces_draftChanges and fix any issues it reports.

6. Ask me to review and activate the draft in the dashboard (https://app.axonpush.xyz). If I approve it here in the chat, call workspaces_activateDraft yourself; otherwise wait for me.

7. Call workspaces_connect for the workspace. It mints a key that can only publish, bound to this app and one environment, and returns an env map. Write that env into the app's git-ignored env file (.env.local, or the project's existing secret convention) and check the file is ignored. Never commit, print or paste the key. If connect says a key already exists and this repository does not have it, call it again with rotate: true.

8. Add the axonpush SDK to the app and record events with the SDK's observe call, at the points you identified. Each event carries schema_version, source_event_id (stable across retries), event, occurred_at, an optional environment, refs (entity type to opaque id), optional trace_id and span_id, and attributes limited to the keys you declared. Use the SDK's identify call to attach the declared profile attributes (such as a display name) to an entity. Read the configuration from the env written in step 7. Follow the docs at https://docs.axonpush.xyz over anything in this prompt. Keep telemetry out of business transactions so a failure here never changes app behaviour.

9. Send one test event from the app and confirm it appears in workspaces_catalog.

Finish with the diff, what each event means, which attributes are personal, where you wrote the env, and anything you could not verify.
