zakura-core/zakura v1.4.0-rc1 on GitHub

Zakura now advertises prepared mined blocks after expected-work validation and state admission
(#748).
Zakura now reuses prepared mining candidates through workid
(#748).

Updated the Zakura Common (zakura-core/common) crates from 1.1.0 to
1.2.0
(#925).
Shortened the end-of-support window to 22 days so v1.4.0-rc1 halts at block
3,504,731 — the same halt block and date (~2026-10-03) as v1.4.0-rc0 and
v1.3.2
(#927).

Zakura withdraws rejected mining templates, stops affected internal mining work, and
validates empty-template recovery before returning a replacement
(#748).
Zakura bounds mined submissions and contextual writes, and returns inconclusive when a mined
block must wait for its parent or verification capacity
(#748).
Zakura blocks optimistic relay while earlier contextual writes or operator changes can move
the selected tip (#748).
Zakura avoids duplicate all-peer inventory delivery
(#748).
Header sync now repairs contiguous ranges of missing VCT roots in one
request. Checkpoint commits now resume immediately after a header-chain
commit instead of polling every 500 ms. A parked checkpoint also clears a
resource-stall alarm itself, so it can no longer wait for an insertion that
the alarm would refuse. These changes improve checkpoint catch-up for
retained states with large missing-root gaps
(#893).
The stalled-height diagnostic now measures the parked block's complete wait,
so a changing missing height no longer postpones the operator error or clears
the gauge before the block commits
(#893).
A repair supplier that refuses or withholds its response no longer ends the
scheduling round for the remaining candidates, and an unresponsive supplier
is now charged like any other timed-out peer
(#893).
Added a check on the combined chain value-pool balance as defence in depth
(#911).

This release also ships the latest verified Mainnet release state (checkpoints,
VCT frontier, and subtree roots up to height 3474810)
(#926).