Release & support

Current 0.1.0 source candidate

The workspace declares 0.1.0. Complete release acceptance remains open. Read the 0.1.0 progress report for recorded checks and remaining work. Read Cargo.toml, studio/package.json, and extensions/native-alpha-v1.json for source versions and the extension profile. A source version does not establish an accepted artifact or provider support. Use the exact source revision, dirty changes, and lockfile identities with every result.

Last accepted release

Last accepted release: 0.0.3 passed source, Studio, and persistent preview acceptance on 2026-10-05. Accepted source: 584c01b614127b3f62799f1a26a1cdf3f734c3dc. Restart acceptance preserves edited and deleted seeded Resources. Explicit application acceptance uses WPE 2364 with the locked Playwright 1.63.0 client. The earlier default WPE 2359 runs retain their documented native compositor failure. The tested replacement runtime does not establish every browser protocol feature or every Safari platform. The completion record identifies its accepted source and executed checks. Use the matching 0.0.3 Cargo and Studio source set. Recompile trusted extensions. The compatibility review lists descriptor and renderer changes. Native format eight, archive format six, and query protocol version one remain unchanged.

The native-alpha and 0.0.2 records below retain their historical support boundaries.

Status: native source alpha accepted on 2026-10-03. The completion report identifies the accepted source revision, artifacts, and executed evidence. The 0.0.2 Studio source and asset release passed local acceptance on 2026-10-05. The completion record identifies its exact source revision and evidence. The accepted source was pushed to GitHub main at 3e4822e; GitHub Actions and registry publication remain disabled.

Historical native-alpha profile

The tested Linux host does not establish support for every operating system or filesystem. Rust source APIs remain experimental. No stable binary ABI or cross-release source compatibility is promised. Use one matching source package set. Recompile extensions when you change it. This release does not specify a support response-time commitment.

Data compatibility

Accepted 0.0.3 uses native storage format 8 and archive format 6. The unreleased 0.1.0 candidate uses native format 11 and archive format 7. Format 9 introduced frozen delayed channel eligibility; format 10 separates native Work records and metadata. Format 11 stores journal positions separately and keeps scalar Resource metadata. Focused scheduling, archive conversion, populated adapter upgrade and native-layout checks pass. Earlier previous-release database-reader rejection passed on copied SQLite and redb fixtures before the format-10 change. The reader report records source identity, controls, and limits. The latest working-source verifier passed; final-package verification, whole-application upgrade and release acceptance remain open. The current release evidence audit separates current results from historical tests. Ordinary open rejects unsupported native markers. Native upgrade describes candidate explicit conversion from formats 3 through 10 into format 11. Resource migration preserves declared historical request codecs and unfinished obligations. Retention requires explicit policy and restore fences.

Keep a verified backup before offline maintenance. Preserve external blob bytes separately. Stop the active owner before maintenance and do not modify a live database with another tool. An old mutation receipt still requires current authority and its retained historical request codec. A retry with an unresolved outcome must keep the original operation identity. Operator recovery describes retry, reconciliation, and explicit compensation.

Limits

An action changes a Resource through the common commit contract. Reactive chains keep earlier commits and retry a failed step within declared budgets. Compensation is an explicit Resource action; it does not erase history or infer rollback from a timeout. External delivery cannot guarantee deduplication without the declared provider or receiver support.

Queries use the common semantic model and checked adapter strategies. Moving pagination does not promise a stable snapshot across requests. Local query measurements apply to their recorded workloads, not every database or deployment.

Independent Field identities and a Field registry remain open proposals. WASM, dynamic loading, RabbitMQ, Studio, shared tenancy, multiwriter deployment, and heavy analytics are outside the accepted native alpha. The real-provider fixture does not establish universal OAuth compatibility, human login, or production TLS deployment. Process-exit tests do not certify machine power-loss durability. Automated author tests do not establish human usability or measured productivity improvement.

Candidate 0.1.0 identity boundary

The unreleased Host implements a restricted RSA/RS256 provider profile. It does not establish universal OIDC provider interoperability. The JWK parser accepts its declared key members and bounded certificate metadata. It rejects other members. A key set is limited to 65,536 bytes and eight keys. Certificate metadata does not establish certificate trust. This restriction differs from RFC 7517's general rule for unknown JWK members. Do not infer broader interoperability from one successful provider fixture. The identity investigation records this limit and the upgrade experiment.

The legacy provider fixture supports the historical application login. It is not a production identity provider. The upgrade experiment preserves separate verified principals for the legacy fixture and the current provider. Linking both principals to one User does not combine their receipt identities or permit cross-provider result disclosure. Whole-application upgrade acceptance remains open.

Verification and maintenance

Run the complete local gates before distributing changed source. Use the release skill for the command sequence and the release report for executed evidence. Keep failed checks and known limitations visible. Do not infer readiness from a selected example alone.

The local artifact producer runs the fixed acceptance sequence from a clean checkout. It writes source and skill archives, gate logs, a manifest, and checksums to an exclusive directory. Artifact publication requires the tested Linux/ext4 host and GNU tools described in that procedure. This requirement applies to artifact preparation, not to the generic persistence contract.

Report a defect with the source revision, lock hash, safe error category, and a minimal synthetic reproduction. Exclude credentials, private Resource values, and customer databases from reports. GitHub hosts source; local scripts perform verification and artifact preparation.

Historical 0.0.2 package set

The 0.0.2 workspace manifests use version 0.0.2. All local ROM dependency constraints use the same exact version. The frontend manifest and lock identify 0.0.2 separately from the Cargo lock. Use the complete matching source package set. Do not mix native alpha packages with 0.0.2 packages.

The owner's requested identifier sorts before 0.1.0-alpha.1 under semantic version ordering. It does not describe a rollback of the accepted native alpha's code or data formats. Native storage format 8 and archive format 6 remain unchanged. The historical native alpha artifact and its source revision remain available with their original identities.

The new Studio metadata changes experimental Rust source APIs. Manual FieldCodec and input descriptor literals need the codec_wrappers member. An empty path means that the codec owns the complete declared shape. Recompile extensions against the complete 0.0.2 source set.

The accepted Studio uses static Svelte and shadcn-svelte assets with an optional Rust host. The host verifies human OIDC, maintains server-side sessions, and enforces current Resource authority. The executed provider profile does not establish compatibility with every identity provider. Actual native/browser tests do not establish production TLS deployment or client VPN reachability. Final artifact acceptance and protected preview acceptance remain release gates.

Historical Studio source authoring for 0.0.2

The public Studio facade exports the application, client, renderer registration, shared types, and input control. The external author example uses these exports from an independently extracted Studio source tree. Its custom renderer uses codec identity, not Resource-specific view branches. This is a source-consumer contract. It is not a registry-published npm package.

The executed author workflow uses Linux, Node.js 22, pinned dependencies, and an explicitly selected immutable native binary. Chromium and WebKit test the actual provider against SQLite and redb. These automated tests do not establish human usability or support for every provider or operating system.

The current scenario index links current acceptance evidence. The historical native-alpha scenario report retains its original six-gate scope.

Accepted 0.0.2 source and Studio assets

The local release bundle uses source revision 8652fcd2d296f2bfe3102cdc0dfe977fecf1b034. It contains source and Studio assets. It does not publish a registry package or binary. The accepted 0.0.2 preview served that Studio build and its protected API at /rom-studio/. The preview uses the demonstration identity provider. Its in-memory grants and signing keys reset after restart. Local HTTPS, API-protection, and restart checks passed. Remote Mac and iPhone access still needs client-side verification.