SwiftAgent 1.0.0-rc.1

SwiftAgent 1.0.0-rc.1 Release Notes

Status: Published as GitHub Pre-release 1.0.0-rc.1.
Last verified: 2026-09-19

Highlights

• Provider-neutral ModelProvider contract and normalized model event stream.
• Typed AgentTool API with schema validation and controlled type erasure.
• Multi-Run AgentSession conversation continuity.
• Durable AgentJournal checkpoints and crash-safe recovery.
• Evidence prerequisites, independent host authorization, and Receipt-backed
  mutation settlement.
• Stable mutation idempotency across Host retries, Sessions, restart, compaction,
  and provider fallback.
• Recoverable, model-visible failures for explicitly opted-in read-only tools.
• Provider routing and fallback without replaying mutation side effects.
• macOS, iOS, and Linux Core support plus an optional Apple Foundation Models adapter.

Frozen Contracts

• wait() resolves at logical Run termination.
• waitForDrain() waits for provider/tool physical drain and Session identity release.
• Crash recovery never automatically replays an uncertain mutation.
• Cross-Run mutation retry safety requires a stable non-nil operationID, the
  same tool, canonical semantic arguments, and a shared durable AgentJournal.
• Conversation memory is not Evidence. Model output is not authorization.
• An executor return is not durable mutation completion until Receipt validation
  and journal settlement succeed.
• A recoverable read error is not a runtime or safety error; mutation,
  authorization, Evidence, receipt, journal, timeout, and cancellation failures
  remain fail-closed.

Known Limitations

• A first-class queued follow-up while another Run is active is not included.
  Hosts can await the active Run and submit the next turn explicitly (SAI-045).
• Settled and aborted mutation tombstones are retained indefinitely by default.
  A future explicit retention policy may trade storage for deduplication horizon
  without changing the current correctness-first default (SAI-046).
• Immutable v1/v2 journal byte fixtures produced by the original historical
  encoders are not checked in. Current migration regressions cover the accepted
  legacy vocabulary; immutable provenance fixtures remain a P3 follow-up (SAI-050).

Verification Scope

The RC gate requires clean-clone macOS, Linux, Apple adapter, ExternalClient,
architecture, journal migration, mutation, concurrency, and hosted CI evidence.
The public release seal also requires a credential-isolated anonymous HTTPS
clone and a no-cache SwiftPM consumer build from the documented repository URL.
Live cloud and Apple model calls remain operator opt-ins and are not required
for ordinary CI.

Published as annotated tag and GitHub Pre-release 1.0.0-rc.1.