Skip to content

koinon 26.11.10

Keep regional preferences personal

Your account now includes language and region, calendar, time format, time zone and response language. New browser profiles can use the device's reported regional settings once. Existing profiles retain their saved choices, including explicit English and UTC settings. Corporate identity synchronization does not overwrite personal regional preferences.

The profile API and Python, TypeScript and Java 21+ SDKs support both explicit updates and conditional first-use initialization. Concurrent initialization cannot replace a saved choice. See the profile guide for the controls, examples and precedence rules.

Select structured evidence correctly

Structured answers select recorded cell and derived values through their evidence identifiers. Those values are no longer treated as document quotations. New model answer plans must specify the response language; historical evidence records remain readable. A bounded repair can correct an invalid selection without weakening source or lineage validation.

Product help also supports questions combining the assistant's identity and capabilities. The streaming transport has additional HTTP regression coverage for incremental answer events and completed audit information.

Preserve the shared email template

The primary link markup matches the recipient-confirmed template, including its visible destination address. Welcome messages, invitations, security notices, access changes and summaries share that template. HTML and plain-text alternatives retain branding and Foundation attribution.

A received diagnostic verifies one message, not every future welcome or summary. Confirm the intended message at the recipient mailbox after changing a deployment. Previously sealed messages and welcome history are preserved; upgrading does not resend them. See communications.

Update the installation

Use 26.11.10 across runtime packages, SDKs and interface assets, with pyfly 26.10.32. Before starting the updated application, apply native migration koinon_0042_profile_preferences through the separate migration process. This adds an initialization marker without changing saved preferences. An image-only update is insufficient.

Back up the database and rehearse the exact upgrade on a restored copy. Preserve source versions, original files, conversation evidence and email delivery history. Follow schema and role changes, then verify API and worker readiness, existing and new profiles, knowledge ingestion, an evidence-backed conversation and the configured email flow.