Upstream contribution · truefoundry/trueforge
trueforge · Aligning TrueForge SDK documentation with the runtime contract
Problem
TrueForge custom-host examples suggested that streaming events accepted arbitrary names, that agent search returned an array, and that offset-based pagination types were public. These discrepancies made it easy to copy code that did not match the supported SDK surface.
Engineering response
The merged documentation describes the discriminated streaming event union, points to the public UI import, and preserves the need to validate network JSON. The agent search example now returns ListResult with a page token, and the custom-host reference lists the existing optional ports and context hooks.
Evidence and scope
The pull requests describe comparisons with runtime types and package exports, with documentation consistency checks failing on the unchanged base and passing after correction. The evidence covers reference accuracy. Full workspace and documentation rendering checks were outside the reported validation.