trunk-merge/pr-107620/99443364-8fe2-496e-b447-5610198465e4

cli/CHANGELOG.md

@@ -1,5 +1,12 @@
 # posthog-cli
 
+## 0.18.8 — 2026-09-28
+
+### Patch changes
+
+- [09644fddca4](https://github.com/PostHog/posthog/commit/09644fddca4814ae7e95b67353c9c1a13f29bfbc) Read the remote URL from the `[remote "..."]` sections of the Git config only, and prefer `origin`. A repository that records another URL in its config, such as a superproject that records the URL of a submodule, no longer gets the wrong remote URL and repository name in its release metadata. — Thanks @hpouillot!
+- [69a47659037](https://github.com/PostHog/posthog/commit/69a4765903776a5e70d4633590673395b1eaec2f) In event release mode, `sourcemap upload` no longer uploads unchanged chunks again when the bundler names chunks by content, as Vite does by default. Every chunk carries the release id, so every release renamed every chunk, and the content hash covered those names: the map's `file`, the `sourceMappingURL` comment and imports of other chunks. The hash now leaves out script file paths (ending in `.js`, `.mjs` or `.cjs`). Hashes stored by earlier versions include the paths, so the first upload after updating sends each chunk once more. — Thanks @ablaszkiewicz!
+
 ## 0.18.7 — 2026-09-24
 
 ### Patch changes

cli/Cargo.toml

@@ -4,7 +4,7 @@ resolver = "2"
 
 [package]
 name = "posthog-cli"
-version = "0.18.7"
+version = "0.18.8"
 authors = [
     "David <david@posthog.com>",
     "Olly <oliver@posthog.com>",

docs/internal/hogql-language-service.md

@@ -46,9 +46,8 @@ Built-in `posthog.*` namespaces are outside this rollout.
 
 ### Lazy-table traversal catalog
 
-The Go consumer accepts optional traversal metadata alongside the flat catalog.
-This is a consumer-first extension: existing Django snapshots do not publish these annotations yet.
-Deploy the Go consumer before enabling publication in Python, because older consumers reject unknown JSON fields.
+The Python publisher adds traversal metadata alongside the flat catalog using the same permission-filtered HogQL database.
+Deploy the Go traversal consumer before this publisher, because older consumers reject unknown JSON fields.
 Snapshots without traversal metadata keep their existing completion and validation behavior.
 
 A field can carry one of two optional annotations:
@@ -137,19 +136,38 @@ The cache budget includes the traversal graph and annotations; the catalog reque
 Cycles are allowed without recursive expansion.
 Each query path can follow at most 16 relation hops and also consumes the request's field-lookup work budget.
 
-This first consumer slice supports traversal from bound catalog sources, including sources inside CTE bodies.
+Traversal works from bound catalog sources, including sources inside CTE bodies.
 Direct top-level property containers retain their explicit namespace through the existing projected-field provenance rules.
 Projecting a relation or nested virtual property container through a CTE, subquery, or SELECT alias does not yet retain traversal provenance.
-Quoted path completion, nested JSON schemas, scalar traverser expression inference, and execution of lazy joins remain outside this slice.
+Quoted path completion, nested JSON schemas, scalar traverser expression inference, and execution of lazy joins remain unsupported by this graph.
 For deeper JSON paths under an explicit property namespace, validation checks the first property key but does not validate its descendants.
 
-The Python publisher follow-up must resolve `LazyJoin`, `VirtualTable`, and table-valued `FieldTraverser` targets using the same permission-filtered database as the snapshot.
-It must publish only permitted fields, reuse canonical table schemas when they match the resolved target, and deduplicate virtual relation definitions.
-It must bound traversal during publication and isolate unresolvable edges without exposing denied targets.
-It must also distinguish traversal-capable revisions so cached flat snapshots refresh instead of hiding the new suggestions until expiry.
+The Python publisher resolves `LazyJoin`, `VirtualTable`, and table-valued `FieldTraverser` targets from the snapshot's database.
+It follows the configured person and session schemas, including person-on-events virtual fields and parent-relative traversers used by custom joins.
+It reuses a canonical table only when the resolved object and permitted field set match; other permitted helper and virtual targets receive deduplicated inline definitions.
+Warehouse tables and views require a matching exported canonical schema; the publisher never copies them into inline definitions.
+Hidden fields and denied targets do not gain traversal metadata.
+An unresolvable edge or publication budget limit omits the affected traversal, while unrelated fields remain available.
+Omissions produce one aggregate warning per catalog build with reason counts, without table names, query text, or exception traces.
 Scalar traversers need no relation annotation.
 No Python resolver chains, join SQL, credentials, or executable expressions belong in the graph.
 
+For example, with the corresponding tables and properties available to the user:
+
+| SQL                                               | Completion behavior                                                     |
+| ------------------------------------------------- | ----------------------------------------------------------------------- |
+| `SELECT e.person.\| FROM events AS e`             | Fields on the effective person target, not an assumed copy of `persons` |
+| `SELECT e.person.properties.\| FROM events AS e`  | Permitted person properties                                             |
+| `SELECT e.session.\| FROM events AS e`            | Fields on the configured session table                                  |
+| `SELECT e.group_0.properties.\| FROM events AS e` | Properties for group index 0 only                                       |
+| `SELECT e.pdi.person.\| FROM events AS e`         | Fields reached through the person distinct-ID helper                    |
+
+`CATALOG_VERSION` is the single version for catalog publication and Redis coordination.
+Revisions use `v2:<timestamp>`, and Redis coordination hashes the numeric version with the service target, team, and user.
+Django refreshes snapshots with older revision prefixes on use instead of accepting them until expiry.
+Older Django workers do not accept the new prefix; a mixed rollout can cause extra publications or Python fallback while the service is feature flagged.
+The frontend request and response contracts do not change, and the existing eligibility checks and Python fallback still apply.
+
 ## Query analysis
 
 `internal/analysis` owns parsed statements, nested scopes, table and CTE bindings, and projected fields for validation and completion.
@@ -399,9 +417,9 @@ fails startup unless dedicated signing keys are configured.
 Local and debug environments may use the service directly. Production integration remains behind a server-side
 feature flag and should progress through shadow comparison before serving editor results.
 The Go consumer accepts alias metadata, and Django always publishes resolver-confirmed warehouse aliases.
-Django refreshes cached catalogs with numeric or `legacy-v1` revisions before it uses their responses.
+Django refreshes cached catalogs without the current version prefix before it uses their responses.
 Each request attempts at most one publication and one post-publication retry; marker and lease paths add only bounded Go rechecks.
-The retry must return an alias-capable revision, but a concurrent publication for the same team and user can supersede the requested revision.
+The retry must return the current catalog version, but a concurrent publication for the same team and user can supersede the requested revision.
 If publication fails or a catalog cannot represent the resolver result, Django uses the Python autocomplete or validation path.
 Malformed HTTP payloads, incompatible revisions after refresh, and malformed autocomplete or validation mappings also use the Python path.
 Malformed service responses produce a sanitized Error Tracking event without the SQL text, response body, user context, or original exception.

frontend/src/lib/components/EmailPreviewThumbnail/EmailPreviewThumbnail.test.tsx

@@ -0,0 +1,25 @@
+import '@testing-library/jest-dom'
+
+import { render } from '@testing-library/react'
+
+import { EmailPreviewThumbnail } from './EmailPreviewThumbnail'
+
+describe('EmailPreviewThumbnail', () => {
+    // The design rides in the iframe's `srcdoc`, which the recorder serializes like any attribute.
+    it('keeps the email design out of session replay', () => {
+        const { container } = render(
+            <EmailPreviewThumbnail html="<p>Spring sale</p>" title="Spring sale preview" size="card" />
+        )
+
+        expect(container.querySelector('iframe')).toHaveClass('ph-no-capture')
+    })
+
+    // Each card frames a whole email, so without this its links are tab stops the caller never wanted.
+    it('stays out of the tab order', () => {
+        const { container } = render(
+            <EmailPreviewThumbnail html="<p><a href='/x'>Shop now</a></p>" title="Spring sale preview" size="card" />
+        )
+
+        expect(container.querySelector('iframe')).toHaveAttribute('tabindex', '-1')
+    })
+})

frontend/src/lib/components/EmailPreviewThumbnail/EmailPreviewThumbnail.tsx

@@ -0,0 +1,35 @@
+import { cn } from 'lib/utils/css-classes'
+
+// Email designs are laid out for a 600px canvas. Each size renders that canvas and scales it to its width,
+// so the thumbnail shows the whole design and not its top-left corner. Scale is width / 600.
+const SIZE_CLASSES = {
+    attachment: 'w-24 h-16 [--email-preview-scale:0.16]',
+    card: 'w-40 h-28 [--email-preview-scale:0.2667]',
+} as const
+
+export interface EmailPreviewThumbnailProps {
+    /** Self-contained email html. Rendered in a fully sandboxed iframe: no scripts, no same-origin access. */
+    html: string
+    title: string
+    size: keyof typeof SIZE_CLASSES
+    className?: string
+}
+
+/** A scaled-down, non-interactive render of an email, for composer attachments and picker cards. */
+export function EmailPreviewThumbnail({ html, title, size, className }: EmailPreviewThumbnailProps): JSX.Element {
+    return (
+        <span className={cn('block shrink-0 overflow-hidden bg-white', SIZE_CLASSES[size], className)}>
+            <iframe
+                srcDoc={html}
+                sandbox=""
+                title={title}
+                // The framed email is decorative: its own links would otherwise be tab stops with no
+                // visible focus at this scale, and `pointer-events-none` covers the mouse only.
+                tabIndex={-1}
+                // `ph-no-capture`: the recorder serializes `srcdoc`, so without it the whole design
+                // would ride into our own session recordings. Unreadable at this scale anyway.
+                className="w-[600px] h-[1000px] origin-top-left scale-(--email-preview-scale) border-0 pointer-events-none ph-no-capture"
+            />
+        </span>
+    )
+}

frontend/src/lib/constants.tsx

@@ -306,6 +306,7 @@ export const FEATURE_FLAGS = {
     DWH_POSTGRES_CDC: 'dwh-postgres-cdc', // owner: #team-warehouse-sources
     DWH_SOURCE_METRICS: 'dwh-source-metrics', // owner: #team-warehouse-sources
     EDITOR_DRAFTS: 'editor-drafts', // owner: @EDsCODE #team-data-tools
+    EMAIL_TEMPLATES_AI_FIRST_NEW: 'email-templates-ai-first-new', // owner: @mayteio #team-workflows
     EMOJI_RELATED_SEARCH: 'emoji-related-search', // owner: @pauldambra, gates the model search in `emojiSuggestionsLogic.ts` when the emoji picker finds no match
     ENDPOINTS_AI_MATERIALIZATION_FIX: 'endpoints-ai-materialization-fix', // owner: @sakce #team-data-modeling, gates the AI materialization rewrite (UI button + API action + MCP tools)
     ENGINEERING_ANALYTICS: 'engineering-analytics', // owner: #team-devex

frontend/src/scenes/max/aiFirstCreate/AiFirstCreateScene.tsx

@@ -0,0 +1,90 @@
+import { useActions, useValues } from 'kea'
+import { useEffect } from 'react'
+
+import { LemonBanner } from '@posthog/lemon-ui'
+
+import { cn } from 'lib/utils/css-classes'
+import { MAX_SIDE_PANEL_ID } from 'scenes/max/components/PhaiSidePanelChat'
+import { SuggestionCard } from 'scenes/max/components/SuggestionCard'
+
+import { runnerPanelLogic } from 'products/posthog_ai/frontend/api/logics'
+import { SidePanelRunner } from 'products/posthog_ai/frontend/api/runner'
+
+import { AiFirstHandoffLogicProps, aiFirstHandoffLogic } from './aiFirstHandoffLogic'
+
+export interface AiFirstSuggestion {
+    title: string
+    description: string
+    prompt: string
+}
+
+export interface AiFirstCreateSceneProps {
+    handoff: AiFirstHandoffLogicProps
+    /** Banner copy that says what this page trials. */
+    banner: string
+    escapeHatchLabel: string
+    onEscapeHatch: () => void
+    suggestions: AiFirstSuggestion[]
+    suggestionIcon: JSX.Element
+    /** Rendered between the composer and the suggestions while no run is active, e.g. a row of starting points. */
+    belowComposer?: React.ReactNode
+    // pinned: `data-attr` root. The page, its escape hatch (`-open-editor`) and its cards (`-suggestion`) hang off it.
+    dataAttr: string
+}
+
+/** An AI-first "new entity" page: the side panel's runner rendered full page, with a way back to the editor. */
+export function AiFirstCreateScene({
+    handoff,
+    banner,
+    escapeHatchLabel,
+    onEscapeHatch,
+    suggestions,
+    suggestionIcon,
+    belowComposer,
+    dataAttr,
+}: AiFirstCreateSceneProps): JSX.Element {
+    const { composerShown, escapeHatchClicked, fillComposer } = useActions(aiFirstHandoffLogic(handoff))
+    useEffect(() => composerShown(), [composerShown])
+    const { activeCreation } = useValues(runnerPanelLogic({ panelId: MAX_SIDE_PANEL_ID }))
+
+    return (
+        // Natural height while drafting so the cards sit under the composer; full page once a run starts.
+        <div className="flex flex-col grow min-h-0" data-attr={dataAttr}>
+            {/* The escape hatch stays up during a run, so a turn that never creates the entity has a way out. */}
+            <LemonBanner
+                type="ai"
+                className="m-2 shrink-0"
+                action={{
+                    children: escapeHatchLabel,
+                    onClick: () => {
+                        escapeHatchClicked()
+                        onEscapeHatch()
+                    },
+                    'data-attr': `${dataAttr}-open-editor`,
+                }}
+            >
+                {banner}
+            </LemonBanner>
+            <div className={cn('flex flex-col', activeCreation ? 'grow min-h-0' : 'shrink-0 mt-auto')}>
+                <SidePanelRunner panelId={MAX_SIDE_PANEL_ID} />
+            </div>
+            {!activeCreation && (
+                <div className="flex flex-col items-center gap-4 shrink-0 pb-6 mb-auto">
+                    {belowComposer}
+                    <div className="grid grid-cols-1 @min-[40rem]/main-content:grid-cols-2 gap-1 w-full max-w-2xl px-4">
+                        {suggestions.map((suggestion) => (
+                            <SuggestionCard
+                                key={suggestion.prompt}
+                                title={suggestion.title}
+                                description={suggestion.description}
+                                icon={suggestionIcon}
+                                onClick={() => fillComposer(suggestion.prompt)}
+                                data-attr={`${dataAttr}-suggestion`}
+                            />
+                        ))}
+                    </div>
+                </div>
+            )}
+        </div>
+    )
+}