v0.15.11

• TUI /sync now previews project AGENTS.md summaries and saves the exact reviewed candidates after confirmation. Custom memory-store paths use the launch project as their source.
• Empty and filtered dashboards explain what to do next. Long previews scroll, and compact terminals keep controls and errors visible.
• DOX imports reject conflicting project/root identities atomically, retain stable IDs, and clearly report secret-containing files skipped entirely.
• Successful activation checks existing valid recall receipts and gives a concrete next step when a new harness session is needed.
• Codex 0.3.8 and Claude 0.3.6 retain native lifecycle hooks and require CLI 0.15.11 for DOX writes. Re-running init safely backfills this guidance into recognized generated project instructions.
• Relative file sources support legacy upgrades; linked database paths do not qualify as source-local legacy stores unless their actual location belongs to the source project.

A recall receipt proves the memory hook ran; it can legitimately return zero memories from a new store. DOX sync imports project instruction summaries, while lifecycle capture saves selected durable outcomes from agents working in that project. Coordinated-mode imports require the existing coordinator capability in the TUI's environment.

DOX source fingerprints bind new records to their canonical project root. Shared legacy records and fingerprinted records copied or moved to another root require provenance review before reuse; the importer does not silently rebind records or migrate stable IDs. Use separate project-local stores when source IDs conflict.

This release includes the 0.15.10 changes. The 0.15.10 workflow was cancelled before binary publication while late-review fixes were completed.