v0.5.0

Conduit now has durable local persistence

Conduit’s runtime state has moved from scattered local files into embedded Turso
databases.

This is a foundational release. Drafts, refinement history, agent runs, reviews,
recovery state, and reusable role profiles now persist through a typed database API
—while approved feature packets remain ordinary, reviewable files in Git.

A safer startup experience

When Conduit starts, it now displays a migration screen before running application
queries.

It safely:

1. Migrates the user-global database.
2. Migrates the project database.
3. Imports existing file-backed state.
4. Opens the application only when storage is ready.

Migrations are ordered and checksummed. Before applying changes, Conduit creates a
backup, checks it for plaintext secrets, and records recovery information. If
something is unsafe, startup stops with actionable guidance instead of continuing
against a partially migrated database.

Local by design

Conduit uses embedded Turso with two separate storage scopes:

• The project database keeps drafts, refinement state, runs, reviews, and recovery
  data local to the repository.

• The global database stores reusable role-profile defaults for the current
  machine.

Provider credentials remain in the operating-system vault or encrypted fallback.
They are never stored in project databases, migration backups, agent prompts, or
run logs.

Coding agents also never receive database paths, connections, or storage helpers.
The Conduit process remains the sole database owner.

Built for developers, too

The new persistence layer uses typed Kysely repositories and domain-owned
migrations. Application services share one lifecycle-managed project connection,
and the previous monolithic bootstrap has been split into focused domain services.

A new database API guide documents how to:

• Add domain repositories.
• Write migrations.
• Use transactions safely.
• Manage connection ownership.
• Test persistence and recovery behavior.
• Extend storage without leaking infrastructure into business logic.

There is also a new diagnostic command:

conduit storage-doctor

It verifies migrations, prepared queries, transactions, native Turso bindings, and
close/reopen persistence.

Better documentation and mobile support

The Conduit website now includes:

• Updated storage and migration documentation.
• An interactive Turso persistence showcase.
• Mobile navigation.
• Responsive documentation navigation.
• Fixed horizontal overflow on smaller screens.

Supported standalone platforms

The embedded Turso standalone build currently supports:

• Linux x64 glibc
• Linux ARM64 glibc
• macOS on Apple Silicon
• Windows x64

Intel macOS and Alpine/musl builds are not yet supported.

What happens to existing projects?

Existing projects migrate automatically on their first project-aware startup.
Compatible legacy drafts and run artifacts are imported idempotently, and their
original files are left untouched.

Your approved feature packets remain in specs/. Only local runtime state moves into
the database.

This release gives Conduit a durable, secure persistence foundation—and prepares
the architecture for richer agent memory and handoff capabilities in the releases
ahead.

What's Changed

• feat: refine persistence and memory specs by @MartinAndreev in #10
• Complete Feature 002 Turso persistence foundation by @MartinAndreev in #11

Full Changelog: v0.4.2...v0.5.0