[truefoundry-saas]

Automated cherry-pick for release request 735ce6c7-5f21-475b-9b37-e1109508fa67.

Source PRs (merged to main):

• chore: Add PostHog envs in Dockerfile, add trueforge prefix and include tenant id #1036
• Wire posthog creds during build #1059
• feat: fine-grained tool streaming via TFY beta header #1088

Warning

This PR does not contain the fix yet. The cherry-pick conflicted, so
automation stopped at the first conflicting commit and left the rest out.
GitHub therefore shows this PR as mergeable, with no conflict to resolve —
it currently carries no changes at all (an empty placeholder commit).
Paste the prompt below into any coding agent that has this repository open.
It checks out this branch, applies the missing commits, and pushes.
Do not merge the PR. The release request checks every commit within a few
minutes (or use "Sync status" on it). The PR is merged when the request is
approved — or, if it is already approved, when a QA member or engineering
admin uses "Retry merge".

Agent prompt — copy from here:

Apply the missing cherry-pick commits onto this pull request. Work only in this repository. Do not merge the pull request and do not open a new one.

Repository: truefoundry/trueforge
Branch to check out and push to: cherry-pick/735ce6c7-5f21-475b-9b37-e1109508fa67/release-v0.179.3
Base branch (do not commit onto this directly): release-v0.179.3
The first commit conflicted in: packages/frontend/src/authSession.ts.

Commits still missing, in this order:
1. 7f2be59e6e8beaa91d67aa9e6338203a519beed7
2. 69f099012ee004b79c4bd9da0e7e5725b804cdc0
3. 248e7683b4d3f96b5fd0bb54e875989ad1c148bc

Steps:
1. Fetch and check out the branch above.
2. For each missing commit, in the order listed, run `git cherry-pick -x <sha>`. Keep the `-x`: the release request confirms a commit from the "cherry picked from" line it writes.
3. If a cherry-pick conflicts, resolve it so that commit's changes land on this branch, then `git add` the resolved files and `git cherry-pick --continue`. Do not skip a commit and do not abort the sequence.
4. Push to the same branch. This pull request updates on its own.
5. Stop. Do not merge the pull request.

Conflicting file(s):

• packages/frontend/src/authSession.ts

Commits still to apply (starting at the conflict):

• 7f2be59e6e8beaa91d67aa9e6338203a519beed7
• 69f099012ee004b79c4bd9da0e7e5725b804cdc0
• 248e7683b4d3f96b5fd0bb54e875989ad1c148bc

Do not merge manually — this PR is merged automatically when the release request is approved. If you do merge it yourself, use "Sync status" on the request so it stops showing as pending.

---

Note

Medium Risk
Renaming analytics events is a breaking contract for hosts on old names; LLM header/tool-streaming and stricter tool-arg parsing change agent behavior on incomplete streamed JSON.

Overview
Analytics & product telemetry: Public AnalyticsEvents strings are renamed with a trueforge. prefix so host sinks like PostHog can namespace TrueForge events. The harness app wires PostHog at build time (VITE_POSTHOG_* in Docker and release workflow) and only attaches hostAnalytics after auth, enriching each capture with tenant from the session.

Agent runtime (LLM + tools): TrueFoundry OpenAI-compatible calls add the anthropic-beta: fine-grained-tool-streaming-2025-05-14 header; Anthropic provider options always set toolStreaming: true. Tool execution parses function.arguments before callTool—invalid or non-object JSON returns a structured parse error without invoking the tool (new test coverage).

OpenAPI/docs version bumps to 0.179.2; patch changesets document the UI and core package bumps.

^{Reviewed by Cursor Bugbot for commit 00ad3c2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

🦋 Changeset detected

Latest commit: 00ad3c2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@truefoundry/trueforge-ui	Patch
@truefoundry/trueforge-core	Patch
@truefoundry/trueforge	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR