v1.0.1

Fixes

Prevent duplicated initial content after a collaboration server crash and reconnect. The server now commits the initial seed and its CRDT identity to SQLite before exposing it to clients.

• Preserve the same seed across reconnects, including when a read-only viewer connects before the first writer.
• Leave the live document untouched if the initial database write fails.
• Preserve intentionally cleared documents and existing content without reseeding.

Documentation and tests

Document graceful shutdown, persistence limits, ephemeral presence, and the requirements for alternative database integrations.

Add regression coverage for crash recovery, concurrent writers, failed writes and retries, reseeding exclusions, and SIGINT/SIGTERM shutdown.

Compatibility

• Supported runtime: Node.js 22.23.2.
• No dependency or lockfile changes.
• No database schema migration is required.
• Custom persistence backends must preserve the commit-before-broadcast guarantee.

Upgrade and rollback

Back up SQLite using the procedure in OPERATIONS.md before deployment. Update to this release and rebuild the services while retaining the existing persistence volume.

To roll back, redeploy the previously approved source revision. This release does not require a database rollback migration.

Known limitations

Ordinary edits retain debounced persistence. Abrupt termination can still lose edits that have not reached storage; the seed fix does not make every keystroke durable.

Distribution

This is an MIT-licensed source release. No npm packages or container images are published.

Self-hosting v1.0.0

Self-hosting v1.0.0

Initial versioned source release of the MIT-licensed Domternal self-hosting reference services.

Included

• Node.js collaboration server based on Hocuspocus and Yjs
• Persistent SQLite document, comment and version storage
• Reference AI proxy for connecting Domternal applications to hosted or local AI providers
• Docker Compose configuration for running both services
• Health checks, authentication controls and secure secret-file handling
• Backup, restore, token rotation and operational guidance
• Container validation for amd64 and arm64
• Supply-chain, dependency, artifact and vulnerability checks
• Maintainer procedures for future source releases

Requirements

• Node.js 22.23.2 for the documented local workflow
• A current Docker Engine and Docker Compose v2 for container deployments
• Strong randomly generated caller tokens
• A provider API key when using a hosted AI provider

Review the repository README and service-specific documentation before deployment. Replace all example credentials and configure TLS, network access, storage encryption, backups and monitoring according to the deployment environment.

License scope

The reference services in this repository are published under the MIT License and do not require a Domternal Pro License Key.

Applications that install or use Domternal Pro packages remain governed by the applicable Domternal Pro Commercial License and accepted Order.

Release scope

This is a source-only release. It does not publish npm packages or container images. Build and deploy the reviewed source using the documented procedures.