Releases

The tagged coordinated AppSurface release represented by this documentation tree.

Coordinated AppSurface release 0.1.0, tagged on 2026-06-27.

Coordinated AppSurface release 0.2.0-preview.1, tagged on 2026-06-28.

Coordinated AppSurface release 0.2.0-preview.2, tagged on 2026-07-02.

Coordinated AppSurface release 0.2.0-preview.3, tagged on 2026-07-17.

Coordinated AppSurface release 0.2.0-preview.4, tagged on 2026-07-18.

Coordinated AppSurface release 0.2.0-preview.5, tagged on 2026-07-31.

Coordinated AppSurface release 0.2.0-preview.6, prepared on 2026-08-11 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.7, prepared on 2026-08-15 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.8, prepared on 2026-08-22 for maintainer review.

Start with the public release hub, then drill into the current v0.2.0 preview, the canonical v0.1.0 archive, unreleased proof, changelog, and upgrade policy.

Maintainer guide for frozen tree-local coordinated package release pointers.

Living proof artifact for the next coordinated AppSurface release. This page is intentionally provisional until a version is tagged.

Compact ledger for coordinated AppSurface releases across packages, CLI tooling, examples, and docs-facing behavior.

Stability and migration contract for AppSurface before the first tagged release.

Maintainer workflow for turning the unreleased proof artifact into a consumer-led tagged release note.

Markdown callouts and contextual two-to-four-path tabs without requiring raw HTML or a client-only component. Pages keep a complete source-ordered baseline for static export and no-JavaScript readers; the optional accessible tabs enhancement preserves fragments, browser history, and Turbo-frame navigation. Invalid directives remain visible as literal source and appear in harvest health with stable remediation diagnostics, so documentation repositories can adopt the feature incrementally.

now exposes an AppHost-only, strictly ordered `RealmReady()` and `WithLocalSeed(...)` lifecycle for finite consumer-owned local projects. It keeps Keycloak Admin API clients, credentials, retries, mutation policy, and idempotent application state in the consumer worker while AppSurface supplies only the baseline proof, dependency graph, typed secret-reference validation, and redacted diagnostics.

now lets `ProviderKeyed` Work opt into a closed executor result: success, a proven pre-effect retry, terminal application failure, or an explicitly ambiguous external outcome. Existing `IDurableWorkerExecutor<TWork, TResult>` registrations remain unchanged; the PostgreSQL provider keeps effect permits, retry timing, cancellation, and fencing authoritative rather than exposing a direct state mutation or retry hook.