v0.3.0

Fluent v0.3.0

Fluent v0.3.0 adds durable Slack collaboration and broadens recovery for
long-running, scheduler-owned work. It also makes provider failures, candidate
rewrites, and host-specific test evidence safer to diagnose and resume.

What changed

• Slack Socket Mode can now carry a project-bound Fluent thread without a
  public endpoint. Threads preserve planning context, approvals, provider
  switches, Work status, reviewable candidates, and recovery actions. A local
  runner keeps Slack credentials in the macOS Keychain and enforces configured
  project, checkout, participant, and approver boundaries.
• Slack can enable approved existing checkouts, start planning, deliver Work
  transitions, and connect ready candidates to GitHub review. Reconnects,
  duplicate events, delayed provider replies, and interrupted deliveries are
  reconciled through durable identities.
• Scheduler-owned Work now has stronger service registration, nested-sandbox
  handling, fair provider admission, and explicit recovery for provider
  outages, canceled tasks, and stale dispatches. Scheduler status identifies
  the exact Fluent build that owns a project.
• Candidate recovery now covers Tester harness repairs, host-specific evidence,
  failed-command rechecks, candidate ancestry repairs, audited commit-message
  rewrites, and planning-reference or Approach revisions. These paths preserve
  candidate provenance and reject ordinary drift instead of silently combining
  evidence from different commits.
• Review and Tester settlement now waits for parallel reviewers, preserves
  late or superseded task output, reuses immutable baseline results, and avoids
  terminalizing an Attempt while authorized work is still settling.
• Codex and Claude provider failures now distinguish authentication, host
  sandbox, capacity, argument, and response-liveness failures. Bounded
  continuation and explicit handoffs keep transient provider problems from
  losing the current Attempt.
• Commit validation is clearer and more targeted. Prospective commit-message
  policy checks, executable command-shaped behavior references, isolated Git
  inspection, and bounded candidate gates catch malformed or drifted output
  before reviewers run.
• The release documentation and project Expertise now describe the Slack
  runner, recovery boundaries, scheduler ownership, and durable external
  effects. The release test harness also tracks the current transcript-pump
  schema.

Installation and upgrade

Run fluent update to install the latest binary, or follow the release
installation instructions in the repository. Verify the installed build with:

fluent version

The reported version should start with fluent 0.3.0.

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

Existing Work Items and Attempts retain their durable lifecycle state. Resume a
paused Attempt with the exact command shown by fluent status; scheduler-owned
Work should return through fluent queue resume rather than starting a new
Attempt.

For Slack setup, see docs/slack-runner.md.
Fluent v0.3.0 supports the verified local macOS workflow. Fargate execution is
not part of this release's readiness claim.