v0.5.0

Fluent v0.5.0

Fluent v0.5.0 tightens the evidence used to decide whether a candidate can
advance, and makes interrupted Writer and recovery paths more reliable. These
changes follow the published v0.4.0 release.

What changed

• Verification now tracks each required command and its accepted proof through
  correction, targeted review, and final Tester runs. A failed command sends a
  candidate back for source correction only when the failure establishes a
  defect; missing prerequisites and unexplained failures pause for diagnosis.
  Host-provided proof must still match the current candidate, command, inputs,
  and freshness rules before it can satisfy a requirement.
• Rust library Test: references can name tests in a package-root library or a
  selected member of a virtual Cargo workspace. Fluent resolves the package,
  library target, and committed sources, then requires matching native test
  results. Ambiguous targets, dirty sources, and results from another library
  do not satisfy the reference.
• Writer handoffs assess the current completion matrix and candidate gate before
  assigning corrective work. The Writer receives the pending obligations and a
  compact view of current verification; malformed matrix state has an explicit
  recovery path. Candidate files remain confined to the Writer's checkout.
• Recovery commands preserve their original evidence and authorization across
  retries. Approach revisions at a failed-review round cap require a matching
  approved extension. Interrupted output-free Writer restoration and combined
  recovery paths validate the saved candidate and model state before changing
  Git or Work records.
• Review coverage and release test fixtures now check the full Writer history
  and supervise nested Fluent and provider processes through cleanup. This
  reduces the chance that stale review evidence or a surviving fixture process
  is mistaken for a completed gate.

Installation and upgrade

If a scheduler is running, let its current Work finish and stop it before
installing the new binary:

fluent scheduler status
fluent scheduler stop
fluent update
fluent version
fluent scheduler run

The reported version should start with fluent 0.5.0 and include the build
commit. Without a running scheduler, use fluent update followed by
fluent version.

Fluent v0.5.0 reads v0.4.0 Work Items. Existing Work Items and Attempts retain
their durable lifecycle state; resume paused work with the command shown by
fluent status. Scheduler-owned Work should return through fluent queue resume.

After v0.5.0 mutates a Work Item, use v0.5.0 or a compatible newer binary for
that item. The writer-version gate prevents older binaries from rewriting newer
state. To explicitly upgrade stored Work Items, run
fluent work-item upgrade <work-item-id>, or omit the ID to process all items.

Fluent v0.5.0 supports the verified local macOS workflow. Fargate execution is
outside this release's readiness claim.