koinon 26.11.5

Retain and reconcile uploaded originals

Migration koinon_0040_bulk_pinned allows a Library upload to record its first validated object reference. It verifies the admitted original's key, size and hash, then prevents that reference from being replaced or removed. Existing upload identities, quotas, writer leases and retained receipts remain protected. Published migrations and previously stored originals are unchanged.

If a previous upload stored its bytes but did not confirm staging, preserve the batch and its original. Apply and verify the migration, refresh the batch's current state, and explicitly reconcile that same upload. Do not upload the file again or reset its receipt. Follow durable bulk recovery.

Library now includes Retained uploads so an authorized user can reopen a saved batch after signing in, inspect its current revision and explicitly review recovery of the same original. The interface keeps pending and unknown writes visible and does not automatically replay them. See bulk intake.

Clearer index and resource administration

The Storage & indexing panel guides authorized administrators through reviewing an embedding plan, building a separate target, checking its physical index and explicitly activating it. Progress and recovery remain attached to the tracked operation, and the interface focuses the review when that work completes. Read knowledge index management.

Library resource details now use the available work area. Settings keeps the product's model-provider configuration and removes the separate framework provider inventory from deployment setup.

Reliable first chat reads on PostgreSQL

The first queued message page no longer asks PostgreSQL to compare JSON application metadata for equality. Current application, token and membership restrictions still apply when resolving remembered authority. This fixes the initial conversation read without broadening access.

Visible email destinations

Branded HTML email links display their full destination URLs. The existing template, inline branding, attribution, plain-text alternative and same-origin restrictions remain in place. This change does not rewrite previously prepared messages, retry unknown deliveries or establish a general rule about mailbox filtering.

Package and deployment compatibility

Use version 26.11.5 consistently across the runtime packages, SDKs and interface assets. PyFly remains on 26.10.32. The deployment source bundle carries the operator scripts and migration history; the runtime wheel does not replace that bundle. See installation.

Source and installed-package tests, hosted CI, published asset verification and live ingestion are separate checks. A passing local recovery test does not establish that a deployed batch has been reconciled, indexed or used successfully in an answer.