r34 confirmed assistant consolidation — 2026-10-16

Baseline full release SHA-256: f03cd165a2b9ab4e4406d66d150df3c33382b96ea51bfaff174baa682b48627c.

This release merges the approved Assistant Recovery, Assistant Loading and Assistant Opening patches into the full standalone and SaaS source. It retains r34. The proposed Orbit Viewer Header patch is excluded; the established hosted Orbit Viewer navigation remains unchanged.

Consolidated changes

• Publish immutable assistant source before owner-session transactions can refer to it, rather than holding an owner lease row lock during long source uploads. Native HF startup publishes the installed source before admitting HTTP traffic.
• Reuse verified, committed source descriptors for unchanged files while retaining ownership, encryption, hashes, lifecycle references and quota checks. Avoid rewriting unchanged reference indexes inside private-state reads.
• Read navigation metadata and the selected conversation in one workspace request. Lists use small summaries; selected details retain their evidence index. Saved conversations and permissions are read afresh on each request.
• Ordinary assistant opening selects saved metadata without silently capturing a completed run. Open selected run explicitly starts evidence capture. Reopening workflow authoring selects an existing conversation; New authoring conversation explicitly starts another. Pending mutations remain protected against replay, and loading failures release controls with a usable error.
• Read shared encrypted artifact packs once within a bounded capture or companion request. Keep individual file, attempt, owner, size and hash checks intact.
• Retry an immutable object read once after an allowlisted transport failure only when that first failure happens within two seconds. Failed streams are closed; the original network timeouts and integrity checks remain. This condition is not a two-second overall network deadline. Writes, mutable heads and ownership operations do not gain automatic replay.
• Keep saved BYOK keys private and permit unchanged public settings without requiring a replacement key. Remove repetitive untested-provider display text while retaining machine-readable verification state and genuine errors. Saving credentials still does not establish provider access.

The shared service and UI changes are used by standalone and SaaS. Native publication, durable-read recovery and source-descriptor reuse apply to the HF adapter. The HF bundle generator preserves the approved two-hour startup-health window. That window is an upper limit, not an expected startup duration or a requirement for users to wait two hours.

No database migration or stored-data format conversion is introduced by these assistant changes. Scientific equations, run configuration, provider permissions, BYOS policy and execution isolation remain as before. Request-local pack reuse and immutable-source descriptor reuse do not cache simulation executions or reuse previous results to satisfy a new simulation.

Live observation and validation scope

On 2026-10-16 the operator reported that the excessive assistant loading delay was resolved with the Recovery → Loading → Opening patch chain installed. This is a user-reported acceptance observation, not an independently timed latency result, production capacity measurement or new-full-release deployment qualification.

Current targeted local commands and their exact results are recorded in validation_r34_assistant_consolidation/test_execution.json; the command plan is release_tools/assistant_consolidation_checks.json. Earlier patch evidence is retained under validation_r34_assistant_consolidation/patch_evidence/ as historical material. Its overlapping reruns are not added to the current test totals or presented as additional distinct cases. Original release validation and benchmark records retain their original bytes.

This consolidation does not rerun the full scientific or regression campaign. Local fixtures do not qualify live AI services, production PostgreSQL concurrency, native Windows execution, live HF throughput or external scientific replication. Pending qualification is explicit in the current registry and release ledger.

Release integrity and deployment

The schema-33 registries retain the schema-32 workflow-reliability registries as their historical predecessor. Every original archive member is preserved. The previous bytes of changed members are retained under the new validation folder, and current source hashes, full package checksums and archive SHA-256 are rebuilt from the consolidated tree. Byte checks establish integrity, not authenticity or scientific correctness.

Verify the extracted full release:

python release_tools/package_r34_assistant_consolidation.py verify --package

For an existing HF deployment already using the three accepted assistant patches, this archive consolidates those fixes for distribution. Creating the archive does not change the live service or require reinstalling the same patches. A later full-release redeployment uses a newly generated matching controller and private runner bundle; do not reuse old runner hashes as new-release hashes. Follow the native upgrade guide, retain a verified private backup and current settings, and confirm application startup before checking the assistant. Do not apply the earlier assistant patch ZIPs on top of this consolidated release.