Verathos v0.1.41 - Bounded Replay and Runtime Stability

Verathos v0.1.41 - Bounded Replay and Runtime Stability

Gleipnir v0.1.41 bounds long-generation hard-audit replay, strengthens
execution verification, and improves capacity-audit reliability.

What's new

• Adds nonce-selected checkpoint-window replay so hard-audit work remains
  bounded independently of a request's decode position.
• Adds runtime support for exact authenticated Qwen3.6 FP8 MLP activation
  binding; signed-profile activation remains a separate artifact rollout.
• Adds CUDA 12.8 and CUDA 13.0 native proof packages for Python 3.10--3.12.
• Extends stock installation and runtime qualification across A100, Hopper and
  Blackwell GPUs.
• Preserves proof-aware prefix reuse and concurrent serving while retaining
  authenticated hard-audit checkpoints.
• Makes Gleipnir v3 the stock miner default while retaining explicitly signed
  transition-policy support.
• Hardens concurrent CUDA-graph proof capture and bounds final-state hashing at
  advertised serving capacity without changing proof commitments.
• Supports one-token completions in GDN hard audits by binding the authenticated
  prompt boundary when no forwarded decode row exists.
• Binds capacity-audit receipt chronology at HTTP ingress and isolates chain
  observation from receipt processing, preventing validator queue pressure from
  misclassifying timely commitments.
• Prevents owner canaries and timed capacity audits from being scheduled onto
  the same endpoint, and reconciles authenticated late overlap receipts without
  penalizing honest serving.
• Uses a lower-heavy, signed owner-canary context distribution to reduce routine
  audit load while preserving unpredictable full-range coverage.
• Prepares verified runtime support for the official
  Qwen/Qwen3.8-27B-FP8 checkpoint, including a bounded quality premium over
  Qwen3.6. Model registration and authenticated artifact activation are a
  separate later rollout and are not enabled by this release.

Versions and updating

• Miner: 0.1.41
• Validator: 0.1.41
• Specification: 0.1.41

Miners and validators using automatic updates will adopt the release at a safe
idle boundary. Operators updating manually should pull the release and rerun
the stock setup command; no custom runtime flags are required.

The existing supported-model set remains active and compatible throughout this
release.