vybekiit 0.7.3 → 0.7.7

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

@@ -194,7 +194,7 @@ If you're using PostHog's JavaScript SDK on the frontend, enable tracing headers
 ```javascript
 posthog.init('<ph_project_token>', {
     api_host: 'https://us.i.posthog.com',
-    __add_tracing_headers: ['your-backend-domain.com'],
+    tracing_headers: ['your-backend-domain.com'],
 })
 ```
 
@@ -271,6 +271,49 @@ class CoreConfig(AppConfig):
         if settings.DEBUG:
             posthog.debug = True
 
+        # Register the auth signal that identifies the login request's context.
+        from . import signals  # noqa: F401
+
+```
+
+---
+
+## core/signals.py
+
+```py
+"""PostHog identity for the login request.
+
+The middleware reads request.user once, before any view runs. On a login request
+the visitor is still anonymous at that point, so the request's context has no
+distinct ID, and calling login() inside the view does not change that. This
+signal runs inside the login request and identifies the ambient context, so
+every capture later in that same request is attributed to the user who just
+logged in. Requests made after login don't need this: the middleware sees the
+authenticated user from the start.
+"""
+
+import posthog
+from posthog import identify_context
+from django.contrib.auth.signals import user_logged_in
+from django.dispatch import receiver
+
+
+@receiver(user_logged_in)
+def identify_posthog_user(sender, request, user, **kwargs):
+    identify_context(str(user.pk))
+
+    # PII belongs in person properties, never in event properties.
+    posthog.set(
+        distinct_id=str(user.pk),
+        properties={
+            'email': user.email,
+            'username': user.username,
+            'name': user.get_full_name() or user.username,
+            'is_staff': user.is_staff,
+            'date_joined': user.date_joined.isoformat(),
+        },
+    )
+
 ```
 
 ---
@@ -739,7 +782,7 @@ urlpatterns = [
 """Django views demonstrating PostHog integration patterns"""
 
 import posthog
-from posthog import new_context, identify_context, tag, capture
+from posthog import capture
 from django.shortcuts import render, redirect
 from django.contrib.auth import authenticate, login, logout
 from django.contrib.auth.decorators import login_required
@@ -762,20 +805,11 @@ def home_view(request):
         if user is not None:
             login(request, user)
 
-            # PostHog: Identify user and capture login event
-            with new_context():
-                identify_context(str(user.id))
-
-                # Set person properties (PII goes in tag, not capture)
-                tag('email', user.email)
-                tag('username', user.username)
-                tag('name', user.get_full_name() or user.username)
-                tag('is_staff', user.is_staff)
-                tag('date_joined', user.date_joined.isoformat())
-
-                capture('user_logged_in', properties={
-                    'login_method': 'email',
-                })
+            # PostHog: the user_logged_in signal (core/signals.py) has identified
+            # this request's context, so a plain capture is attributed.
+            capture('user_logged_in', properties={
+                'login_method': 'email',
+            })
 
             return redirect('dashboard')
         else:
@@ -787,12 +821,9 @@ def home_view(request):
 def logout_view(request):
     """Logout the current user"""
     if request.user.is_authenticated:
-        user_id = str(request.user.id)
-
-        # PostHog: Track logout before session ends
-        with new_context():
-            identify_context(user_id)
-            capture('user_logged_out')
+        # PostHog: the middleware identified this request's context from the
+        # still-authenticated user, so capture before calling logout().
+        capture('user_logged_out')
 
         logout(request)
 
@@ -804,12 +835,11 @@ def dashboard_view(request):
     """Dashboard page with feature flag example"""
     user_id = str(request.user.id)
 
-    # PostHog: Track dashboard view
-    with new_context():
-        identify_context(user_id)
-        capture('dashboard_viewed', properties={
-            'is_staff': request.user.is_staff,
-        })
+    # PostHog: the middleware already identified this request's context from the
+    # logged-in user, so a plain capture is attributed to them.
+    capture('dashboard_viewed', properties={
+        'is_staff': request.user.is_staff,
+    })
 
     # PostHog: Check feature flag
     show_new_feature = posthog.feature_enabled(
@@ -854,14 +884,10 @@ def consider_burrito_view(request):
     count = request.session.get('burrito_count', 0) + 1
     request.session['burrito_count'] = count
 
-    user_id = str(request.user.id)
-
     # PostHog: Track custom event
-    with new_context():
-        identify_context(user_id)
-        capture('burrito_considered', properties={
-            'total_considerations': count,
-        })
+    capture('burrito_considered', properties={
+        'total_considerations': count,
+    })
 
     return JsonResponse({
         'success': True,
@@ -875,9 +901,7 @@ def profile_view(request):
     user_id = str(request.user.id)
 
     # PostHog: Track profile view
-    with new_context():
-        identify_context(user_id)
-        capture('profile_viewed')
+    capture('profile_viewed')
 
     context = {
         'user': request.user,
@@ -906,12 +930,10 @@ def trigger_error_view(request):
         posthog.capture_exception(e)
 
         # PostHog: Track error trigger event
-        with new_context():
-            identify_context(str(request.user.id))
-            capture('error_triggered', properties={
-                'error_type': error_type,
-                'error_message': str(e),
-            })
+        capture('error_triggered', properties={
+            'error_type': error_type,
+            'error_message': str(e),
+        })
 
         return JsonResponse({
             'success': False,
@@ -939,17 +961,15 @@ def group_analytics_view(request):
     )
 
     # PostHog: Capture event with group
-    with new_context():
-        identify_context(user_id)
-        capture(
-            'feature_used',
-            properties={
-                'feature_name': 'group_analytics',
-            },
-            groups={
-                'company': 'acme-corp',
-            }
-        )
+    capture(
+        'feature_used',
+        properties={
+            'feature_name': 'group_analytics',
+        },
+        groups={
+            'company': 'acme-corp',
+        }
+    )
 
     return JsonResponse({
         'success': True,

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

@@ -446,8 +446,7 @@ class PostHogMiddleware:
 
         with new_context():
             if user:
-                identify_context(user.email)
-                tag("email", user.email)
+                identify_context(str(user.id))
                 tag("is_staff", user.is_staff)
 
             await self.app(scope, receive, send)
@@ -794,12 +793,11 @@ async def login(
     if user:
         is_new_user = user.record_login(db)
         with new_context():
-            identify_context(user.email)
+            identify_context(str(user.id))
             capture(
                 "user_logged_in",
                 properties={
                     "$set": {"email": user.email, "is_staff": user.is_staff},
-                    "username": user.email,
                     "is_new_user": is_new_user,
                 },
             )
@@ -860,12 +858,11 @@ async def signup(
     user = User.create_user(db, email=email, password=password, is_staff=False)
 
     with new_context():
-        identify_context(user.email)
+        identify_context(str(user.id))
         capture(
             "user_signed_up",
             properties={
                 "$set": {"email": user.email, "is_staff": user.is_staff},
-                "username": user.email,
                 "signup_method": "form",
             },
         )

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

@@ -265,7 +265,7 @@ def consider_burrito():
 
     # PostHog: Capture custom event
     with new_context():
-        identify_context(current_user.email)
+        identify_context(str(current_user.id))
         capture("burrito_considered", properties={"total_considerations": burrito_count})
 
     return jsonify({"success": True, "count": burrito_count})
@@ -291,7 +291,7 @@ def test_error():
         if should_capture:
             # Manually capture this specific exception in PostHog
             with new_context():
-                identify_context(current_user.email)
+                identify_context(str(current_user.id))
                 event_id = posthog.capture_exception(e)
 
             return jsonify({
@@ -398,7 +398,7 @@ from app.main import routes  # noqa: E402, F401
 import posthog
 from flask import flash, redirect, render_template, request, session, url_for
 from flask_login import current_user, login_required, login_user, logout_user
-from posthog import capture, identify_context, new_context, tag
+from posthog import capture, identify_context, new_context
 
 from app.main import main_bp
 from app.models import User
@@ -420,12 +420,17 @@ def home():
 
             # PostHog: Identify user and capture login event
             with new_context():
-                identify_context(user.email)
-
-                # Set person properties (PII goes in tag, not capture)
-                tag("email", user.email)
-                tag("is_staff", user.is_staff)
-                tag("date_joined", user.date_joined.isoformat())
+                identify_context(str(user.id))
+
+                # PII belongs in person properties, never in event properties
+                posthog.set(
+                    distinct_id=str(user.id),
+                    properties={
+                        "email": user.email,
+                        "is_staff": user.is_staff,
+                        "date_joined": user.date_joined.isoformat(),
+                    },
+                )
 
                 capture("user_logged_in", properties={"login_method": "password"})
 
@@ -464,11 +469,16 @@ def signup():
 
             # PostHog: Identify new user and capture signup event
             with new_context():
-                identify_context(user.email)
+                identify_context(str(user.id))
 
-                tag("email", user.email)
-                tag("is_staff", user.is_staff)
-                tag("date_joined", user.date_joined.isoformat())
+                posthog.set(
+                    distinct_id=str(user.id),
+                    properties={
+                        "email": user.email,
+                        "is_staff": user.is_staff,
+                        "date_joined": user.date_joined.isoformat(),
+                    },
+                )
 
                 capture("user_signed_up", properties={"signup_method": "form"})
 
@@ -486,7 +496,7 @@ def logout():
     """Logout and capture event."""
     # PostHog: Capture logout event before session ends
     with new_context():
-        identify_context(current_user.email)
+        identify_context(str(current_user.id))
         capture("user_logged_out")
 
     logout_user()
@@ -499,7 +509,7 @@ def dashboard():
     """Dashboard with feature flag demonstration."""
     # PostHog: Capture dashboard view
     with new_context():
-        identify_context(current_user.email)
+        identify_context(str(current_user.id))
         capture("dashboard_viewed", properties={"is_staff": current_user.is_staff})
 
     # Check feature flag
@@ -538,7 +548,7 @@ def profile():
     """User profile page."""
     # PostHog: Capture profile view
     with new_context():
-        identify_context(current_user.email)
+        identify_context(str(current_user.id))
         capture("profile_viewed")
 
     return render_template("profile.html")

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

@@ -115,7 +115,7 @@ export default defineNuxtPlugin((nuxtApp) => {
 })
 ```
 
-The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers when `__add_tracing_headers` is configured in the PostHog initialization.
+The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers when `tracing_headers` is configured in the PostHog initialization.
 
 **Important**: do not identify users on the server-side.
 
@@ -138,7 +138,7 @@ const handleSubmit = async () => {
 }
 ```
 
-The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `__add_tracing_headers` option in the PostHog initialization.
+The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `tracing_headers` option in the PostHog initialization.
 
 **Important**: do not identify users on the server-side.
 
@@ -153,7 +153,7 @@ import { getHeader } from 'h3'
 export default defineEventHandler(async (event) => {
   const runtimeConfig = useRuntimeConfig()
 
-  // Relies on __add_tracing_headers being set in the client-side SDK
+  // Relies on tracing_headers being set in the client-side SDK
   const sessionId = getHeader(event, 'x-posthog-session-id')
   const distinctId = getHeader(event, 'x-posthog-distinct-id')
 
@@ -711,6 +711,9 @@ export default defineNuxtPlugin((nuxtApp) => {
   const posthogClient = posthog.init(runtimeConfig.public.posthog.publicKey, {
     api_host: runtimeConfig.public.posthog.host,
     defaults: runtimeConfig.public.posthog.posthogDefaults as any,
+    // Automatically add X-POSTHOG-SESSION-ID and X-POSTHOG-DISTINCT-ID headers
+    // to same-origin requests so server-side events join the same session.
+    tracing_headers: [window.location.hostname],
     loaded: (posthog: PostHogInterface) => {
       if (import.meta.env.MODE === 'development') posthog.debug()
     },
@@ -772,7 +775,7 @@ export default defineEventHandler(async (event) => {
 
   const runtimeConfig = useRuntimeConfig()
 
-    // Relies on __add_tracing_headers being set in the client-side SDK
+    // Relies on tracing_headers being set in the client-side SDK
   const sessionId = getHeader(event, 'x-posthog-session-id')
   const distinctId = getHeader(event, 'x-posthog-distinct-id')
 
@@ -844,7 +847,7 @@ export default defineEventHandler(async (event) => {
 
   const runtimeConfig = useRuntimeConfig()
 
-  // Relies on __add_tracing_headers being set in the client-side SDK
+  // Relies on tracing_headers being set in the client-side SDK
   const sessionId = getHeader(event, 'x-posthog-session-id')
   const distinctId = getHeader(event, 'x-posthog-distinct-id')
 

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

@@ -117,7 +117,7 @@ export default defineNuxtConfig({
     host: process.env.NUXT_PUBLIC_POSTHOG_HOST || 'https://us.i.posthog.com',
     clientConfig: {
       capture_exceptions: true, // Enables automatic exception capture on the client side (Vue)
-      __add_tracing_headers: ['localhost', 'yourdomain.com'], // Add your domain here
+      tracing_headers: ['localhost', 'yourdomain.com'], // Add your domain here
     },
     serverConfig: {
       enableExceptionAutocapture: true, // Enables automatic exception capture on the server side (Nitro)
@@ -138,7 +138,7 @@ export default defineNuxtConfig({
 - Client-side error tracking is enabled via `capture_exceptions: true`
 - Server-side error tracking is enabled via `enableExceptionAutocapture: true`
 - Source map uploads are configured for better error tracking
-- The `__add_tracing_headers` option automatically adds `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers to requests
+- The `tracing_headers` option automatically adds `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers to requests
 
 **Important**: do not identify users on the server-side.
 
@@ -161,7 +161,7 @@ const handleSubmit = async () => {
 }
 ```
 
-The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `__add_tracing_headers` option in the PostHog configuration.
+The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `tracing_headers` option in the PostHog configuration.
 
 **Important**: do not identify users on the server-side.
 
@@ -879,7 +879,7 @@ export default defineNuxtConfig({
     host: process.env.NUXT_PUBLIC_POSTHOG_HOST || 'https://us.i.posthog.com', // Optional: defaults to https://us.i.posthog.com. Use https://eu.i.posthog.com for EU region
     clientConfig: {
       capture_exceptions: true, // Enables automatic exception capture on the client side (Vue)
-      __add_tracing_headers: [ 'localhost', 'yourdomain.com' ], // Add your domain here
+      tracing_headers: [ 'localhost', 'yourdomain.com' ], // Add your domain here
     },
     serverConfig: {
       enableExceptionAutocapture: true, // Enables automatic exception capture on the server side (Nitro)

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-react-react-router-7-framework.md

@@ -84,7 +84,7 @@ import { PostHogProvider } from '@posthog/react'
 posthog.init(import.meta.env.VITE_PUBLIC_POSTHOG_PROJECT_TOKEN, {
   api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST,
   defaults: '2026-01-30',
-  __add_tracing_headers: [ window.location.host, 'localhost' ],
+  tracing_headers: [ window.location.hostname ],
 });
 
 <PostHogProvider client={posthog}>
@@ -105,7 +105,7 @@ posthog?.capture('user_logged_in', {
 });
 ```
 
-The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `__add_tracing_headers` option in the PostHog initialization.
+The session and distinct ID are automatically passed to the backend via the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers because we set the `tracing_headers` option in the PostHog initialization.
 
 **Important**: do not identify users on the server-side.
 
@@ -372,7 +372,7 @@ import { PostHogProvider } from '@posthog/react'
 posthog.init(import.meta.env.VITE_PUBLIC_POSTHOG_PROJECT_TOKEN, {
   api_host: import.meta.env.VITE_PUBLIC_POSTHOG_HOST,
   defaults: '2026-01-30',
-  __add_tracing_headers: [ window.location.host, 'localhost' ],
+  tracing_headers: [ window.location.hostname ],
 });
 
 

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-ruby-on-rails.md

@@ -117,9 +117,11 @@ end
 class User < ApplicationRecord
   has_secure_password
 
-  # Called by posthog-rails for automatic user association in error reports
+  # Called by posthog-rails for automatic user association in error reports.
+  # The primary key, not the email — an email can change, which splits one
+  # person's history in two, and it is PII on every event's identity.
   def posthog_distinct_id
-    email
+    id.to_s
   end
 
   def posthog_properties
@@ -218,7 +220,7 @@ This example includes the posthog-js snippet in the layout template to demonstra
 
 1. **posthog-js** (frontend) captures pageviews, clicks, and session replay
 2. **posthog-ruby + posthog-rails** (backend) captures business logic events, errors, and feature flag evaluations
-3. **Shared distinct_id** — frontend and backend events are linked when the same `distinct_id` is used on both sides. Call `posthog.identify(user.email)` in posthog-js after login, matching the `posthog_distinct_id` used on the backend
+3. **Shared distinct_id** — frontend and backend events are linked when the same `distinct_id` is used on both sides. Call `posthog.identify(user.id.to_s)` in posthog-js after login, matching the `posthog_distinct_id` used on the backend
 4. **Session replay** lets you watch user sessions where errors occurred
 
 **Note:** Unlike the Django SDK, posthog-rails does not include a context middleware that reads `X-POSTHOG-SESSION-ID` or `X-POSTHOG-DISTINCT-ID` tracing headers. Frontend and backend events are correlated through the shared `distinct_id`.
@@ -584,8 +586,10 @@ class User < ApplicationRecord
   # Called by posthog-rails for automatic user association in error reports.
   # When auto_capture_exceptions and capture_user_context are enabled,
   # posthog-rails calls this method on current_user to get the distinct_id.
+  # The primary key, not the email: an email can change, which would split one
+  # person's history in two, and it is PII on every event's identity.
   def posthog_distinct_id
-    email
+    id.to_s
   end
 
   # Helper used by controllers when calling PostHog.identify to set person properties.

package/dist/global-skills/instrument-product-analytics/references/EXAMPLE-tanstack-start.md

@@ -122,16 +122,21 @@ This client is used in API routes to track server-side events.
 
 ### Server-side capture (routes/api/*)
 
-Server-side events include the client's `$session_id` so they appear in the same session in PostHog. The frontend sends it via a header:
+Server-side events include the client's `$session_id` so they appear in the same session in PostHog. The `tracing_headers` option on the `PostHogProvider` adds the `X-POSTHOG-SESSION-ID` and `X-POSTHOG-DISTINCT-ID` headers to same-origin requests automatically, so the frontend fetch needs no PostHog headers of its own:
 
 ```typescript
-// Frontend: include session ID in API requests
+// Client: tracing_headers is configured once on the PostHogProvider
+options={{
+  api_host: '/ingest',
+  // ...
+  // Guarded for SSR, where `window` is undefined.
+  tracing_headers: typeof window !== 'undefined' ? [window.location.hostname] : [],
+}}
+
+// Frontend fetch — no manual header needed
 await fetch('/api/burrito/consider', {
   method: 'POST',
-  headers: {
-    'Content-Type': 'application/json',
-    'X-PostHog-Session-Id': posthog.get_session_id() ?? '',
-  },
+  headers: { 'Content-Type': 'application/json' },
   body: JSON.stringify({ ... }),
 })
 ```
@@ -352,11 +357,12 @@ export function AuthProvider({ children }: { children: ReactNode }) {
     password: string,
   ): Promise<boolean> => {
     try {
+      // The session and distinct ID are added automatically by the
+      // tracing_headers option configured on the PostHogProvider.
       const response = await fetch('/api/auth/login', {
         method: 'POST',
         headers: {
           'Content-Type': 'application/json',
-          'X-PostHog-Session-Id': posthog.get_session_id() ?? '',
         },
         body: JSON.stringify({ username, password }),
       })
@@ -509,6 +515,11 @@ function RootDocument({ children }: { children: React.ReactNode }) {
             defaults: '2025-05-24',
             capture_exceptions: true,
             debug: import.meta.env.DEV,
+            // Automatically add X-POSTHOG-SESSION-ID and X-POSTHOG-DISTINCT-ID
+            // headers to same-origin requests so server-side events join the
+            // same session. Guarded for SSR, where `window` is undefined.
+            tracing_headers:
+              typeof window !== 'undefined' ? [window.location.hostname] : [],
           }}
         >
           <AuthProvider>
@@ -704,11 +715,12 @@ function BurritoPage() {
     setHasConsidered(true)
     setTimeout(() => setHasConsidered(false), 2000)
 
+    // The session and distinct ID are added automatically by the
+    // tracing_headers option configured on the PostHogProvider.
     await fetch('/api/burrito/consider', {
       method: 'POST',
       headers: {
         'Content-Type': 'application/json',
-        'X-PostHog-Session-Id': posthog.get_session_id() ?? '',
       },
       body: JSON.stringify({
         username: user.username,

package/dist/global-skills/instrument-product-analytics/references/android.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
+
+# Android - Docs
+
+Copy page
+
 # Android - Docs
 
 It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your mobile app.
@@ -566,6 +572,41 @@ PostHog.captureFeatureView("flag-key", flagVariant = "variant-key")
 PostHog.captureFeatureInteraction("flag-key", flagVariant = "variant-key")
 ```
 
+### 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.
+
+Set `config.bootstrap` before calling `setup()` to seed identity and flag values before the first `/flags` response (requires Android SDK `3.55.0`+):
+
+Kotlin
+
+PostHog AI
+
+```kotlin
+import com.posthog.PostHogBootstrapConfig
+val config = PostHogAndroidConfig(apiKey = POSTHOG_API_KEY, host = POSTHOG_HOST)
+config.bootstrap = PostHogBootstrapConfig(
+    distinctId = "distinct_id_of_your_user",
+    isIdentifiedId = true,
+    featureFlags = mapOf(
+        "flag-1" to true,
+        "variant-flag" to "control"
+    )
+)
+PostHogAndroid.setup(this, config)
+```
+
+-   **Bootstrapped identity applies during setup.** On a fresh install, setting it before `setup()` means events captured synchronously during initialization (like `Application Installed`) carry your distinct ID instead of the SDK-generated UUID.
+    -   An **anonymous** bootstrap (`isIdentifiedId: false`, the default) seeds the anonymous ID only when none is persisted yet. Once an anonymous ID exists on disk, or the person has been identified, the SDK ignores it.
+    -   An **identified** bootstrap (`isIdentifiedId: true`) is for a signed-in identity available to your app (for example, from a backend session token). On a fresh install, it seeds the distinct ID, marks the person identified, and generates a separate device ID. On a returning install, a matching anonymous ID is marked identified without emitting `$identify`; a different anonymous ID is merged via `identify()` when person profiles are enabled. This emits `$identify` unless capturing is opted out. A different, already-identified person is left untouched.
+-   **Bootstrapped flags are served until the first `/flags` response, then replaced.** A complete `/flags` response takes over entirely, so bootstrapped-only keys don't persist past it. Only *enabled* flags are seeded: a `true` boolean or a non-empty variant string. A `false` or empty value is dropped, matching posthog-js. Seed payloads with the separate `featureFlagPayloads` option. Flag values and payloads must be JSON-serializable, or they're dropped. Bootstrapped flags are cleared on `reset()`.
+
+The feature-flags-loaded signal fires as soon as bootstrapped flags are applied, so startup logic can read them immediately. These SDKs don't support the `sessionID` bootstrap option. When person profiles are set to `never`, the SDK preserves a different anonymous identity instead of merging it into an identified bootstrap.
+
+See the [SDK bootstrapping guide](/docs/libraries/bootstrapping.md) for the cross-SDK overview.
+
 ## Experiments (A/B tests)
 
 Since [experiments](/docs/experiments/start-here.md) use feature flags, the code for running an experiment is very similar to the feature flags code:
@@ -750,6 +791,7 @@ val config = PostHogAndroidConfig(
 | errorTrackingConfig | PostHogErrorTrackingConfig() | Configures error tracking. autoCapture defaults to false; set it to true to autocapture uncaught exceptions when project settings also enable error tracking. |
 | surveys | false | Internal/experimental native Android survey support. Native Android survey UI is not fully supported or documented yet. |
 | surveysConfig | PostHogSurveysConfig() | Internal/experimental survey display delegate configuration, primarily for hybrid SDKs. |
+| bootstrap | null | Seeds identity (distinctId, isIdentifiedId) and feature-flag state (featureFlags, featureFlagPayloads) before the first /flags response. Bootstrapped identity applies to the first session; only enabled flags are served, until the first /flags response replaces them. See [SDK bootstrapping](/docs/libraries/bootstrapping.md#behavior-on-mobile-sdks). |
 
 ### Event filtering with `beforeSend`
 
@@ -792,6 +834,10 @@ config.addBeforeSend { event ->
 }
 ```
 
+## Push notifications
+
+The Android 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).
+
 ## FAQ
 
 ## What Android API level is required?
@@ -802,10 +848,6 @@ The Android SDK supports Android API 23 and newer.
 
 Usually, no. The SDK declares `android.permission.INTERNET` and `android.permission.ACCESS_NETWORK_STATE`, and Android's manifest merger adds them to your app. The SDK does not declare or require an Android `Service`.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better