cloud: at the @objectstack/core bump that carries #26078, check the three AI entry points pass the organization id as organizationId (ResolveLocalizationInput.tenantId is retired) #26110

Filed by the domain:server seat 2 on the maintainer's direct word for items that must go to cloud, verbatim: 「需要转给 cloud的，应该立 cloud 车道卡」. Parked here with domain:cloud + status:parked until the cloud PM moves it, as pm-dispatch's domain:cloud row says. ⛔ Not a claim; this repository does not dispatch it.

Origin: #25555, fixed by PR #26078 (merged as 65145d34fb). ResolveLocalizationInput.tenantId in @objectstack/core is renamed to organizationId, and the old key is retired at once with no alias. The changeset carries a BREAKING banner and ADR-0087 runtime-export-retired @objectstack/core#ResolveLocalizationInput.tenantId.

Why cloud must check it: objectstack-ai/cloud calls resolveLocalizationContext from three AI entry points: agent-routes, ai-routes /chat and tool-routes (cloud#3150 fixed them to pass the organization id). After the bump:

• an object-literal call site that still spells tenantId fails loudly at compile time (TS2353), which is the safe case;
• a call site that passes a wider-typed variable, a spread, or a wrapper that still spells tenantId compiles, drops the organization id, and resolves UTC again. That is the same silent defect core: ResolveLocalizationInput.tenantId takes an organization id but does not say so — cloud passed the environment id for months and every hosted environment resolved UTC; rename or brand it #25555 was filed for.

Done when: at the cloud PR that bumps @objectstack/core to the release carrying PR #26078, each of the three entry points passes the organization id under organizationId (read at the call site, not inferred from a green build), and the hosted-kernel e2e that cloud#3150 added still resolves the organization's timezone (for example Asia/Shanghai), not UTC.

Blocked-by: the @objectstack/core release that carries PR #26078.

Generated by Claude Code