Guarantee one memory-loop writer per Vault

[miniLV]

What to build

Guarantee that each Vault has exactly one scheduled memory-loop writer.

• Model the writer as one exclusive choice: codex or claude.
• Keep session-source selection and read-only skill installation targets independent and multi-select.
• Apply a Vault-wide writer lease to both Daily ingestion and periodic reconciliation.
• Reject or safely skip a second writer while a lease is active.
• Recover from stale leases after abnormal termination.
• Preserve compatibility with existing Codex-only configurations.
• Surface the selected writer, lease owner, and conflict reason in setup/status output.

Acceptance criteria

• Configuration cannot select Codex and Claude as writers at the same time.
• Runtime protection prevents concurrent Daily or reconciliation writes to the same Vault.
• Codex and Claude may still both be session sources.
• Codex and Claude may still both have the read-only query skill installed.
• Active collisions, abnormal release, and stale-lease recovery have automated coverage.
• Existing Codex-only setups migrate without requiring a manual reset.
• User-facing status clearly explains which writer owns the Vault and why a conflicting run was rejected.

Blocked by

None.

[miniLV]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Enforce one exclusive scheduled memory-loop writer for each Vault.

Current behavior:
The repository documents that one Vault should have one scheduled writer, and the supported setup currently uses Codex App Automations. There is no shared runtime ownership mechanism protecting Daily ingestion and periodic reconciliation from a second scheduler.

Desired behavior:
Writer selection is exclusive and independent from session sources and read-only Skill targets. Daily and reconciliation acquire the same Vault-wide ownership lease, reject active collisions, recover safely from stale ownership after abnormal termination, and expose actionable status.

Key interfaces:

• Writer configuration — one explicit owner, currently codex or claude.
• Vault writer ownership — acquire, renew or validate, release, and stale recovery semantics shared by every write workflow.
• Setup/status output — selected owner, active lease owner, and conflict reason.

Acceptance criteria:

• Configuration cannot select two scheduled writers for one Vault.
• Daily and reconciliation use the same ownership contract.
• Concurrent writers cannot mutate the Vault at the same time.
• Stale ownership can be recovered without deleting valid active ownership.
• Codex-only installations continue working without manual reset.
• Session-source and read-only Skill target selections remain independent and multi-select.
• Tests cover collision, normal release, abnormal termination, stale recovery, and migration.

Out of scope:

• Creating Claude Desktop scheduled tasks.
• Changing the read-only engineering memory Skill.
• Supporting multiple simultaneous writers.