Repository navigation
Default Flash Next to Red Hat NVFP4 and advertise recipe capabilities - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default non-abliterated
qwen3.8:flash-next/qwen3.8:flash-next-nvfp4aliases now select RedHatAI's immutable NVFP4 checkpoint. Recipes also declare client capabilities explicitly, so a healthy qualified generation advertises its reasoning levels, default effort, summaries, tools, parallel tools and verbosity through the control API and public/v1/models. Codex consumes that contract instead of blanket feature defaults: the Red Hat model exposes efforts throughxhigh, defaults toxhigh, and streams reasoning summaries without workaround flags. Explicit user overrides still win.Capability declarations travel with the exact generation's verified gateway profile through executor IPC and reconciliation. Warming, unhealthy, mismatched and legacy generations remain conservative. Recipe validation rejects inconsistent declarations; a bounded startup reasoning probe requires both reasoning and a completed answer before publication. Legacy profile serialization preserves protected identities and historical evidence.
The Red Hat engine uses compressed-tensors W4A4 experts and disk-backed BF16 PLE with the owned, digest-pinned B12X runtime. It preserves 262,144-token context, FP8 KV, MTP4 and vision. The image normalizes the checkpoint's serialized attention-layer label for the pinned runtime while retaining QSA/indexer settings. Hash-guarded patches and real checkpoint/PLE reader tests cover compatibility, reads, strides, BF16 expansion, concurrency and failure cleanup. Existing RadixArk and separately selected abliterated recipes remain available.
Interrupted downloads credit only allocated bytes in safe managed partial files when planning additional storage. Transfer verification, temporary budgets and the 100 GiB disk reserve remain enforced. This PR also records the previously deployed abliterated recipe, updates zstd for the dependency audit and installs CPU reader test dependencies in CI.
Long coding sessions also exposed a transport failure during automatic compaction: the adapter's 1,800-second HTTP deadline was silently shortened by reqwest's 30-second Linux TCP unacknowledged-data timeout. Set that TCP deadline explicitly to the same finite inference budget. Translated Responses, Chat and Anthropic streams emit ten-second SSE comment heartbeats through the adapter during quiet prefill, without creating output events or token usage. Redacted diagnostics distinguish request/body failures and timeout classification. Engine deadlines and cancellation remain enforced.
Validation:
make lint,make test(1,101 passed),make test-client(186 passed),make auditmake web-test-browser, strict Rust documentation and native Codex launcher regressionxhigh; effectivexhigh/ summaryautodespite a stalenonepreference; no coding thread createdxhighand reasoning summaries: tool call and stateless continuation completed; zero tools executedThe Red Hat snapshot is approximately 186 GB. Disk-backed PLE avoids allocating its full BF16 embedding table in unified memory. Memory/disk admission reserves and the bounded startup deadline are unchanged. Deployment preserved existing local launcher permission behavior through a private build overlay; unrelated workspace edits are excluded from this PR.