video1.0<iframe src="https://www.loom.com/embed/cbffbfccbb384220bfe0a8aa80981b9d" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/cbffbfccbb384220bfe0a8aa80981b9d-d8b84326bc17d9ef.gif130.847This Loom explains the upsert root code used to handle upserting internal content cross-app data. It takes the space ID from the route and assumes the request.json is standalone cross-app, with a standalone type created because many parameters are optional in inline but mandatory in standalone. The author postponed the z-validator, applied a constraint inverter, and then performed the upsert. In the diff, they describe changes to require cross-app base fields, infer the inline variant, and add a new converter plus helper functions to supply either local or database IDs while setting the other related fields to null, including the inline parameter.