v0.4.0

Integrations are now capability-driven instead of hardcoded to Claude Code and
Codex. A declarative profile describes detection, skills, instructions, hooks,
native-memory sources, and default trust. Built-in profiles cover Claude Code,
Codex, Hermes, and a generic local integration; additional local profiles can be
added without changing the engine. Configuration now uses integrations = [...] and
per-integration override sections; old single-user instances are updated manually rather
than carrying an automatic migration layer.

regesto install now plans and applies those profiles through the Go engine. Its
versioned JSON dry-run reports canonical targets, ownership, current and intended
state, backups, and the exact action before anything is written. Shared skill or
instruction targets are reconciled once, generated artifacts carry ownership
markers, hooks are registered through declared protocols, and symlink or path
escapes are refused.

Every integration gets portable Regesto skills. Claude keeps its tailored
variant while Codex, Hermes, and generic integrations receive the same search,
write, and promote workflows through stable instance shims. Instruction blocks
use bounded markers, preserve host-owned text, and can be installed into more than
one declared target without duplicating content.

Native Markdown memory can now be harvested from every declared source with a
separate persisted baseline. Overlapping declarations deduplicate publication,
untrusted sources remain quarantined, and all reads
and writes stay within descriptor-verified roots. No proprietary cloud-memory
connector or network transport was added.

A local stdio MCP server exposes Regesto resources and tools. regesto mcp
implements the 2025-06-18 initialize lifecycle, tools, resources, bounded JSON-RPC
framing, and clean EOF shutdown using the same validation and trust rules as the
CLI. It listens on no socket and writes only protocol messages to stdout.

regesto doctor [--integration ID] [--json] provides deterministic, read-only
diagnostics for detection, installed artifacts, capabilities, memory, and trust,
with concrete remediation. The documentation now includes a profile-derived
capability matrix and setup recipes for Claude Code, Codex, Hermes, generic local
tools, and MCP clients.

Cycle alert delivery is now explicit and portable. Regesto no longer posts built-in
desktop notifications through macOS osascript or Linux notify-send; the former opens
Script Editor when clicked and neither backend can offer one coherent CLI interaction.
External alerts are sent only when [notify].command names a user-chosen executable. The
existing argument and REGESTO_NOTIFY_* environment contract is unchanged. Independently
of that optional delivery, the current failure reason and age now appear at the top of
agent context, so an agent is warned before relying on stale generated indexes.

If you are upgrading an existing 0.3.x instance, configure [notify].command if you
want external alerts. With no command, desktop alerts stop after the upgrade; see the
README alert configuration for the small
configuration block.

The release gate now builds the engine away from its knowledge-base instance and
drives init, inert install dry-run, install, doctor, lint, upgrade, and an MCP
handshake inside a disposable HOME.