v0.1.5

Morphz Runtime v0.1.5

This stable release reunifies the published 0.1.4 baseline, GitHub main,
previously local main work, and the verified post-release development fixes.
The 0.1.4 tag and its published assets remain unchanged.

Model and Context controls

• Support xhigh reasoning consistently in Runtime, Dashboard and Desktop,
  showing only the levels declared supported by the selected model. The offline
  Harness tool schema is generated from that same current Host definition.
• Align input admission with the selected model's total Context capacity and
  output allowance. Desktop exposes current usage, reserved output capacity
  and the editable maximum through its compact Context control.
• Preserve the existing account and model authorization boundaries when
  selecting and resuming work.

Conversation and execution fixes

• Preserve ordinary progress explanations accompanying no_reply while its
  separately validated control determines silence or finite waiting. Conflicting
  work/control calls and waits without a live event still fail validation.
• Open ordinary Thread and Objective supplements directly, including targets
  outside the currently loaded history; isolate execution-control errors from
  the surrounding toolbar.
• Bring pending approvals to their authorized outer view, including scheduled
  roots and related work, and start scoped authorization lifetime at the actual
  approval decision.
• Complete Desktop execution controls and preserve exact schedule and Thread
  identities across narrow layouts and control menus.
• Keep Runtime read diagnostics and current activity independent from failed or
  retained historical pages; retain the bounded, incremental read behavior.

Reliability and release process

• Preserve the local causal-wake synchronization correction and the verified
  Provider-wait recovery/cancellation contract. A failed physical model attempt
  is not confused with a terminal logical Thread, and partial output is not
  promoted to a completed result.
• Preserve native Context maintenance before a Runtime-owned Harness entry
  when pressure is critical, then resume that exact bound entry. The model relay
  retains only cognitive maintenance and applicable Objective control; physical
  work remains inside the entry, and child infer tool scopes remain unchanged.
• Give Runtime publications, including replies, Provider recovery wakes, progress
  and model-state transitions, collision-resistant Event identities even within
  the same clock tick. Persistence retries reuse
  the same immutable Event; later notices remain distinct and cannot replace an
  already committed outcome through the Activation's existing duplicate fence.
• Require three full 16-Thread HTTP Provider outage/recovery/cancellation passes
  on the optimized binary in CI, retaining failed receipts and the original
  bounded deadlines.
• Integrate the existing CI, dependency-security and regression fixes without
  reducing their semantic coverage or acceptance requirements. Remove an exact
  duplicate test introduced by the merge so the browser inventory can collect.
• Keep PostgreSQL 16 test jobs on their tested Ubuntu 24.04 image instead of the
  moving latest alias. Drive the background-checkpoint unit fixture through
  explicit persisted claims rather than a fragile wall-clock race.
• Keep release-critical sandbox tests on that same Ubuntu 24.04/AppArmor 4
  acceptance baseline as the complete CI native gates. Reject a moving runner
  alias or disabled native coverage in the release configuration checks.
• Give Context encoding fixtures an independent civil clock while retaining
  exact byte comparisons and explicit second/day rollover checks. Live Context
  rendering continues to sample the real host clock on every render.
• Update the Rust Markdown parser to the patched 0.13 series; retain matching
  nested locks and third-party license records.
• Update the website renderer and its font/archive dependency to patched
  versions while keeping the existing React version. Node HTML checks use the
  renderer's official restricted prerender loader; Worker bindings remain
  unavailable to these checks.
• Use the official patched minimatch 11.0.1 matcher in Dashboard and website
  build tools, with a documented export adapter for older lint plugins. Matching
  code remains upstream; both audit gates and complete lint/build checks remain.
• Seal unsigned code only in newly copied macOS development bundles, preserving
  valid vendor signatures and strict rejection of changed installed bundles.
  Native Notes checks use their real center without starting an unused peer Web
  application, with five consecutive Intel regression passes required by CI.
• Release paired reference, creation and annotation browser contexts with their
  individual test scopes instead of retaining closed pages or all renderers
  until the entire parent completes. Require five complete Intel mounted-view
  regression passes before publication; retain all layout/identity assertions
  and the original five- and ten-second operation limits.
• Observe document protocol acknowledgments independently of browser paint
  scheduling, with a real SDK/SQL counterfactual for suppressed rendering and
  the same five-second wall-clock deadline.
• Cut stable tags from integrated main. Pre-release tags retain release-branch
  isolation. Publication still requires successful complete CI for the exact
  release commit and verification of the complete immutable asset inventory.

Upgrade

Use the normal installer or the native Runtime bundle for your platform. Keep
your existing data and configuration; no profile reset or database deletion is
part of this release. Desktop remains a separately developed application, not
an additional binary distribution promised by this Runtime release.

Runtime validation establishes execution behavior. It does not constitute
domain acceptance of any scientific or business task run through Morphz.