vybekiit 0.7.3 → 0.7.7

package/dist/global-skills/instrument-product-analytics/references/next-js.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Next.js - Docs
+
+Copy page
+
 # Next.js - Docs
 
 PostHog makes it easy to get data about traffic and usage of your [Next.js](https://nextjs.org/) app. Integrating PostHog into your site enables analytics about user behavior, custom events capture, session recordings, feature flags, and more.
@@ -57,6 +63,18 @@ pnpm add posthog-js
 bun add posthog-js
 ```
 
+> **If your site sets a Content-Security-Policy**, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog's CDN, and sends events to the ingestion host. PostHog serves from subdomains of `posthog.com` that change over time, so allow the wildcard:
+>
+> PostHog AI
+>
+> ```
+> script-src 'self' https://*.posthog.com;
+> connect-src 'self' https://*.posthog.com;
+> worker-src 'self' blob: data:;
+> ```
+>
+> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+
 Add your environment variables to your `.env.local` file and to your hosting provider (e.g. Vercel, Netlify, AWS). You can find your project token in your [project settings](https://app.posthog.com/project/settings).
 
 .env.local
@@ -113,8 +131,34 @@ See the [bootstrapping guide](/docs/feature-flags/bootstrapping.md) for more inf
 
 > **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](/docs/session-replay.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too.
 >
+> Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like `"anonymous"` or `"user"`, which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that's automatically assigned.
+>
+> Call `posthog.reset()` on logout, so the next person to use the browser doesn't inherit the last one's identity.
+>
 > See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
 
+### Linking client and server events
+
+Next.js apps usually capture on both sides. To keep them on the same person, use the same distinct ID in both, and let the browser tell your server which one that is.
+
+If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
+
+JavaScript
+
+PostHog AI
+
+```javascript
+posthog.init('<ph_project_token>', {
+  api_host: 'https://us.i.posthog.com',
+  // Optional: send PostHog session/user context to your backend
+  tracing_headers: ['api.example.com'],
+})
+```
+
+This works in local development too, but match on the hostname alone: use `'localhost'`, not `'localhost:3000'`. Ports are never part of a hostname, so a value with one in it never matches anything. `localhost` and `127.0.0.1` are also different hostnames — use whichever your app actually calls.
+
+Tracing headers help you attribute events across front and backend consistently. When this isn't available, use your server-side stable IDs to deduce the matching `distinctId`, and pass it in when capturing the event.
+
 Set up a reverse proxy (recommended)
 
 We recommend [setting up a reverse proxy](/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers.
@@ -183,7 +227,7 @@ See the [React SDK docs](/docs/libraries/react.md) for examples of how to use:
 -   [`posthog-js` functions like custom event capture, user identification, and more.](/docs/libraries/react.md#using-posthog-js-functions)
 -   [Feature flags including variants and payloads.](/docs/libraries/react.md#feature-flags)
 
-You can also read [the full `posthog-js` documentation](/docs/libraries/js/features.md) for all the usable functions.
+You can also read [the full `posthog-js` documentation](/docs/libraries/js/usage.md) for all the usable functions.
 
 ## Server-side analytics
 
@@ -288,6 +332,7 @@ PostHog AI
 // pages/posts/[id].js
 import { useContext, useEffect, useState } from 'react'
 import { getServerSession } from "next-auth/next"
+import { authOptions } from '@/lib/auth'
 import { PostHog } from 'posthog-node'
 export default function Post({ post, flags }) {
   const [ctaState, setCtaState] = useState()
@@ -309,7 +354,8 @@ export default function Post({ post, flags }) {
   )
 }
 export async function getServerSideProps(ctx) {
-  const session = await getServerSession(ctx.req, ctx.res)
+  // Pass authOptions, or your session callbacks don't run.
+  const session = await getServerSession(ctx.req, ctx.res, authOptions)
   let flags = null
   if (session) {
     const client = new PostHog(
@@ -318,9 +364,11 @@ export async function getServerSideProps(ctx) {
         host: process.env.NEXT_PUBLIC_POSTHOG_HOST,
       }
     )
-    flags = await client.getAllFlags(session.user.email);
+    // A stable ID from your auth system, not an email. See the note below.
+    const distinctId = session.user.id
+    flags = await client.getAllFlags(distinctId);
     client.capture({
-      distinctId: session.user.email,
+      distinctId,
       event: 'loaded blog article',
       properties: {
         $current_url: ctx.req.url,
@@ -339,6 +387,28 @@ export async function getServerSideProps(ctx) {
 }
 ```
 
+> **Note**: next-auth doesn't put a user ID on the session by default. Its session is `{ name, email, image }`, so `session.user.id` is `undefined` until you add it yourself with a session callback in your `authOptions`:
+>
+> JavaScript
+>
+> PostHog AI
+>
+> ```javascript
+> // lib/auth.js
+> export const authOptions = {
+>   callbacks: {
+>     session({ session, token, user }) {
+>       // JWT sessions (the default) carry the user ID in token.sub.
+>       // Database sessions get it from user.id instead.
+>       session.user.id = token?.sub ?? user.id
+>       return session
+>     },
+>   },
+> }
+> ```
+>
+> Capturing with an `undefined` distinct ID creates events that belong to nobody, so check that the ID arrives before relying on it.
+
 > **Note**: Make sure to *always* call `await client.shutdown()` after sending events from the server-side. PostHog queues events into larger batches, and this call forces all batched events to be flushed immediately.
 
 ### Server-side configuration
@@ -374,10 +444,6 @@ To improve the reliability of client-side tracking and make requests less likely
 -   [How to set up Next.js pages router analytics, feature flags, and more](/tutorials/nextjs-pages-analytics.md)
 -   [How to set up Next.js A/B tests](/tutorials/nextjs-ab-tests.md)
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/nuxt-js-3-6.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Nuxt.js (v3.0 to v3.6) - Docs
+
+Copy page
+
 # Nuxt.js (v3.0 to v3.6) - Docs
 
 PostHog makes it easy to get data about usage of your [Nuxt.js](https://nuxt.com/) app. Integrating PostHog into your app enables analytics about user behavior, custom events capture, session replays, feature flags, and more.
@@ -34,6 +40,18 @@ pnpm add posthog-js
 bun add posthog-js
 ```
 
+> **If your site sets a Content-Security-Policy**, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog's CDN, and sends events to the ingestion host. PostHog serves from subdomains of `posthog.com` that change over time, so allow the wildcard:
+>
+> PostHog AI
+>
+> ```
+> script-src 'self' https://*.posthog.com;
+> connect-src 'self' https://*.posthog.com;
+> worker-src 'self' blob: data:;
+> ```
+>
+> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+
 2.  Store your PostHog key and host in environment variables rather than hard-coding them. Add them to a `.env` file (and to your hosting provider). You can find these in [your project settings](https://us.posthog.com/settings/project).
 
 .env
@@ -113,10 +131,28 @@ PostHog AI
 </script>
 ```
 
-See the [JavaScript SDK docs](/docs/libraries/js/features.md) for all usable functions, such as:
+See the [JavaScript SDK docs](/docs/libraries/js/usage.md) for all usable functions, such as:
 
--   [Capture custom event capture, identify users, and more.](/docs/libraries/js/features.md#capturing-events)
--   [Feature flags including variants and payloads.](/docs/libraries/js/features.md#feature-flags)
+-   [Capture custom event capture, identify users, and more.](/docs/libraries/js/usage.md#capturing-events)
+-   [Feature flags including variants and payloads.](/docs/libraries/js/usage.md#feature-flags)
+
+If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
+
+JavaScript
+
+PostHog AI
+
+```javascript
+posthog.init('<ph_project_token>', {
+  api_host: 'https://us.i.posthog.com',
+  // Optional: send PostHog session/user context to your backend
+  tracing_headers: ['api.example.com'],
+})
+```
+
+This works in local development too, but match on the hostname alone: use `'localhost'`, not `'localhost:3000'`. Ports are never part of a hostname, so a value with one in it never matches anything. `localhost` and `127.0.0.1` are also different hostnames — use whichever your app actually calls.
+
+Tracing headers help you attribute events across front and backend consistently. When this isn't available, use your server-side stable IDs to deduce the matching `distinctId`, and pass it in when capturing the event.
 
 Set up a reverse proxy (recommended)
 
@@ -235,10 +271,6 @@ Alternatively, the following tutorials can help you get started:
 -   [How to set up A/B tests in Nuxt](/tutorials/nuxtjs-ab-tests.md)
 -   [How to set up surveys in Nuxt](/tutorials/nuxt-surveys.md)
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/nuxt-js.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Nuxt.js - Docs
+
+Copy page
+
 # Nuxt.js - Docs
 
 PostHog makes it easy to get data about usage of your [Nuxt.js](https://nuxt.com/) app. Integrating PostHog into your app enables analytics about user behavior, custom events capture, session replays, feature flags, and more.
@@ -45,12 +51,46 @@ pnpm add @posthog/nuxt
 bun add @posthog/nuxt
 ```
 
+> **If your site sets a Content-Security-Policy**, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog's CDN, and sends events to the ingestion host. PostHog serves from subdomains of `posthog.com` that change over time, so allow the wildcard:
+>
+> PostHog AI
+>
+> ```
+> script-src 'self' https://*.posthog.com;
+> connect-src 'self' https://*.posthog.com;
+> worker-src 'self' blob: data:;
+> ```
+>
+> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+
 ## Identifying users
 
 > **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](/docs/session-replay.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too.
 >
+> Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like `"anonymous"` or `"user"`, which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that's automatically assigned.
+>
+> Call `posthog.reset()` on logout, so the next person to use the browser doesn't inherit the last one's identity.
+>
 > See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
 
+If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
+
+JavaScript
+
+PostHog AI
+
+```javascript
+posthog.init('<ph_project_token>', {
+  api_host: 'https://us.i.posthog.com',
+  // Optional: send PostHog session/user context to your backend
+  tracing_headers: ['api.example.com'],
+})
+```
+
+This works in local development too, but match on the hostname alone: use `'localhost'`, not `'localhost:3000'`. Ports are never part of a hostname, so a value with one in it never matches anything. `localhost` and `127.0.0.1` are also different hostnames — use whichever your app actually calls.
+
+Tracing headers help you attribute events across front and backend consistently. When this isn't available, use your server-side stable IDs to deduce the matching `distinctId`, and pass it in when capturing the event.
+
 ## Configuration
 
 Store your PostHog keys in environment variables rather than hard-coding them. Add them to a `.env` file (and to your hosting provider). You can find these values in [your project settings](https://us.posthog.com/settings/project).
@@ -244,10 +284,6 @@ Alternatively, the following tutorials can help you get started:
 -   [How to set up A/B tests in Nuxt](/tutorials/nuxtjs-ab-tests.md)
 -   [How to set up surveys in Nuxt](/tutorials/nuxt-surveys.md)
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/php.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# PHP - Docs
+
+Copy page
+
 # PHP - Docs
 
 This is an optional library you can install if you're working with PHP. It uses an internal queue to batch requests, flushes at the end of the request, and optionally does so in an async manner.
@@ -637,10 +643,6 @@ PostHog::init(
 
 This library is largely based on the `analytics-php` package.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/posthog-python.md

@@ -1,6 +1,8 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
 # PostHog Python SDK
 
-**SDK Version:** 7.22.1
+**SDK Version:** 7.38.4
 
 Integrate PostHog into any python application.
 
@@ -34,11 +36,11 @@ Initialize a new PostHog client instance.
 - **`debug`** (`bool`) - Enable verbose SDK logging and re-raise errors from public         API methods.
 - **`max_queue_size`** (`int`) - Maximum number of events buffered before upload.
 - **`send`** (`bool`) - If False, queueing succeeds but events are not sent.
-- **`on_error`** (`any`) - Optional callback invoked by background consumers when an         upload fails.
+- **`on_error`** (`any`) - Optional callback invoked by background consumers when an         upload fails. Keep it short and non-blocking. Calling lifecycle         methods directly is safe and deferred, but do not start another         thread or task that calls ``flush()``, ``join()``, or         ``shutdown()`` and then wait for it from the callback.
 - **`flush_at`** (`int`) - Number of queued events that triggers a batch upload.
 - **`flush_interval`** (`float`) - Maximum seconds a background consumer waits before         flushing a partial batch.
 - **`gzip`** (`bool`) - Whether to gzip event upload payloads.
-- **`max_retries`** (`int`) - Number of upload retries for background consumers.
+- **`max_retries`** (`int`) - Number of upload retries. Values below 0 are treated as 0.
 - **`sync_mode`** (`bool`) - If True, send each event synchronously instead of using         background worker threads.
 - **`timeout`** (`int`) - HTTP request timeout in seconds for event uploads.
 - **`thread`** (`int`) - Number of background consumer threads.
@@ -72,7 +74,9 @@ Initialize a new PostHog client instance.
 - **`capture_mode`** (`CaptureMode`) - Capture wire protocol to use. Defaults to         ``CaptureMode.V0`` (legacy ``/batch/``). Set ``CaptureMode.V1``         (or pass the string ``"v1"``) to opt into         ``/i/v1/analytics/events``. When omitted, the         ``POSTHOG_CAPTURE_MODE`` env var is consulted, then ``V0``.
 - **`capture_compression`** (`CaptureCompression`) - Request-body compression for capture-v1 uploads         (ignored in V0, which uses ``gzip``). ``CaptureCompression.GZIP``         or ``DEFLATE`` (or the strings ``"gzip"``/``"deflate"``). When         omitted, the ``POSTHOG_CAPTURE_COMPRESSION`` env var is consulted,         then the legacy ``gzip`` flag, then no compression.
 - **`secret_key`** (`any`) - A Personal API Key or Project Secret API Key, used to         authenticate local feature flag evaluation, remote config         payloads, and decrypted flag payloads. Example::              posthog.Client(project_api_key, secret_key="phx_...")
-- **`_dedicated_ai_endpoint`** (`bool`)
+- **`metrics?`** (`dict`)
+- **`_use_ai_lane`** (`bool`)
+- **`_enable_multimodal_capture`** (`bool`)
 
 ### Returns
 
@@ -98,8 +102,8 @@ Create an alias between two distinct IDs.
 
 ### Parameters
 
-- **`previous_id?`** (`str`) - The previous distinct ID.
-- **`distinct_id?`** (`str`) - The new distinct ID to alias to.
+- **`previous_id?`** (`Number`) - The previous distinct ID. Required - the call is dropped         with a warning if it is missing or empty.
+- **`distinct_id?`** (`str`) - The new distinct ID to alias to. Falls back to the         context distinct ID; the call is dropped with a warning if         neither is available.
 - **`timestamp`** (`datetime`) - The timestamp of the event.
 - **`uuid?`** (`str`) - A unique identifier for the event. If provided, it must be a         valid UUID string or uuid.UUID instance; invalid values are         ignored and replaced with a newly generated UUID.
 - **`disable_geoip?`** (`bool`) - Whether to disable GeoIP for this event.
@@ -124,8 +128,8 @@ Identify a group and set its properties.
 
 ### Parameters
 
-- **`group_type?`** (`str`) - The type of group (e.g., 'company', 'team').
-- **`group_key?`** (`str`) - The unique identifier for the group.
+- **`group_type?`** (`str`) - The type of group (e.g., 'company', 'team'). Required -         the call is dropped with a warning if it is missing or empty.
+- **`group_key?`** (`str`) - The unique identifier for the group. Required - the call         is dropped with a warning if it is missing or empty.
 - **`properties?`** (`dict[str, Any]`) - A dictionary of properties to set on the group.
 - **`timestamp`** (`datetime`) - The timestamp of the event.
 - **`uuid`** (`str`) - A unique identifier for the event. If provided, it must be a         valid UUID string or uuid.UUID instance; invalid values are         ignored and replaced with a newly generated UUID.
@@ -259,7 +263,7 @@ posthog.capture('$pageview', distinct_id="distinct_id_of_the_user", properties={
 
 **Release Tag:** public
 
-Capture an exception for error tracking.
+Capture an exception for error tracking.  When OpenTelemetry is installed and a valid span is active, its trace and span IDs are added as ``$trace_id`` and ``$span_id`` event properties.
 
 ### Parameters
 
@@ -696,7 +700,7 @@ if flag_result and flag_result.get_value() == 'variant-key':
 
 **Release Tag:** public
 
-End the consumer thread once the queue is empty. Do not use directly, call `shutdown()` instead.
+Attempt to process queued events and end the consumer threads. Do not use directly, call `shutdown()` instead.  Failed or undrainable events may be dropped and reported through logging or ``on_error``; returning does not guarantee server receipt. Lifecycle cleanup is attempted once, and cleanup failures are logged without retry.
 
 ### Returns
 
@@ -714,7 +718,7 @@ posthog.join()
 
 **Release Tag:** public
 
-Flush all messages and cleanly shutdown the client. Call this before the process ends in serverless environments to avoid data loss.
+Flush all messages and cleanly shutdown the client. Call this before the process ends in serverless environments to avoid data loss.  Normally this method blocks until queued events have been attempted and cleanup finishes. Failed or undrainable events may be dropped and reported through logging or ``on_error``; returning does not guarantee server receipt. Lifecycle cleanup is attempted once, and cleanup failures are logged without retry. When called directly from an SDK callback such as ``on_error``, shutdown is deferred to avoid blocking the worker that invoked the callback. If the callback must coordinate a blocking shutdown, have it signal an application-owned thread and return before that thread calls shutdown. Do not wait inside the callback for another thread or task that calls a lifecycle method.
 
 ### Returns
 
@@ -867,7 +871,7 @@ To marry up whatever a user does before they sign up or log in with what they do
 
 ### Parameters
 
-- **`previous_id?`** (`str`) - The unique ID of the user before
+- **`previous_id?`** (`Number`) - The unique ID of the user before
 - **`distinct_id?`** (`str`) - The current unique id
 - **`timestamp?`** (`datetime`) - Optional timestamp for the event
 - **`uuid?`** (`str`) - Optional UUID for the event
@@ -895,8 +899,8 @@ Set properties on a group.
 
 ### Parameters
 
-- **`group_type?`** (`str`) - Type of your group
-- **`group_key?`** (`str`) - Unique identifier of the group
+- **`group_type?`** (`str`) - Type of your group. Required - the call is dropped with a         warning if it is missing or empty.
+- **`group_key?`** (`str`) - Unique identifier of the group. Required - the call is         dropped with a warning if it is missing or empty.
 - **`properties?`** (`dict[str, Any]`) - Properties to set on the group
 - **`timestamp?`** (`datetime`) - Optional timestamp for the event
 - **`uuid?`** (`str`) - Optional UUID for the event
@@ -1366,7 +1370,7 @@ flush()
 
 **Release Tag:** public
 
-Block program until the client clears the queue. Used during program shutdown. You should use `shutdown()` directly in most cases.
+Attempt to process queued events and stop the client's background workers. Use `shutdown()` directly in most cases.  Failed or undrainable events may be dropped and reported through logging or ``on_error``; returning does not guarantee server receipt. Lifecycle cleanup is attempted once, and cleanup failures are logged without retry.
 
 ### Returns
 
@@ -1385,7 +1389,7 @@ join()
 
 **Release Tag:** public
 
-Flush all messages and cleanly shutdown the client.
+Flush all messages and cleanly shutdown the client.  This normally blocks until queued events have been attempted and cleanup finishes. Failed or undrainable events may be dropped and reported through logging or ``on_error``; returning does not guarantee server receipt. Lifecycle cleanup is attempted once, and cleanup failures are logged without retry. Calls made directly from SDK callbacks such as ``on_error`` are deferred to avoid deadlocking the worker. If blocking completion is required, signal an application-owned thread, return from the callback, and call ``shutdown()`` from that thread. Do not wait inside a callback for another thread or task calling a lifecycle method.
 
 ### Returns
 
@@ -1666,7 +1670,7 @@ tag("user_id", "123")
 
 **Release Tag:** public
 
-Create or return the global PostHog client configured by module settings.  Most applications should either instantiate ``Posthog`` directly or set ``posthog.api_key``/other module settings before calling top-level helpers. ``setup()`` is called automatically by global APIs such as ``capture()``.  Returns:     The global ``Client`` instance. If ``api_key`` is missing or blank,     the client is disabled and module-level calls become no-ops.
+Create or return the global PostHog client configured by module settings.  Most applications should either instantiate ``Posthog`` directly or set ``posthog.api_key``/other module settings before calling top-level helpers. ``setup()`` is called automatically by global APIs such as ``capture()``.  Returns:     The global ``Client`` instance. If both ``api_key`` and     ``project_api_key`` are missing or blank, the client is disabled and     module-level calls become no-ops.
 
 ### Returns
 

package/dist/global-skills/instrument-product-analytics/references/python.md

@@ -1,10 +1,14 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
 # Python - Docs
 
-The Python SDK makes it easy to capture events, evaluate feature flags, track errors, and more in your Python apps.
+Copy page
+
+# Python - Docs
 
-**Python 3.9 and lower**
+The Python SDK makes it easy to capture events, evaluate feature flags, track errors, and more in your Python apps.
 
-Python 3.9 is no longer supported for PostHog Python SDK versions `7.x.x` and higher.
+> These docs cover version `7.x` of the Python SDK, which requires Python 3.10 or higher. On Python 3.9? See [supported versions](#supported-versions).
 
 ## Installation
 
@@ -54,6 +58,8 @@ You can find your project token and instance address in the [project settings](h
 >         capture("foo_viewed")
 >     return {"status": "ok"}
 > ```
+>
+> When possible, write a small piece of **middleware** that resolves your authenticated user, wrap a context around the request, and identifies it. Every `capture()` downstream is then attributed *automatically*. The SDK's Django middleware does this automatically and you can replicate it when using the plain Python SDK.
 
 ## Capturing events
 
@@ -889,9 +895,13 @@ As our open source project [PostHog](https://github.com/PostHog/posthog) shares
 
 This library is largely based on the `analytics-python` package.
 
-### Community questions
+## Supported versions
+
+These docs cover version `7.x` of the PostHog Python SDK, which requires Python 3.10 or higher. Python 3.9 is no longer supported on `7.x.x` and higher — pin to the 6.x line with `pip install 'posthog<7'`, where `6.9.3` is the final release.
+
+Everything on this page works the same way on `6.9.3`. Event capture, the context API (`new_context`, `identify_context`, `set_context_session`), and `PosthogContextMiddleware` are identical on `6.9.3` and `7.0.0` — `7.0.0` only dropped Python 3.9 and bumped the optional LLM provider SDKs. That includes the middleware identifying the request context from the `X-POSTHOG-DISTINCT-ID` header and falling back to the authenticated user, which behaves the same across both lines.
 
-Ask a question
+Later `7.x` releases add what the 6.x line does not receive, such as the Celery integration, tracing header sanitization, and `set_context_device_id`. They also changed the middleware's own captured properties: `7.x` sends the request IP as `$ip`, where `6.9.3` sends it as `$ip_address`, and `7.x` additionally captures `$request_path`, `$raw_user_agent`, and the authenticated user's `email`.
 
 ### Was this page useful?
 

package/dist/global-skills/instrument-product-analytics/references/react-native.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# React Native - Docs
+
+Copy page
+
 # React Native - Docs
 
 ## Installation
@@ -159,7 +165,7 @@ You can further customize how PostHog works through its configuration on initial
 | defaultOptInType: BooleanDefault: true | If set to false, the SDK will not track until the optIn() function is called. |
 | sendFeatureFlagEventType: BooleanDefault: true | Whether to track that getFeatureFlag was called (used by experiments). |
 | preloadFeatureFlagsType: BooleanDefault: true | Whether to load feature flags when initialized or not. |
-| bootstrapType: ObjectDefault: {} | An object containing the distinctId, isIdentifiedId, featureFlags, and featureFlagPayloads keys. distinctId is a string, and featureFlags and featureFlagPayloads are objects of key-value pairs. Used to ensure data is available as soon as the SDK loads. |
+| bootstrapType: ObjectDefault: {} | Seeds identity (distinctId, isIdentifiedId) and feature flag state (featureFlags, featureFlagPayloads) during initialization. See [SDK bootstrapping](/docs/libraries/bootstrapping.md). |
 | disableRemoteFeatureFlagsType: BooleanDefault: false | When true, the SDK never fetches or evaluates feature flags from PostHog, and identify(), group(), and reset() stop triggering /flags requests. Supply flag values yourself via bootstrap (at startup) and updateFlags() (at runtime). Available in version 4.49.0+. |
 | fetchRetryCountType: NumberDefault: 3 | How many times HTTP requests will be retried. |
 | fetchRetryDelayType: NumberDefault: 3000 | The delay between HTTP request retries. |
@@ -177,6 +183,9 @@ You can further customize how PostHog works through its configuration on initial
 | evaluationContextsType: Array of StringsDefault: undefined | Evaluation context tags that constrain which feature flags are evaluated. When set, only flags with matching evaluation context tags (or no evaluation context tags) will be returned. This helps reduce unnecessary flag evaluations and improves performance. See [evaluation contexts documentation](/docs/feature-flags/evaluation-contexts.md) for more details. Available in version 4.21.0+. The legacy parameter evaluationEnvironments (version 4.10.0+) is also supported for backward compatibility. |
 | addTracingHeadersType: Array of StringsDefault: undefined | Hostnames for which PostHog should add tracing headers to outgoing fetch requests. Matching requests include X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID, which lets backend events, errors, and LLM traces link back to frontend sessions and replays. Use hostnames only, without the protocol or path. |
 | before_sendType: FunctionDefault: undefined | A callback function that is called before each event is sent to PostHog. You can use it to modify, filter, or suppress events. Return null to drop the event, or return the modified event to send it. See [customizing exception capture](#customizing-exception-capture-with-before_send) for details. |
+| capturePushNotificationSubscriptionsType: BooleanDefault: true | Whether to automatically register this device's push token so [Workflows](/docs/workflows.md) can target it. Requires @posthog/react-native-plugin. See [push notifications](#push-notifications). Available in version 4.62.0+. |
+| capturePushNotificationOpenedType: BooleanDefault: true | Whether to automatically capture $push_notification_opened when the user taps a push notification. Requires @posthog/react-native-plugin. See [push notifications](#push-notifications). Available in version 4.62.0+. |
+| pushIdentityProviderType: FunctionDefault: undefined | Supplies a signed identity-verification token for push subscription requests. Only needed when your push channel requires identity verification. See [identity verification](#identity-verification). Available in version 4.62.0+. |
 
 ### Tracing headers
 
@@ -1050,13 +1059,38 @@ The list of properties that this overrides:
 
 This enables any geolocation-based flags to work without manually setting these properties.
 
-### Bootstrapping Flags
+### Bootstrapping flags
 
 Since there is a delay between initializing PostHog and fetching feature flags, feature flags are not always available immediately. This makes them unusable if you want to do something like redirecting a user to a different page based on a feature flag.
 
 To have your feature flags available immediately, you can initialize PostHog with precomputed values until it has had a chance to fetch them. This is called bootstrapping. After the SDK fetches feature flags from PostHog, it will use those flag values instead of bootstrapped ones.
 
-For details on how to implement bootstrapping, see our [bootstrapping guide](/docs/feature-flags/bootstrapping.md).
+Pass `bootstrap` in the initialization options to seed identity and flag values:
+
+React Native
+
+PostHog AI
+
+```jsx
+<PostHogProvider
+    apiKey="<ph_project_token>"
+    options={{
+        host: 'https://us.i.posthog.com',
+        bootstrap: {
+            distinctId: 'distinct_id_of_your_user',
+            isIdentifiedId: true,
+            featureFlags: {
+                'flag-1': true,
+                'variant-flag': 'control',
+            },
+        },
+    }}
+>
+    <MyComponent />
+</PostHogProvider>
+```
+
+See [bootstrapping Feature Flags](/docs/feature-flags/bootstrapping.md) for server-side evaluation and flag lifecycle, and [SDK bootstrapping](/docs/libraries/bootstrapping.md) for cross-SDK identity behavior.
 
 ### Supplying flags from your own backend
 
@@ -1208,6 +1242,10 @@ To set up surveys, follow the [additional installation instructions for React Na
 
 > Note: URL and CSS selector targeting are not supported in React Native. Surveys that rely on these conditions will not appear.
 
+## Push notifications
+
+The React Native SDK can register a device for [Workflows](/docs/workflows.md) push notifications and capture when a user opens one. For setup, including automatic and manual registration, capturing opens, opting out, and identity verification, see [Push notifications](/docs/workflows/push-notifications.md).
+
 ## Debug mode
 
 If you're not seeing the expected events being captured, the feature flags being evaluated, or the surveys being shown, you can enable debug mode to see what's happening.
@@ -1329,10 +1367,6 @@ posthog.setPersonPropertiesForFlags(...) // instead of `personProperties`
 posthog.setGroupPropertiesForFlags(...) // instead of `groupProperties`
 ```
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-product-analytics/references/react-router-v6.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# React Router V6 - Docs
+
+Copy page
+
 # React Router V6 - Docs
 
 This guide walks you through setting up PostHog for React Router V6. If you're using React Router v7, find the guide for that mode in the [React Router page](/docs/libraries/react-router.md). If you're using React with another framework, go to the [React integration guide](/docs/libraries/react.md).
@@ -36,6 +42,18 @@ This guide walks you through setting up PostHog for React Router V6. If you're u
     bun add posthog-js @posthog/react
     ```
 
+    > **If your site sets a Content-Security-Policy**, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog's CDN, and sends events to the ingestion host. PostHog serves from subdomains of `posthog.com` that change over time, so allow the wildcard:
+    >
+    > PostHog AI
+    >
+    > ```
+    > script-src 'self' https://*.posthog.com;
+    > connect-src 'self' https://*.posthog.com;
+    > worker-src 'self' blob: data:;
+    > ```
+    >
+    > `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+
 2.  2
 
     ## Add your environment variables
@@ -367,10 +385,6 @@ This guide walks you through setting up PostHog for React Router V6. If you're u
      -   [PostHog AI](/docs/posthog-ai.md): After capturing events, use PostHog AI to help you understand your data and build insights.
      -   [Feature flags and experiments](/docs/libraries/react.md#feature-flags): Feature flag and experiment setup is the same as React. You can find more details in the React integration guide.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better