chore: reassign product owners after team split

[joshsny]

Problem

PostHog/posthog.com#17202 updates feature ownership to reflect a team change: posthog-ai is being split into signals and posthog-code. The products/*/product.yaml owners: fields in this repo (which drive automatic reviewer assignment via .github/scripts/assign-reviewers.js) still point at the retired team-posthog-ai, so PRs touching these products would be routed to the wrong team.

Changes

Reassign every product.yaml still owned by team-posthog-ai:

Product	Old owner	New owner	Source
slack_app	team-posthog-ai	team-signals	"Slack app" → signals
mcp_store	team-posthog-ai	team-signals	"MCP server" → signals
posthog_ai	team-posthog-ai	team-signals	"PostHog AI platform" → signals
tasks	team-posthog-ai	team-posthog-code	"Background agents" → "Cloud agents" → posthog-code
mcp_analytics	team-posthog-ai	team-signals	Not a posthog.com feature; grouped with the other MCP product since its owner team is retired

After this change no product.yaml references team-posthog-ai.

How did you test this code?

I'm an agent (PostHog Code). No automated tests were run locally. The repo's owner-lint (hogli product:lint:owners, gated on products/*/product.yaml changes) validates the new owner slugs against PostHog org teams in CI — team-signals is already used by signals/tracing, and team-posthog-code will be validated there.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

Docs update

No docs impact — this only changes reviewer-routing metadata.

🤖 Agent context

Authored by PostHog Code at Josh Snyder's request, following Julian's note to adjust the product.yamls to the right GitHub teams after the posthog.com feature-ownership PR.

The mapping was derived from the diff of PostHog/posthog.com#17202 (src/hooks/useFeatureOwnership.tsx), translating each posthog.com owner slug to the repo's team-<slug> convention. mcp_analytics was the one judgement call: it has no matching posthog.com feature, but since team-posthog-ai is being fully retired it can't stay, so it was grouped with the other MCP product under team-signals. Flag if it should instead go to team-posthog-code or elsewhere.

---

Created with PostHog Code

[github-actions]

Hey @joshsny! 👋

It looks like your git author email on this PR isn't your @posthog.com address (joshua@timenavi.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

• Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
• Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

[greptile-apps]

_{Reviews (1): Last reviewed commit: "chore: reassign product owners after tea..." | Re-trigger Greptile}

[Copilot]

Pull request overview

This PR updates products/*/product.yaml ownership metadata to reflect the split of the retired team-posthog-ai into team-signals and team-posthog-code, ensuring automatic reviewer assignment routes to the correct teams.

Changes:

• Reassigned Tasks product ownership to team-posthog-code.
• Reassigned Slack app, PostHog AI, MCP servers, and MCP analytics product ownership to team-signals.
• Removed remaining team-posthog-ai references from products/*/product.yaml.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
products/tasks/product.yaml	Updates product owners to team-posthog-code for Tasks.
products/slack_app/product.yaml	Updates product owners to team-signals for Slack app.
products/posthog_ai/product.yaml	Updates product owners to team-signals for PostHog AI.
products/mcp_store/product.yaml	Updates product owners to team-signals for MCP servers.
products/mcp_analytics/product.yaml	Updates product owners to team-signals for MCP analytics.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-06-03 12:03 UTC	Run
prod-us	✅ Deployed	2026-06-03 12:21 UTC	Run
prod-eu	✅ Deployed	2026-06-03 12:22 UTC	Run